Skip to content

Multi-Region Monitoring

CheckOps runs every monitor from multiple regions simultaneously. This detects localized outages, CDN issues, and geographic performance degradation that single-region monitoring misses.

Code Location Provider
fr-par Paris, France OVH
fr-gra Gravelines, France OVH
de-fra Frankfurt, Germany ClearCloud
de-ber Berlin, Germany ClearCloud
nl-ams Amsterdam, Netherlands ClearCloud
be-bru Brussels, Belgium OVH
fi-hel Helsinki, Finland OVH
pl-waw Warsaw, Poland OVH

All OPS regions plus:

Code Location Provider
uk-lon London, UK OVH
es-mad Madrid, Spain OVH
it-mil Milan, Italy OVH
se-sto Stockholm, Sweden OVH
ch-zur Zurich, Switzerland ClearCloud
at-vie Vienna, Austria OVH
pt-lis Lisbon, Portugal OVH

Enterprise plans can request custom regions including non-EU locations.

Each check cycle dispatches the monitor to all selected regions in parallel. Results are aggregated with the following logic:

  1. All regions UP — Monitor status is UP
  2. Some regions DOWN — Monitor status is DEGRADED with region details
  3. All regions DOWN — Monitor status is DOWN

This prevents false positives from transient network issues in a single region.

The dashboard displays per-region response times in a heatmap view:

Region Latency Status
─────────────────────────────────
fr-par 42ms UP
de-fra 51ms UP
nl-ams 48ms UP
uk-lon 67ms UP
es-mad 89ms SLOW
it-mil 112ms SLOW

Regions where response time exceeds the response_time assertion threshold are flagged as SLOW without triggering a DOWN alert.

Select regions when creating or editing a monitor:

{
"url": "https://api.acme.com/health",
"regions": ["fr-par", "de-fra", "nl-ams", "uk-lon"],
"assertions": [
{ "type": "status_code", "operator": "equals", "value": 200 },
{ "type": "response_time", "operator": "less_than", "value": 2000 }
]
}

If no regions are specified, all regions available on your plan are used.

  • CDN verification — Ensure your CDN serves content consistently across Europe
  • DNS propagation — Detect stale DNS records in specific regions
  • Localized outages — Identify issues affecting specific geographic areas
  • Compliance — Verify data residency by checking responses from specific regions
  • Performance baseline — Compare latency across regions to identify optimization targets