Location Reference

statusas monitors your endpoints from multiple global locations to ensure accurate uptime and latency reporting. Locations span several infrastructure providers (Fly.io, Railway, and Koyeb), so IP availability varies: Fly.io regions expose both IPv4 and IPv6 addresses, Railway regions are IPv4-only, and Koyeb does not provide static IPs.

You can use these locations to:

• Configure region-specific checks.
• Allowlist monitoring IPs in your firewall.
• Understand where requests originate during synthetic monitoring.

Three forms of the same region code

The same probe is addressed by a different spelling depending on the surface you are using:

The SDKs expose the enum as a generated constant rather than a raw string — Region.FLY_IAD in the Node.js SDK, Region::REGION_FLY_IAD in PHP — so you rarely type the value out.

Pick whichever form the surface you are using expects. The tables below list the bare and prefixed codes; the enum value is the prefixed code upper-cased with - replaced by _ and REGION_ prepended.

Fly.io regions and monitoring IPs

Below is the complete list of regions used for monitoring, along with their associated IPv4 and IPv6 addresses.

Railway regions and monitoring IPs

Below is the complete list of Railway regions used for monitoring, along with their associated IPv4 addresses.

Koyeb regions

Koyeb does not provide static IP addresses for their regions, so IPs are not available for allowlisting. For details, see Koyeb's documentation.

---

Note:

• Where available, IPv4 and IPv6 addresses are provided for allowlisting and diagnostics (Fly.io regions only; Railway is IPv4-only and Koyeb has no static IPs).
• Location names are for reference and may be used in the dashboard UI.