Status / live reachability probe
Service status, without the theatre.
This page runs one real check: it asks the ScanDrix API for its /healthz endpoint and reports what came back, with the round-trip time of that request. It is a live reachability signal, refreshed every 30 seconds — not an incident log, and not a latency measurement of your reviews.
Contractual uptime commitments are a separate thing, agreed in writing. The targets we publish are in the SLA section of our Terms, and only a signed agreement changes them.
- Overall state
- Checking
- Probe latency
- —
- Awaiting a reading
- Last checked
- —
- No reading yet
- Refresh cadence
- Every 30 s
- Pauses while the tab is hidden
01Current state
One probe, reported as it came back.
Nothing on this page is assumed healthy. If the probe cannot be completed, the state reads as unavailable rather than reverting to a green default.
Checking
Waiting for the first response from the status endpoint.
- Probe target
- GET /healthz
- Service reported
- Not reported
- Database ping
- Not reported
- HTTP status
- No response
The latency figure above is the round-trip time of the status page's own /healthz request. It is not the time your pull request review takes, and it says nothing about latency inside the review pipeline.
02Components
What is listed, and what is measured.
These are the parts of the platform that a request travels through. Only the first row is probed from here. The rest are described so you know what the state line does and does not cover — we would rather say “not probed” than print a status we did not measure.
If a component fails, this page will not necessarily change. Self-hosted deployments can be monitored directly instead: the services expose /healthz, /readyz and /metrics for your own alerting.
03Commitments
Targets we wrote down, not a chart we did not measure.
This deployment does not keep an uptime history, so there is no honest bar chart to print here. What follows are the published availability targets, which are contractual promises rather than observed measurements.
- Team
- 99.9% uptime target, as published in Terms §3, Service Level Agreement.
- Scale
- 99.95% uptime target, as published in the same SLA section.
- Enterprise
- 99.99% uptime target with 24/7 engineering escalation, and service credits where a signed agreement includes them.
A target is not a measurement. Whether a given period met the target is established from your agreement and our incident records, not from a badge on this page.
04Method & help
Live probe from GET /api/system/status; refreshed every 30 seconds while this tab is visible, and on demand when you press refresh. The endpoint calls the API's /healthz with a 2.5-second timeout and reports the round-trip time, the HTTP status, and whatever the service says about itself.
If something looks wrong and you need it checked by a person, we would rather hear from you.