Skip to content
Error codes · Outages & the public API

RU-6003: Public outage API rate limited

Your address read the public outage API more than 120 times in a minute, the per-address budget of the keyless JSON route. No API key is involved: this is the keyless public surface.

Where it is raised

  • GET /api/v1/outages/{slug}
  • GET /api/v1/outages

What triggers it

The keyless outage JSON route allows 120 reads a minute per client address, counted before the slug is read. The throttle reply is never cacheable, so a shared cache cannot hand one caller's refusal to the next.

Example response

GET /api/v1/outages/github
HTTP 429
Retry-After: <seconds>
Cache-Control: no-store

{
  "error": "Rate limit exceeded. Try again shortly.",
  "code": "RU-6003"
}

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