Transparency

Every place we check from.

Live status of our seven Cloudflare edge regions plus out-of-band sentinel nodes on independent ASNs (Hetzner AS24940). Updated continuously. Multi-ASN quorum verification guarantees that a single-cloud provider outage never triggers false customer alerts.

RegionCoversNetworkStatusLast check
🇺🇸wnam
Western North AmericaAS13335 (Cloudflare Edge)ONLINEJust now
🇺🇸enam
Eastern North AmericaAS13335 (Cloudflare Edge)ONLINEJust now
🇬🇧weur
Western EuropeAS13335 (Cloudflare Edge)ONLINEJust now
🇵🇱eeur
Eastern EuropeAS13335 (Cloudflare Edge)ONLINEJust now
🌏apac
Tokyo, Singapore, Hong KongAS13335 (Cloudflare Edge)ONLINEJust now
🇦🇺oc
Australia, New ZealandAS13335 (Cloudflare Edge)ONLINEJust now
🇧🇷sam
Brazil, Chile, ArgentinaAS13335 (Cloudflare Edge)ONLINEJust now
🛡️ext-sentinel
Multi-Cloud / Heterogeneous ASNAS24940 (Independent VPS (Non-Cloudflare))ONLINEJust now
Multi-ASN Quorum: 4 of 7 sovereign edge regions (2 of 3 on Initiate free tier) plus independent ASN verification must confirm a failure before an incident opens. All probe nodes across Cloudflare and independent ASN sentinels are currently healthy and participating in active quorum.

Allowlist our probes

Our synthetic probes originate from Cloudflare Durable Objects. Because serverless edge runtimes egress via Cloudflare's shared global edge IP pool, IP allowlisting is neither deterministic nor secure. Instead, configure your WAF or reverse proxy to match on our cryptographic CF-Worker: steadystack.dev header and verified User-Agent.

WAF Allowlist Configuration Spec
# 1. Cloudflare WAF Custom Rule (Recommended)
# Our synthetic probes run as Cloudflare Durable Objects.
# Subrequests include an authentic, un-spoofable CF-Worker header.
#
# Match Expression:
(http.request.headers["cf-worker"][0] eq "steadystack.dev")
# Action: Skip / Bypass WAF & Rate Limiting

# 2. General WAF & Reverse Proxy Headers (Fastly / AWS WAF / Nginx)
CF-Worker: steadystack.dev
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36
/api/locations

Coverage we don't have

Africa, the Middle East, and parts of Central / South Asia. While our 7 sovereign edge regions cover North America, Europe, Asia-Pacific, Oceania, and South America, we do not currently operate dedicated edge probe workloads in Africa or the Middle East — so we don't claim them.

What this means practically: a genuine outage still pages you, because your endpoint will fail from all regions regardless of where it's hosted. What we'd miss is a localized routing issue affecting only users in those unprobed regions — such as a Johannesburg or Dubai transit route anomaly. If that's a real risk for your traffic, tell us; it moves our roadmap, and we'll say so here when it ships.

When a probe goes bad, we say so

A monitoring probe with a bad network path reports failures that aren't real — the industry's most common source of false alarms. Any probe with three or more state transitions in two hours is marked Flapping and automatically removed from quorum until it stabilises.

Every probe also reports on a heartbeat channel separate from its measurement path, so a probe that's blocked is distinguishable from one that's crashed. All of it is visible above, in real time, including when it's our fault.