> ## 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.

# Regions

Six globally distributed check locations and how Happy Uptime aggregates their results.

# Regions

Every monitor runs from one or more of these check regions:

| Region | Location |
|---|---|
| `us-east` | Ashburn, Virginia |
| `us-west` | San Jose, California |
| `eu-west` | London, UK |
| `eu-central` | Frankfurt, Germany |
| `ap-southeast` | Singapore |
| `ap-northeast` | Tokyo, Japan |

Pick regions when you create the monitor (`regions: ["us-east", "eu-west"]`). Free plan allows 3 regions; Pro/Team allow all 6.

## How status aggregates across regions

After each round of checks the results are aggregated into one of three states:

| Result per region | Aggregated status |
|---|---|
| All regions report `up` | `up` |
| At least one region reports `down` or `degraded`, not all | `degraded` |
| All regions report `down` | `down` |

Status changes still go through the confirmation period (default 2 consecutive identical checks) before they trigger alerts or auto-create incidents.

## Why multi-region matters

Single-region checks lie. A monitor that only runs from `us-east` will flag a global outage **and** a Virginia-specific routing issue with the same severity. You can't tell whether your customers are affected.

  With multi-region, an outage that affects Singapore but not Virginia shows as `degraded` and the alert says exactly which regions failed.

## Region in alerts and incidents

- Alert payloads include the region(s) that observed the failure.
- Auto-created incidents have severity inferred from the failed-region count: 1 region failed = `minor`, some failed = `major`, all failed = `critical`.
- Status page incidents show the affected regions in the title and timeline.

## Picking the right regions

**My users are global**

Use all 6 regions. Catches regional outages from any major cloud provider.
  **My users are US-only**

`us-east` + `us-west` is enough. Adding EU/AP regions just creates noise from network glitches in regions you don't serve.
  **Internal API on a private network**

Only one region with VPN/private connectivity will succeed — pick that one and turn off the others. Or use [heartbeat monitoring](/guides/heartbeat-cron) for self-reported health.