Skip to content
Error codes · realuptime errors ingest

RU-4001: Error event quota reached

This month's error-event quota is used up, so the whole batch was dropped: and counted: dropped events appear on your Errors dashboard, never silently discarded. The response's `resetsAt` says when the quota resets. Ships with `reason: "over_quota"`.

On the wire

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

Common causes

  • An error spike consumed the month's quota.
  • A noisy, known error group left unresolved and re-reported on every request.

How to fix it

  1. Check the Errors dashboard's drop counters to see what consumed the quota.
  2. Resolve or rate-limit the noisiest issue at the source.
  3. Upgrade the plan if your normal volume genuinely exceeds the quota; SDKs stop retrying until `resetsAt`.

Related codes

Still stuck?

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