Docs/Regions
Regions
Public monitors run from one or more regional probes. Each region runs its own independent schedule against your monitor; if one region sees a failure, an incident opens with that region attached to the cause.
| ID | Location |
|---|---|
us-east | United States |
eu-west | Germany |
eu-north | Sweden |
ap-southeast | Singapore |
as-east | Japan |
me-west | UAE |
af-south | South Africa |
sa-east | Brazil |
oc-southeast | Australia |
Choosing regions
- One region — fine for staging, internal dashboards, anything where you just want to know it's reachable somewhere.
- Multiple regions — production. Lets you distinguish a global outage from a regional network blip, and surfaces issues like a CDN POP misbehaving.
- Default —
us-eastif you don't pick.
Each selected region multiplies the number of checks counted toward the monitor's interval — a 60s check from 3 regions runs every 20s on average from one of them, but each individual region still checks every 60s.
What region selection doesn't do
- It doesn't apply to DNS monitors — DNS resolves from a single location today.
- It doesn't apply to Lighthouse-bound monitors — those run from your agent inside your network. See Lighthouse.
Network paths
All regional probes egress from datacenter ranges. If your service allow-lists IPs, contact us for the current egress list — the set isn't published as a stable contract because we add and rotate regions.