Skip to main content
PulseGuard runs checks from 50 probe locations spread across North America, Europe, Asia Pacific, South America, Africa, and the Middle East. When you assign multiple regions to a monitor, each location runs the check independently and reports its own result and latency. This gives you a real-time view of your service’s availability from the perspective of users in every geography you care about.

​
Why Multi-Region Monitoring Matters

A service can be down in Tokyo while remaining fully operational in New York. Without regional probes, a monitoring system that checks from a single location either misses that regional outage entirely or — if it happens to probe from the affected region — fires a false global alert. PulseGuard solves both problems.

Detect regional failures

PulseGuard tracks failures per region independently. A DOWN result in ap-northeast-1 doesn’t mask a UP result in us-east-1 — you see the full picture.

Suppress false global alerts

PulseGuard requires a majority of your selected regions to report DOWN before declaring a global outage, preventing a single flaky probe from waking your on-call team.

Latency heatmaps

Response times are recorded per region and visualised as a global latency heatmap on your monitor detail page.

Regional incident tracking

Regional incidents are tracked separately from global incidents, giving you granular incident history without noise.

​
Configuring Check Regions

Set the checkRegions field on any monitor to a JSON array of region codes. When checkRegions is omitted, PulseGuard uses its default single-probe behaviour. When you provide one or more region codes, all selected regions run the check in parallel on every scheduled tick.
Start with three to five geographically distributed regions that represent your primary user segments. You can always add more regions later without any downtime or data loss.

​
Alert Threshold with Multi-Region Checks

When multi-region checking is active, PulseGuard automatically adjusts the alert threshold to use the higher of your configured alertThreshold value or 50% of your selected regions. This means that even if alertThreshold is set to 1, a single failing region among five selected regions will not trigger a global incident.
If you deliberately want to alert on a single regional failure — for example, you have a critical presence in one specific region — create a separate monitor scoped to that region alone with a low alertThreshold.

​
Available Regions

​
North America

​
Europe

​
Asia Pacific

​
South America

​
Africa

​
Middle East

​
Example: Global Coverage Configuration

The following YAML example configures a single API monitor with probes in six strategically distributed regions covering every major inhabited continent.

Overview

Full monitor configuration reference including the checkRegions field.

Monitor Types

Choose the right monitor type for your use case.

Assertions

Validate response content from every region.