Multi-Region Monitoring
Run uptime checks from multiple global regions to detect region-specific outages and compare response times.
Multi-Region Monitoring
A service can be down in one part of the world while running perfectly in another. Multi-region monitoring lets you detect these localized outages by running checks from multiple geographic locations simultaneously.
Monitoring regions
Seenty operates monitoring probes in three regions:
| Region | Location | Identifier |
|---|---|---|
| South America | Sao Paulo, Brazil | sa-east-1 |
| North America | Virginia, USA | us-east-1 |
| Europe | Paris, France | eu-west-3 |
Each check runs from all selected regions in parallel. A monitor is only considered down if the check fails from all selected regions for the configured number of consecutive failures. This design reduces false positives caused by localized network issues between a single probe and your server.
How regions work per plan
| Plan | Region behavior |
|---|---|
| Hobby | Checks run from a single default region (Sao Paulo) |
| Starter | Checks run from a single default region (Sao Paulo) |
| Pro | Select one or more regions per monitor |
| Ultra | Select one or more regions per monitor |
| Enterprise | Select one or more regions per monitor |
Custom location selection is available on Pro plans and above. Hobby and Starter monitors run from the default region.
Selecting regions for a monitor
When creating or editing a monitor on a Pro+ plan:
- Open the monitor configuration
- In the Regions section, toggle the regions you want to check from
- Save the monitor
You can select any combination -- a single region, two regions, or all three. More regions give you better coverage but each region runs an independent check, so the total number of checks per interval equals the number of selected regions.
Response time comparison
The monitor detail view shows response time charts broken down by region. This lets you:
- Compare latency across regions -- See if your service is slower for users in Europe versus South America
- Identify CDN or routing issues -- Spot cases where one region consistently has higher latency
- Track performance trends -- Watch how response times change over time in each region
Each region's response time is plotted as a separate line on the chart, color-coded by region.
Region-specific outages
When a monitor fails from one region but succeeds from others, Seenty treats this differently from a full outage:
- If the check fails from all selected regions for the configured threshold, the monitor is marked as down and an alert is triggered
- If the check fails from some but not all regions, the monitor remains up but the failing region is flagged in the check log
This behavior ensures you are only alerted for genuine outages, not transient routing issues between a single probe location and your server.
Best practices
- Select all three regions for production services to maximize outage detection coverage
- Use a single region for internal or development services where global availability is not a concern
- Review per-region latency regularly to identify performance regressions before they affect users
- Consider your user base -- if your users are primarily in one region, pay special attention to response times from the nearest probe location