What it is
A region is a location your checks run from. Every probe runs from at least one region. Run it from several and you learn something a single location can’t tell you: whether an outage is global or just regional, and how fast your service responds from each part of the world.
If your site is unreachable from Europe but fine from the US, one region checking from each shows you that split the moment it happens, instead of leaving you guessing why some users report problems and others don’t.
Where checks run from
Checks currently run from:
- Seattle, USA
- Nuremberg, Germany (Europe)
More locations are being added over time. The regions you can pick appear in the probe form, so the list there is always current.
Choosing regions
When you create a monitor, pick the regions it should run from. Each region runs the full check on your chosen interval and reports its own results.
Every region counts as one monitor against your plan’s limit. A check running from three regions uses three of your monitors. This works the same on every plan, so pick the regions that matter and pay only for what you use.
Reading per-region results
Each region runs and reports independently, with its own status, uptime, and response times. On the monitors list, a check running from several regions groups its regions together so you can see them at a glance.
Open a region to see its history in full. Comparing regions tells a local problem (one region down, the rest up) from a global one (every region down), and shows how latency differs between locations.
Next steps
Add a probe and choose its regions from the probe form. New to probes? Start with the HTTP, TCP, or Domain guide, or see how a probe’s state is worked out in Probe statuses.