Location Reference
Complete technical specification for Location monitoring
statusas monitors your endpoints from two kinds of place: hosts we run ourselves, and Cloudflare's edge. Hosts of our own have a fixed outbound address you can allowlist; Cloudflare regions do not, because a Cloudflare request can leave from any of its datacentres.
You can use these locations to:
- Configure region-specific checks.
- Allowlist monitoring IPs in your firewall.
- Understand where requests originate during synthetic monitoring.
Two forms of the same region code
The same probe is addressed by a different spelling depending on the surface you are using:
| Surface | Form | Example |
|---|---|---|
| Dashboard, CLI, Terraform provider, REST API | bare code | vno, fra, cf_weur |
| ConnectRPC API and the SDKs | the protobuf enum value | REGION_VNO, REGION_FRA, REGION_CF_WEUR |
The enum value is the bare code upper-cased with REGION_ prepended — with one exception:
Kaunas is kun everywhere except the enum, where it is REGION_KAUN.
The SDKs expose the enum as a generated constant rather than a raw string — Region.VNO in
the Node.js SDK, Region::REGION_VNO in PHP — so you rarely type the value out.
Our own hosts
One machine per region. These are the regions you can allowlist by IP.
| Region code | Location name | Country |
|---|---|---|
vno | Vilnius | 🇱🇹 Lithuania |
kun | Kaunas | 🇱🇹 Lithuania |
waw | Warsaw | 🇵🇱 Poland |
fra | Frankfurt | 🇩🇪 Germany |
ams | Amsterdam | 🇳🇱 Netherlands |
Cloudflare regions
Cloudflare does not let anyone pick a datacentre, only a broad location hint, so these are hints rather than cities — naming them after airports would promise a precision Cloudflare does not offer.
| Region code | Location name |
|---|---|
cf_weur | Western Europe |
cf_eeur | Eastern Europe |
cf_enam | Eastern North America |
cf_wnam | Western North America |
cf_apac | Asia-Pacific |
cf_oc | Oceania |
cf_sam | South America |
cf_afr | Africa |
Allowlisting monitoring traffic
Cloudflare regions have no static address. If you allowlist by IP, use Cloudflare's published IP ranges, or pick a region of ours instead.
Our own hosts check from a fixed address:
| Region code | IPv4 | IPv6 |
|---|---|---|
vno | 185.170.198.15 | 2a02:4780:c:730f::1 |
A region of ours that is not in the table above is not yet serving public checks. The dashboard's region picker shows what your workspace can select today.
A sturdier alternative to an IP allowlist: give the monitor a secret header and match on that instead. Addresses change; a header you chose does not.
Note: Location names are for reference and may be used in the dashboard UI.