01Status
Is it responding right now?
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.
02Public health endpoints
Three surfaces, three audiences.
The narrow uptime probe, the authenticated operator view, and the protected metrics endpoint — each one answers exactly one question.
/healthz
Simplest uptime check for load balancers and monitors
/v1/health
Minimal public lane status without provider internals; authenticated operators see the richer view
/metrics
Intentionally protected; should be scraped only by authorized operators
03How to interpret status
Healthy, degraded, offline.
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.
Healthy
The configured API path is responding now. It does not, by itself, certify multi-provider redundancy, broader continuity depth, or wider contractual availability.
Degraded
Often a narrower dependency problem — provider health, quota exhaustion, stale data — without meaning a total platform outage.
Offline
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.
04Live detector gate
Read straight from the current artifact.
This value is read from 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.
Overall gate
Loading current artifact...
Canonical page
/benchmark
Public artifact
/resources/pii_benchmark_latest.json
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.
05If something looks off
Triage first, then escalate with the request ID.
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.
Use status for runtime triage and the trust pages for diligence. That split is deliberate: one surface answers "is it responding now," the other answers "what has been proven and how should it be inspected."