Probe IP addresses
Uptime Room checks your endpoints from the regions below. If a firewall, WAF or rate limiter sits in front of a monitored target, allow these addresses so checks are not blocked and counted as downtime. The same list is available as JSON from GET /api/regions (egress) - poll it from automation; it is cached for five minutes.
| Region | Code | Egress IP | Additional ranges |
|---|---|---|---|
| 🇺🇸 Los Angeles, United States | los-angeles | 45.63.62.128 | - |
| 🇧🇷 São Paulo, Brazil | sao-paulo | 216.238.124.242 | - |
| 🇮🇳 Bangalore, India | bangalore | 139.84.152.107 | - |
| 🇬🇧 London, United Kingdom | london | 95.179.200.36 | - |
| 🇸🇬 Singapore, Singapore | singapore | 149.28.157.59 | - |
| 🇦🇺 Sydney, Australia | sydney | 108.61.185.132 | - |
Identifying our requests
Checks arrive from the addresses above with the method, headers and body you configure on the monitor (set a custom header such as X-Uptime-Room: 1 if you want to recognise them). Heartbeat monitors are the reverse: your job pings us, so nothing needs allow-listing. See the API reference for the monitor fields.