Skip to content
Error codes · realuptime errors ingest

RU-4022: Ingest refused for a suspended account

The ingest key is valid, but the account that owns the project is suspended. Event ingest, user feedback and the scrub rules fetch all refuse with this code, and the reply adds `reason: "account_suspended"`.

Where it is raised

  • Errors ingest (/api/errors/v1/ingest)
  • Errors feedback (/api/errors/v1/feedback)
  • Scrub rules (/api/errors/v1/scrub-rules)

What triggers it

The ingest key is looked up and found valid, but the account behind it is suspended, so the key's verdict is suspended rather than ok. The reply adds reason account_suspended, which the REST suspension reply (RU-1009) does not carry.

Example response

POST /api/errors/v1/ingest/<key>
HTTP 403

{
  "error": "Your account has been suspended. Email support if you believe this was a mistake.",
  "reason": "account_suspended",
  "code": "RU-4022"
}

Common causes

  • Staff suspended the account that owns this Errors project, so every ingest key in it is refused while the suspension lasts.

How to fix it

  1. Contact support@realuptime.io and ask for the suspension to be lifted. A suspension does not change or revoke the project's ingest keys.

Related codes