# Check the status of Coritan's services

> See how Coritan's services are running on the status page, and read the notices about incidents and maintenance at the top of the dashboard.

Source: https://www.coritan.com/docs/support/status-and-notices/

In the dashboard:

- /status: https://www.coritan.com/status

When something on Coritan is not working as it should, the status page and the notices at the top of the dashboard say what we know and what we are doing about it. Check them before you [contact support](/docs/support/conversations/) about a problem that may not be yours alone.

## Before you begin

- The [status page](https://www.coritan.com/status) is open to everyone. To see the notices for your account, sign in to the [dashboard](https://www.coritan.com/dashboard).

## Check the status page

Open [www.coritan.com/status](https://www.coritan.com/status). The page shows:

- how each location and our email service are running, and our website, our API and the payment services we rely on;
- the incidents and planned maintenance we are working on, each with its updates, newest first;
- incidents and maintenance we resolved in the last 24 hours, so you can see what happened and when it was fixed.

The page checks again every minute while you have it open.

## Read the notices in the dashboard

Notices appear above the page you are on in the dashboard, incidents first:

- An *incident* is a problem we are working on now. Its notice shows the latest update, such as `Monitoring, 6 minutes ago:`, and stays until we resolve the incident.
- *Planned maintenance* says what we will work on and when. It stays until the work is done.
- An *announcement* tells you about a change, such as a new product or a new invoice layout. Select **Dismiss** to hide it in this browser.

An incident or maintenance that is also on the status page has a **Status page** button that opens it.

Some notices are for accounts that pay for a service or a plan, and some are for accounts that pay for nothing, so two accounts can see different notices. A trial does not count as paying.

Notices change only when you move to another page, so the page you are reading never jumps. A notice we post or resolve while you read shows as you move between pages.

## Result

You know whether a problem is on our side, what we are doing about it, and when we last said so.

## Troubleshooting

A service is not working, and neither the status page nor the dashboard shows a notice
: The problem may be with your service alone. [Contact support](/docs/support/conversations/) and say which service it is.

An announcement you dismissed shows again
: Dismissing hides it in one browser. It shows again in another browser, or after you clear this browser's site data.

## Related

- [Contact support from the dashboard](/docs/support/conversations/)
- [Choose which emails you get](/docs/account/notifications/)

## With the API

[`GET /status`](/docs/api/reference/client/notices/#op-get-api-v1-status) answers what the status page shows, and needs no sign-in. `status` is `operational`, `maintenance`, `degraded` or `down` for the platform as a whole, and each location and email region has its own. Each service in `services` is `operational`, `degraded`, `down`, or `unknown` when we could not check it. `incidents` lists what is live now and what we resolved in the last 24 hours.

```bash
curl https://api.coritan.com/api/v1/status
```

```json
{
  "status": "degraded",
  "checked_at": "2026-09-27T05:12:04.512345+00:00",
  "locations": [
    { "code": "IAD", "name": "Ashburn", "country_code": "US", "status": "degraded", "load_percent": 41, "memory_percent": 58, "disk_percent": 37 }
  ],
  "mail": [
    { "code": "eu", "name": "Email (eu)", "status": "operational" }
  ],
  "services": [
    { "key": "api", "status": "operational", "latency_ms": 3, "detail": "", "checked_at": 1790485924.51 }
  ],
  "incidents": [
    {
      "id": 31,
      "kind": "incident",
      "title": "Slow connections to servers in Ashburn",
      "body": "Some servers in Ashburn answer slowly or drop connections.",
      "status": "live",
      "starts_at": "2026-09-27T04:20:00",
      "ends_at": null,
      "resolved_at": null,
      "updates": [
        { "id": 93, "state": "monitoring", "body": "Connections are back to their usual speed, and we are watching them.", "created_at": "2026-09-27T05:04:00" }
      ]
    }
  ]
}
```

The example leaves some fields out. Times in `incidents` are in UTC, without a zone.

[`GET /notices`](/docs/api/reference/client/notices/#op-get-api-v1-notices) answers the notices your dashboard shows now, for the account signed in: incidents first, then maintenance, then announcements, at most ten. Each item has the same fields as an item in `incidents`, and `updates` lists its updates, newest first.

```bash
curl https://api.coritan.com/api/v1/notices \
  -H "Authorization: Bearer $CORITAN_TOKEN"
```

```json
{
  "items": [
    {
      "id": 43,
      "kind": "info",
      "title": "Invoices now list each service on its own line",
      "body": "From your next invoice, each service has its own line with the period it covers.",
      "audience": "all",
      "placement": "dashboard",
      "status": "live",
      "starts_at": "2026-09-25T09:00:00",
      "ends_at": "2026-10-09T09:00:00",
      "resolved_at": null,
      "created_at": "2026-09-25T08:41:12",
      "updated_at": "2026-09-25T08:41:12",
      "updates": []
    }
  ]
}
```

`kind` is `incident`, `maintenance` or `info` (an announcement). `placement` is `dashboard`, or `both` when the status page shows it too. `audience` is `all`, `paying` or `free`.

## API

- `GET /api/v1/status`: The platform's status, for the public status page (https://www.coritan.com/docs/api/reference/client/notices/#op-get-api-v1-status)
- `GET /api/v1/notices`: The notices the account's dashboard shows now (https://www.coritan.com/docs/api/reference/client/notices/#op-get-api-v1-notices)