Skip to content
Glowo
Esc
↑↓navigate↵open⌘Jpreview
On this page

Regions

Where Glowo checks from, how multi-region checks are scheduled, and how regions affect false alarms.

Glowo runs checks from these regions:

CodeLocationDefault
graGravelinesYes
cdgParisYes
lhrLondonYes
iadAshburn
laxLos Angeles
nrtTokyo
sinSingapore
gruSão Paulo
sydSydney

A monitor whose regions you have not chosen checks from the regions marked Default: on Free that is every monitor, while Pro and Business can choose their own. The default regions span more than one independent network, so Glowo can tell an outage from a problem on one network’s path.

Why more than one region matters

A single-region check cannot distinguish “the service is down” from “the path between one probe and the service is down”. Transit problems, regional routing issues and localised DNS failures all look identical to one observer.

With several regions, that ambiguity disappears: if every other region sees the service and one does not, the problem is on that path — which is real information, and not usually a reason to wake anyone.

Region strategies

Strategy Behaviour
all Every selected region checks on every interval.
round_robin One region at a time, moving to the next region in the selection about every 15 minutes, and whenever the monitor is edited or resumed.
random One region at a time, picked at random from the selection about every 15 minutes, and whenever the monitor is edited or resumed.

all gives the fastest, most confident detection, and uses the most checks. It is the right default for anything customer-facing.

round_robin and random spread coverage across regions at the cost of one observation per interval. They suit lower-priority monitors where you want geographic coverage over time rather than consensus right now. While one of the selected regions is unavailable, they check from the others until it is back.

Choosing regions

Pick regions where your users are, plus one far away. Two regions on the same continent tend to share transit and fail together, which is exactly the correlation you were trying to avoid.

If your service is only reachable from certain networks, check from regions that can actually reach it — or use a push monitor driven from inside the network instead.

Status across regions

With all, Glowo aggregates the per-region results into one monitor status. Each region’s own result is kept, so a monitor’s history shows which regions saw the failure — usually the fastest way to tell a real outage from a routing problem.

By default the monitor becomes DOWN once most reporting regions confirm the failure. When those regions span more than one independent network, the failure must be seen from at least two of them: a failure that only regions sharing one network see, while another network still reaches the service, leaves the monitor DEGRADED. With regionsDownPolicy set to any or all, the number of failing regions alone decides.

Was this page helpful?