Live runtime posture, the public health endpoints behind it, and what each one is intended to answer. Status answers "is it responding now"; the trust pages carry the broader proof story.
It does not, by itself, certify multi-provider redundancy, broader continuity depth, or wider contractual availability.
That can be provider health, quota exhaustion, stale data, or another dependency issue without meaning a total platform outage.
That split is deliberate: one surface answers “is it responding now,” the other answers “what has been proven and how should it be inspected.”
Three surfaces, three audiences. The narrow uptime probe, the authenticated operator view, and the protected metrics endpoint — each one answers exactly one question.
Simplest uptime check for load balancers and monitors
Minimal public lane status without provider internals; authenticated operators see the richer view
Intentionally protected; should be scraped only by authorized operators
Healthy means the API process is up and its configured privacy-routing surfaces are responding. Degraded usually points at a provider, freshness, or dependency issue — not a full platform outage.
All systems operational
Partial issue — check provider or lane status
Service unavailable
Continuity proof is deliberately narrow on this page. Dated evidence for planned-maintenance continuity and guided recovery drills lives on the Trust & Evidence page — that's where your team should go for the dated proof set and its limits, not here.
Reads the current benchmark artifact directly — not a frozen number on this page. The /benchmark page is where the full suite list, methodology, and claim boundary live.
Loading current artifact...
Detector-quality claims belong on /benchmark. Status answers whether the configured service is responding now; it doesn't infer broader detector quality or forward guarantees.
Two paths: triage in-product first, then contact your operator with the request ID. For diligence-grade evidence rather than live runtime status, the Trust & Evidence and Enterprise pages carry the dated proof set.
If the dashboard is reachable but a lane or provider is degraded, use the in-product Help Center and operator guidance first. For broader incidents, contact your DataSitr operator with the request ID shown in the dashboard or API response. Provider-specific degradation can include quota exhaustion or upstream dependency issues without implying a full service outage.