Status Service combines customer-facing status pages with collector-backed monitoring, regional quorum checks, and automation hooks so your team can detect issues earlier and communicate with confidence.
Validate public endpoints, expected status codes, redirects, and response latency from distributed collector locations.
Check JSON APIs and key response fields so synthetic monitoring follows the interfaces your customers depend on.
Require agreement across multiple collectors before escalating, so one noisy route or local ISP issue does not become a false incident.
Route confirmed monitor signals into incidents, component state, timelines, and subscriber notifications.
Collectors provide the geographic evidence. You decide how much agreement is required before Status Service turns that evidence into an alert, incident, or customer-facing update.
Choose method, expected status, timeout, validation rules, region scope, and the quorum needed before a monitor is treated as failed.
Send operational alerts to your team while keeping subscribers informed through the status page channels they opted into.
Use collector results as supporting evidence for component state, incidents, maintenance decisions, and post-incident timelines.
Use monitors for early warning, keep status pages accurate, and give customers transparent evidence from the same platform.
Create your Status Service account