Regions

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

One region on each of five continents. Africa is next. More are added as they come online, and this table is updated when they do.

Region	Location	Continent
virginia	Northern Virginia, United States	North America
saopaulo	São Paulo, Brazil	South America
frankfurt	Frankfurt, Germany	Europe
singapore	Singapore	Asia
sydney	Sydney, Australia	Oceania

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. Regions on different continents share less infrastructure, so their agreement means more. Three regions is the recommended baseline, and the Free plan allows three per monitor.

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.

Pick the ones that matter. Every region you add is another check per interval. Choose the continents your customers are on rather than all of them by default.

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.