Skip to content

Monitoring from Multiple Locations

WebGuard compares fresh results from every configured location, helping teams avoid false-positive incidents while still identifying regional and global outages.

Get StartedAll features
Monitoring from Multiple Locations — WebGuard

At a glance

  • A single-location failure stays a localized degradation without opening an incident
  • A strict majority of fresh failing results opens a regional incident
  • Unanimous failure classifies the incident as global

How it helps

Every configured monitoring location contributes its latest fresh result. One failed probe remains visible in the per-location status matrix, but it does not create an incident by itself.

More than half of the fresh location results must fail before WebGuard opens a regional incident. If every location fails, WebGuard classifies the incident as global.

A majority recovery closes the incident. The public monitoring locations page also lists active source locations and IP addresses for allow-lists and network-path context.

Frequently asked questions

What is Monitoring from Multiple Locations?

WebGuard compares fresh results from every configured location, helping teams avoid false-positive incidents while still identifying regional and global outages.

Who is Monitoring from Multiple Locations for?

Every configured monitoring location contributes its latest fresh result. One failed probe remains visible in the per-location status matrix, but it does not create an incident by itself.

What does Monitoring from Multiple Locations provide?

A single-location failure stays a localized degradation without opening an incident A strict majority of fresh failing results opens a regional incident Unanimous failure classifies the incident as global