What monitoring regions are available?
UpCanary checks your services from 6 global regions with multi-region consensus to eliminate false positives.
UpCanary runs monitor checks from 6 global regions simultaneously. This geographic distribution gives you accurate uptime data, global performance visibility, and protection against false positive alerts.
Available Regions
| Region | Location |
|---|---|
| US Central | Central United States |
| South America East | São Paulo, Brazil area |
| Europe West | Western Europe |
| Asia South | South Asia (India area) |
| Asia Northeast | Northeast Asia (Japan/Korea area) |
| Australia Southeast | Sydney, Australia area |
When creating or editing a monitor, you select which of these regions run each check. By default, all 6 regions are selected. You can deselect regions that aren’t relevant to your user base or infrastructure.
Multi-Region Consensus
Multi-region consensus is UpCanary’s mechanism for eliminating false positive alerts.
The rule is simple: an alert only fires when 2 or more regions independently confirm the service is down.
Here’s why this matters:
A single monitoring region might fail to reach your service for reasons that have nothing to do with your service being down:
- Temporary packet loss on a regional network path
- A CDN edge node having a brief issue
- A BGP routing hiccup between the monitoring location and your server
- Transient DNS resolution failure at one location
Without consensus, any of these would trigger a false alert - waking you up at 3am for a problem that self-resolved in seconds.
With consensus, UpCanary waits for corroboration. If only one region reports a failure while the other five succeed, the monitor stays green and no alert fires. Only when multiple regions agree does UpCanary conclude there’s a real outage.
Consensus in Practice
| Regions Reporting Down | Alert Fires? |
|---|---|
| 0 of 6 | No - all clear |
| 1 of 6 | No - likely a regional blip |
| 2 of 6 | Yes - confirmed outage |
| 3+ of 6 | Yes - widespread outage |
Per-Region Response Times
Every check records the response time from each region independently. On your monitor detail page you can see:
- Response time per region over time
- Which regions are currently passing or failing
- Regional performance trends
This is useful for identifying geographic performance problems - for example, if your US response times are fast but Asia Northeast is consistently slow, your CDN configuration or nearest origin server may need attention.
Credit Pricing Across Regions
1 credit = 1 check, regardless of how many regions run it.
There is no per-region surcharge. Running a check from all 6 regions costs exactly the same number of credits as running it from just 1 region.
This means you should default to using all regions - the multi-region consensus benefit is free, and you get broader geographic data at no extra cost.
Choosing Regions
Use all regions (default) for most monitors. The false-positive protection and geographic coverage are included at no extra credit cost.
Deselect regions only when you have a specific reason:
- Monitoring an internal service that’s only accessible from certain regions
- A service intentionally restricted to a specific geography (geo-blocking)
- Troubleshooting regional connectivity by comparing a subset of regions
Related Documentation
- Monitor Overview - All monitor types and region support
- Check Intervals & Credits - How regions affect credit consumption
- Alerts & Notifications - Multi-region consensus prevents false alerts
- Global Monitoring - Learn about UpCanary’s global infrastructure