Skip to content
Error codes · Outages & the public API

RU-6003: Public outage API rate limited

Your address read the public outage API faster than its per-IP budget allows. The Retry-After header says how long to back off. No API key is involved: this is the keyless public surface.

On the wire

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

Common causes

  • Polling one service's reading in a tight loop.
  • Many callers behind one shared egress address.

How to fix it

  1. Honor the Retry-After header.
  2. Cache readings: responses already carry Cache-Control allowing two minutes of reuse.

Related codes

  • RU-6001: Service not covered by the outage tracker

Still stuck?

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