Help
Monitoring IPs
Allow these source addresses if a firewall or WAF is blocking RanchAlerts, or if one city looks down while others do not. After you sign in, Help → Guides → Firewalls & False Alerts has the longer walkthrough.
RanchAlerts checks your public websites and hosts from several cities in the United States and Canada. Most firewalls already allow this. If one city reports down while others stay up, or you see blocks from “unknown scanners,” your firewall, WAF, or host may be treating our pollers as untrusted traffic.
Allow inbound traffic from the IPv4 addresses below to the ports you asked us to watch (HTTP 80/443, ICMP echo for PING, and any TCP port on a Port Monitoring check). A down alert still waits for other healthy cities to confirm when three or more pollers are live, so allow every city on this list, not only your primary location. Heartbeat monitors do not use these addresses — your job visits RanchAlerts instead.
RanchAlerts sends HTTP GET only. We do not post bodies, set custom headers, or follow redirects until the next hop is also a public address.
| City | IPv4 |
|---|---|
| Oregon (ORE) | 40.160.138.212 |
| Los Angeles (LAX) | 107.174.50.234 |
| Denver (DEN) | 216.120.201.127 |
| Dallas (DTX) | 23.230.253.124 |
| Chicago (CHI) | 104.168.125.44 |
| Atlanta (ATL) | 107.175.115.80 |
| Miami (MIA) | 89.106.84.202 |
| New York City (NYC) | 192.255.249.106 |
| Toronto (TOR) | 69.12.83.70 |
IPv4 list
One address per line. Comment lines in the download start with #. You can share the public page with a firewall administrator who does not have a RanchAlerts login: portal.ranchalerts.com/help/monitoring-ips/
When to allow-list
- You do not need to change anything if checks already look correct from every city.
- A false down from one city, with others still up, often means that city’s address is blocked or challenged.
- Cloud WAFs and “bot fight” features sometimes challenge datacenter IPs. Skip the challenge for these addresses, or allow GET without a JavaScript wall. After you sign in, Help → Guides → Firewalls & False Alerts covers Windows, Linux, Cloudflare, Imperva, AWS, and Azure.
- Do not point a TCP check at a port you intentionally block (for example a database port) unless you also allow these IPs to that port. Otherwise every city will look down.
- PING needs ICMP echo allowed from these addresses. Blocking ICMP only hides PING; HTTP and TCP checks still run.
- This list is IPv4 only today. If we replace a poller, the address on this page is the one to trust.