Where it is raised
- Keyed MCP endpoint, same status and body
What triggers it
After the key authenticates, the account row is read, and a suspended_at value stops the request. It is raised on the REST API and the keyed MCP endpoint only. The suspension reply for Errors ingest is RU-4022, a separate code with its own body.
Example response
GET /api/v1/checks
HTTP 403
{
"error": "Your account has been suspended. Email support if you believe this was a mistake.",
"code": "RU-1009",
"docs": "https://realuptime.io/kb/errors/ru-1009"
}Common causes
- Staff suspended the account that owns this API key or MCP session.
How to fix it
- Write to support@realuptime.io from the account owner's address. Only staff can lift a suspension, the account cannot do it itself.