Skip to content
Error codes · Outages & the public API

RU-6001: Service not covered by the outage tracker

The outage API does not measure the service you asked about. The 404 carries a real body saying so: "we do not measure this" is the honest answer, and must never be mistaken for "healthy".

Where it is raised

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

What triggers it

After the slug validates, the route asks the live-service module and then the catalog. A slug in neither gets a real answer body that says the service is not covered, with the code added, rather than an empty 404, so a reader that looks only at the status cannot take it for a healthy reading. These 404s are cacheable for two minutes.

Example response

GET /api/v1/outages/not-a-tracked-service
HTTP 404
Cache-Control: public, max-age=120, s-maxage=120, stale-while-revalidate=600

{
  "schema_version": 1,
  "service": {
    "slug": "not-a-tracked-service"
  },
  "verdict": "not_covered",
  "summary": "RealUptime does not currently check \"not-a-tracked-service\", so we have no reading for it. This is not a statement that its checks pass.",
  "source": {
    "url": "https://realuptime.io/outages",
    "methodology_url": "<methodology page>",
    "publisher": "RealUptime"
  },
  "code": "RU-6001"
}

Common causes

  • The service isn't in the tracked catalog.
  • A typo in the service slug.

How to fix it

  1. Browse the tracked catalog at /outages for the correct slug.
  2. If a service you rely on is missing, tell support: the catalog grows by request.

Related codes