Monitors

Regions

The 18 regions StatusCheck probes from, and how to choose them.

StatusCheck runs an independent probe in each of the regions below. Every check result is stamped with the region it ran from, and that region is never inferred or overridden. What you see in the dashboard is where the check actually ran.

Available regions

Region	Location	Area
`sanfrancisco`	San Francisco, United States	Americas
`california`	Northern California, United States	Americas
`virginia`	Northern Virginia, United States	Americas
`nyc`	New York City, United States	Americas
`toronto`	Toronto, Canada	Americas
`saopaulo`	São Paulo, Brazil	Americas
`london`	London, United Kingdom	Europe
`paris`	Paris, France	Europe
`frankfurt`	Frankfurt, Germany	Europe
`amsterdam`	Amsterdam, Netherlands	Europe
`tokyo`	Tokyo, Japan	Asia-Pacific
`seoul`	Seoul, South Korea	Asia-Pacific
`singapore`	Singapore	Asia-Pacific
`sydney`	Sydney, Australia	Asia-Pacific
`mumbai`	Mumbai, India	Asia-Pacific
`bangalore`	Bangalore, India	Asia-Pacific
`bahrain`	Manama, Bahrain	Middle East & Africa
`capetown`	Cape Town, South Africa	Middle East & Africa

Choosing regions for a monitor

At least two. Confirmation needs a second opinion. A monitor with one region will alert on that region’s own network problems.

Spread them out. Two regions in the same country share more infrastructure than two on different continents. Three regions across three continents is the recommended baseline.

Match your customers. Response times are measured from the probe, so a monitor probing from Sydney tells you what Australian users experience. Add the regions your customers are in, not just the ones near your servers.

Don’t add all 18 by reflex. More regions means more checks per interval, which counts against your plan’s check budget, and rarely adds signal beyond five or six well-spread regions.

Allowlisting probe traffic

If your target sits behind a firewall or a WAF, probes identify themselves with the User-Agent header StatusCheck/1.0 (+https://statuscheck.io), which is stable and is the supported way to allow our traffic through.

Private and internal addresses cannot be monitored from public regions. For services on a private network, use heartbeat monitors from inside the network instead.