Appearance
Inspect
Public, rate-limited per IP
No auth required. Held to the shared public budget (~1,200 requests/min per IP, 429 over). Inspect fans out to several primitives per call, so it is heavier, authenticate for sustained use. See rate limits.
Everything Latency knows about a host, in a single call. Inspect is the primitive that powers the search box in our app and the public /inspect page: give it a domain or an IP and it composes DNS, geo, the status catalog, and crowd incidents into one answer.
- Base path:
https://ws.latency.app/v1/inspect - Auth: none (public)
Request
bash
curl "https://ws.latency.app/v1/inspect?target=cloudflare.com"| Parameter | Meaning |
|---|---|
target | Domain or IP to inspect. Required. |
ip | Optional pre-resolved IP (skips server-side DNS). |
locale | Optional locale for place names. |
If you pass a bare domain and no ip, Inspect resolves it for you via the DNS primitive.
What you get back
json
{
"target": "cloudflare.com",
"type": "domain",
"ip": "104.16.132.229",
"geo": { "ip": "…", "geo": { }, "ripe": { "asn": "13335", "asn_name": "CLOUDFLARENET" } },
"statusPage": { "indicator": "…", "status": { "state": "operational", "summary": "All systems operational." } },
"infrastructure": { "provider": "cloudflare", "status": { "state": "operational" } },
"incidents": null,
"verdict": { "label": "Operational", "tone": "operational" },
"crowdVerdict": { "label": "No reports", "tone": "unknown" }
}| Field | Meaning |
|---|---|
geo | Location + operating network (see Geo). |
statusPage | The host's own status page, if it's a tracked provider. |
infrastructure | The cloud the host runs on, discovered by ASN, with that provider's status. Shown alongside, never merged into, the host's own status. |
incidents | Crowd-reported or confirmed outages, if any. |
verdict | The overall, ready-to-display verdict. |
crowdVerdict | A user-reports-only verdict, kept separate from the official one. |
Read the verdict, not the raw indicator
The verdict and each status.state / status.summary are computed by Latency to be internally consistent and staleness-aware. A provider's own indicator/description are passed through verbatim for reference, but they can mislead: a large provider's status page may read "Minor Service Outage" purely because a handful of edge nodes are degraded, with no real incident. Always colour your UI from status.state and show status.summary, not the raw indicator. See the status catalog for why.
Infrastructure inheritance
If example.com is hosted on Cloudflare and Cloudflare is having an incident, Inspect surfaces that under infrastructure, a heads-up that your host's upstream is affected even when its own page is green. It's advisory and always shown separately, so one provider's blip never masquerades as thousands of hosts being down.
Related
- Status catalog: the provider statuses Inspect draws on
- Incidents: the outage feed it reconciles against