Service health

Fixture diagnostics and service health

Project → Fixtures compares exact run IDs with optional expected names and shows existence, expiry, latest arrival, credential status and recent API request metadata. It does not fetch message bodies. Request history is best-effort, limited to 100 records within 24 hours; invalid keys cannot be attributed to a project. Missing or truncated observations are unknown, not proof of absence.

Use service status for regional synthetic MX/capture journeys and the site JSON report for automation. The API’s service-status endpoint returns 200 for recent healthy routes and 503 for degraded or unknown state. /health reports process liveness only. Staging runs scheduled probes; samples older than five minutes are unknown.

Latency is synthetic send-to-read duration, including network and request overhead. Reports include sample counts, sparse-sample flags, p50/p95/p99 and failure rate. Project delays require that project’s own probe observations; global health does not fill missing project data. These measurements cannot prove that StaticForms or another sender submitted a particular message.

See the API reference for full request schemas and permission requirements.