> ## Documentation Index
> Fetch the complete documentation index at: https://docs.happyuptime.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Multi-region monitoring

Detect regional outages without tripping on isolated network glitches.

# Multi-region monitoring

Single-region monitors lie. They can't tell the difference between a global outage and a Virginia-specific routing issue.

Multi-region monitors run from N regions in parallel. The status only flips to `down` if **every** region fails. If only some fail, the monitor is `degraded` and the alert lists which regions saw the failure.

## Picking regions

Default for new monitors: `["us-east"]`. Update via `regions: [...]` on create or update.

| Region code | Datacenter |
|---|---|
| `us-east` | Ashburn, VA |
| `us-west` | San Jose, CA |
| `eu-west` | London, UK |
| `eu-central` | Frankfurt, DE |
| `ap-southeast` | Singapore |
| `ap-northeast` | Tokyo, JP |

Free tier: max 3 regions per monitor. Pro+: all 6.

## Aggregation

For each round of checks, the per-region results aggregate:

| Per-region | Aggregated |
|---|---|
| All `up` | `up` |
| 1+ `down` or `degraded`, not all | `degraded` |
| All `down` | `down` |

## Tuning to your audience

**Global SaaS**

Use all 6. The cost is overlap (you'll see brief regional glitches as `degraded`), but you catch every regional outage.

  **US-only**

`us-east` + `us-west` is plenty. Adding EU/AP regions creates noise from network glitches in regions you don't serve.

  **Internal API on a corporate VPN**

Multi-region won't work — only one region has VPN access. Use [heartbeat monitoring](/guides/heartbeat-cron) for self-reported health, or skip multi-region entirely.

  **EU-only with GDPR concerns**

Use `eu-west` + `eu-central` only. No US/AP probes touch your endpoint.

## Reducing flap

Multi-region monitors will sometimes flicker between `up` and `degraded` due to short-lived network blips in one region. Two ways to reduce noise:

1. Increase `confirmation_period_s` on the monitor — wait N seconds of consistent results before flipping state.
2. Drop regions you don't really need.