Skip to content
Error codes · realuptime errors ingest

RU-4003: Ingest rate limited

This ingest key sent batches faster than its rate budget allows. The refused batch's events are counted as dropped_rate_limited on your dashboard: nothing disappears silently. Ships with `reason: "rate_limited"`.

On the wire

Ships with HTTP status 429, carrying "code": "RU-4003" 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 storm where every request reports.
  • SDK batching disabled, sending one event per request.

How to fix it

  1. Honor the Retry-After header.
  2. Enable SDK batching so many events ride one request.
  3. Fix the erroring code path: the rate limit is usually a symptom of an error storm.

Related codes

Still stuck?

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