Appearance
Incidents
Public, rate-limited per IP
No auth required. Held to the shared public budget (~1,200 requests/min per IP, 429 over). Submitting crowd reports is metered more tightly per IP and device to curb abuse. See rate limits.
The outage feed for a target: what providers have officially acknowledged, what our probes detected, and what other users are reporting right now.
- Base path:
https://ws.latency.app/v1/incidents - Auth: none (public)
List incidents
bash
# Everything currently active
curl "https://ws.latency.app/v1/incidents"
# Narrowed to one target
curl "https://ws.latency.app/v1/incidents?target=cloudflare.com"| Parameter | Meaning |
|---|---|
target | Optional domain to filter to. Omit for the full active feed. |
Confirmation levels
Not every report is equal. An incident carries a status that says how sure we are:
| Status | Meaning |
|---|---|
unconfirmed | Some user reports, but below the threshold to call it real. |
active | Enough independent reports to treat it as a genuine incident. |
confirmed | Corroborated by the provider's own status page or our probes. The strongest signal. |
The confirmed tier is what keeps the feed honest: a handful of reports won't turn a service red, and a provider quietly acknowledging an outage will surface even with zero user reports.
Reporting an outage
Anyone can contribute a report. Reports feed the crowd signal above.
bash
curl -X POST "https://ws.latency.app/v1/reports" \
-H 'content-type: application/json' \
-d '{ "domain": "example.com", "reason": "timeout" }'| Field | Meaning |
|---|---|
domain | The affected domain. Required. |
reason | Optional category, e.g. timeout, errors, slow. |
To fetch the current suggested reasons for a target (used by our app's report sheet):
bash
curl "https://ws.latency.app/v1/reports/recommend?query=example.com"Crowd vs. official
The crowdVerdict you see in inspect reflects user reports only; it's deliberately kept separate from the provider's official status so a page-confirmed outage with no reports never reads as "the crowd confirmed it," and vice versa.
Related
- Status catalog: the official-status side of reconciliation
- Inspect: incidents in the context of a single host