Skip to content
Error codes · realuptime errors ingest

RU-4022: Account is suspended

The ingest key is valid, but the account it belongs to is suspended. Errors ingest, heartbeat pings, and inbound incident webhooks all refuse the same way while an account is suspended.

On the wire

Ships with HTTP status 403, carrying "code": "RU-4022" in the response body alongside the human-readable error message. Existing fields are never replaced by the code: it is additive.

Common causes

  • The account was suspended by RealUptime staff.

How to fix it

  1. Contact support@realuptime.io. There is no self-service reactivation.

Related codes

Still stuck?

Ask support and mention RU-4022: the code pins down the exact refusal path, so you skip the diagnostic back-and-forth.