Status catalog

Public, rate-limited per IP

No auth required. Held to the shared public budget (~1,200 requests/min per IP, 429 over). Sustained or high-volume use should authenticate to run against plan quotas instead. See rate limits.

A curated, continuously-updated catalog of the major providers your stack depends on (cloud platforms, CDNs, payment processors, developer tools) with their live status. It's the data behind "is they down, or is it just me?"

• Base path: https://ws.latency.app/v1/catalog
• Auth: none (public)

What makes it different

Most status aggregators just re-print a provider's own status page. Latency does two things on top of that:

1. Reconciliation. For each provider we also run our own probes against real endpoints. When a page says "all good" but our probes disagree, that gap is itself a signal (an unacknowledged problem).
2. A derived verdict. A provider's published indicator is only a display value: a big fleet can sit at "minor" indefinitely because a few nodes are always in maintenance. We derive a staleness-aware verdict that only turns red when an active incident actually backs it.

Request

# The whole catalog
curl "https://ws.latency.app/v1/catalog"

# One provider by domain
curl "https://ws.latency.app/v1/catalog?target=cloudflare.com"

Response

{
  "providers": [
    {
      "provider": "cloudflare",
      "providerDomain": "cloudflare.com",
      "indicator": "minor",
      "description": "Minor Service Outage",
      "incidents": [],
      "asns": [13335],
      "status": {
        "state": "operational",
        "summary": "All systems operational.",
        "hasIncident": false,
        "hasMajorIncident": false,
        "confirmed": false
      }
    }
  ]
}

Note the example above: the provider publishes indicator: "minor", but with no active incident behind it the derived status.state is operational. Colour your UI from status.state and show status.summary, never the raw indicator/description, which are feed-faithful passthrough for reference only.

Field	Use
indicator / description	The provider's own words. Display-only.
status.state	The verdict: operational | degraded | down | unknown.
status.summary	A human line guaranteed to agree with state.
status.confirmed	The provider's page corroborates an active outage.
incidents	Currently-unresolved incidents from the provider's feed.
asns	Networks this provider operates, and how inspect inherits its status onto hosted domains.

Operator overrides

Occasionally an admin may assert a provider's status for a bounded window (for example, to correct a misleading upstream feed during a known event). When that happens, status.override is present with a reason and an expiry; an asserted status is always disclosed, never shown as if it were observed.

Related

• Inspect: see a single host's catalog status in context
• Incidents: the outage feed reconciled against this catalog