Skip to content
Error codes · Outages & the public API

RU-6002: Invalid outage query

The outage API request had an invalid slug or region parameter. The `error` field names the failing parameter.

Where it is raised

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

What triggers it

The service slug and the optional region query are checked against one schema, and the first issue becomes the message, formatted as the field name, a colon and the schema's text. The rate limit is spent before this check, so a malformed request still costs budget.

Example response

GET /api/v1/outages/github?region=xyz
HTTP 400
Cache-Control: no-store

{
  "error": "region: Invalid option: expected one of \"iad\"|\"sjc\"|\"fra\"|\"nrt\"|\"ord\"|\"yyz\"|\"lhr\"|\"sin\"|\"syd\"|\"gru\"",
  "code": "RU-6002"
}

Common causes

  • A region outside the probe fleet (valid: iad, sjc, fra, nrt, ord, yyz, lhr, sin, syd, gru).
  • A slug with characters the catalog never uses.

How to fix it

  1. Use one of the live regions, iad, sjc, fra, nrt, ord, yyz, lhr, sin, syd or gru, or omit the parameter for every region.
  2. Copy the slug from the service's /outages page URL.

Related codes