Skip to content
Error codes · Authentication & API keys

RU-1009: Account is suspended

The key (or session) is otherwise valid, but the account it belongs to is suspended. Every API and MCP request refuses the same way, starting immediately: nothing about which check or endpoint you called changes the answer.

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

  1. Write to support@realuptime.io from the account owner's address. Only staff can lift a suspension, the account cannot do it itself.

Related codes