> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.usglobalmail.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.usglobalmail.com/_mcp/server.

# System status

We publish real-time uptime and incident status at **[status.usglobalmail.com](https://status.usglobalmail.com)**.
Check it first whenever something isn't working — it tells you at a glance whether the issue is a known
outage on our side or something specific to your request.

#### [Open the status page](https://status.usglobalmail.com)

status.usglobalmail.com — live status and incident history.

## What we track

Each system reports its own status independently, so you can see exactly what's affected:

* **USGM API** — the REST gateway (`api.usglobalmail.com`).
* **MCP server** — the agent endpoint (`mcp.usglobalmail.com`).
* **USGM Core** — the internal core of the USGM system.

## Reading the status

Each component shows one of:

| Status                   | What it means                                               |
| ------------------------ | ----------------------------------------------------------- |
| **Operational**          | Working normally.                                           |
| **Degraded performance** | Up, but slow or partially impaired (e.g. elevated latency). |
| **Partial outage**       | Some functionality is unavailable.                          |
| **Major outage**         | The component is down.                                      |
| **Under maintenance**    | Planned maintenance is in progress.                         |

## Subscribe to updates

Don't wait for a failed request to find out. Click **Get updates** on the status page to get notified when
an incident is opened or resolved — via **email, Slack, or a webhook**.

## Check status programmatically

The status page exposes a JSON summary you can poll from your own monitoring:

```bash
curl https://status.usglobalmail.com/v3/components.json
```

It returns the current status of each component and any active incidents — handy for gating your own
retries or dashboards on our health.

## When you hit an error

> **Note**
>
> Repeated `5xx` responses — [`internal_error`](/api/problems/internal_error),
> [`bad_gateway`](/api/problems/bad_gateway), [`service_unavailable`](/api/problems/service_unavailable),
> or [`gateway_timeout`](/api/problems/gateway_timeout) — are the signal to check the status page.
> If there's an open incident, it's on us; subscribe and wait for the resolved update. If status is all
> green and the errors persist, contact support and quote the `request_id` from the response.