Probes from six continents
Checks run from regions across North America, Europe, Asia-Pacific, South America, and beyond — all simultaneously, every interval.
Run checks simultaneously from regions across six continents — so you always know whether a failure is real or just a bad hop in one ISP's backbone, before any alert fires.
A single probe from one data center tells you almost nothing. Checks from a dozen independent vantage points tell you whether users in Frankfurt, Singapore, and São Paulo can actually reach your service right now.
Checks run from regions across North America, Europe, Asia-Pacific, South America, and beyond — all simultaneously, every interval.
Pin each monitor to the regions that matter for its audience. A regional service doesn't need probes from every continent.
An alert only fires when a configurable number of regions agree on failure. One bad path never wakes your team.
Response times from each vantage point are shown side by side — spot geographic outliers before they become user complaints.
Route alerts to the on-call closest to the affected region, or notify everyone the moment a global outage is confirmed.
Set how many regions must fail before an incident opens — tighter for critical paths, relaxed for edge endpoints.
A routing issue between one probe and your origin looks nothing like a real outage. When checks from Frankfurt, Singapore, and Virginia all fail simultaneously, that's a confirmed incident — and you'll know immediately.
Regions are checkboxes in the monitor configuration. Change them any time without touching code, redeploying agents, or opening a support ticket. The REST API exposes the same controls for automation.
independent probe regions across six continents
agents or infrastructure for you to manage
minimum check interval across all active regions
of failures confirmed by quorum before alerting
We run probes from 12+ globally distributed regions spanning North America, Europe, Asia-Pacific, South America, and beyond. The exact region list is visible in your monitor configuration.
Yes — regions are a per-monitor setting. If your service is only used by European customers, there's no reason to alert on a latency spike from Sydney. Select only the regions that matter for each endpoint.
You configure the minimum number of regions that must independently detect a failure before an incident is opened. This prevents a single degraded probe or regional routing hiccup from creating noise.
Yes. The monitor detail view shows a per-region latency timeline so you can track response times from each vantage point independently — useful for diagnosing geographic performance issues before users notice.
Multi-region checks are included in all plans. Higher plans unlock more concurrent regions per monitor. The free tier lets you activate up to three regions per monitor.
Every product starts free — uptime, cron, synthetic, logs, RUM, incidents, and status pages. No credit card required.