Skip to content
Error codes · realuptime errors ingest

RU-4002: Ingest key revoked

The ingest key in the URL was revoked. Unlike agent tokens, ingest keys are designed to be public, so revocation refuses loudly: `reason: "key_revoked"`: and SDKs log it once and disable themselves instead of retrying into a black hole.

On the wire

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

Common causes

  • The key was rotated in realuptime Errors settings and old deploys still carry the previous key.
  • A key was revoked deliberately after being abused.

How to fix it

  1. Get the current ingest key from realuptime Errors settings.
  2. Redeploy every app and mobile build that embeds the old key.

Still stuck?

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