Turn checks into incident context
Monitoring from Multiple Locations
Location-aware monitoring helps teams understand whether an incident is global, regional, or tied to one monitoring source.
How it helps
Use monitoring locations when protected systems need source IP allow-lists or when network path context matters.
The public monitoring locations page lists active monitoring source locations and IP addresses so SaaS teams can prepare access rules.
Location context pairs well with HTTP, ping, and port checks to make regional failures easier to classify.
Works well with
HTTP Monitoring
Monitor API and website endpoints with latency, method, header, body, auth, and status-code validation.
Ping Monitoring
Track host reachability and network path stability with lightweight checks.
Monitoring Locations
Review public monitoring source locations and IP addresses for allow-lists.