Core concepts

System status

Check whether the Public API, MCP server, and USGM Core are operating normally.

We publish real-time uptime and incident status at 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

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:

  • Public API — the REST gateway (api.usglobalmail.com).
  • MCP server — the agent endpoint (mcp.usglobalmail.com).
  • USGM Core — the internal services the API delegates to.

Reading the status

Each component shows one of:

StatusWhat it means
OperationalWorking normally.
Degraded performanceUp, but slow or partially impaired (e.g. elevated latency).
Partial outageSome functionality is unavailable.
Major outageThe component is down.
Under maintenancePlanned maintenance is in progress.

Subscribe to updates

Don’t wait for a failed request to find out. Click Subscribe on the status page to get notified when an incident is opened or resolved — via email, SMS, Slack, Discord, Microsoft Teams, or a webhook, or by following the RSS/Atom feed at https://status.usglobalmail.com/feed.rss.

Check status programmatically

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

$curl https://status.usglobalmail.com/summary.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

Repeated 5xx responses — internal_error, bad_gateway, service_unavailable, or 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.