Skip to content
Error codes · Outages & the public API

RU-6005: Outage stack not found

The stack key in the URL does not name a stack we hold. A stack is a named set of tracked services with its own combined page at /outages/stack/<slug>; the JSON and MCP reads answer 404 with this code when the slug or id is unknown or the stack was deleted. It says nothing about any service's health.

On the wire

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

Common causes

  • A typo in the stack slug or id, or a link copied before the stack was saved.
  • The stack was deleted by its owner, or an anonymous stack expired with its unconfirmed subscription.

How to fix it

  1. Copy the key from the stack page URL (/outages/stack/<slug>) or build a new stack at /outages/stack.
  2. For one service's reading, use /api/v1/outages/<slug> instead.

Related codes

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

Still stuck?

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