--- title: X description: Allowlisting a monitoring service should not mean asking support for a list of addresses. A new IP ranges page lists every monitoring location by region with… canonical: https://watchfor.io/changelog/2026-07-16-monitoring-ip-ranges-bot --- [All updates](/changelog/page/8#2026-07-16-monitoring-ip-ranges-bot) ✨ New Jul 16, 2026 · v 4.0.1 # Published monitoring IP ranges and a bot info page Allowlisting a monitoring service should not mean asking support for a list of addresses. A new IP ranges page lists every monitoring location by region with IPv4, IPv6 and hostnames, plus machine-readable /ips.json, /ipv4.txt and /ipv6.txt endpoints you can pull on a schedule. A companion bot page explains how to identify and verify our requests, and every monitoring IP now has forward-confirmed reverse DNS. Every monitoring location with its addresses and hostname. Machine-readable lists to pull on a schedule. ## The problem it solves If your site sits behind a firewall, a WAF or a CDN with bot protection, monitoring requests can get blocked. Your monitor then reports the site as down while real visitors see it fine. Fixing that used to mean asking for a list of addresses and copying it by hand. ## What is published - [IP ranges](/ip-ranges) : every monitoring location, grouped by region, with its IPv4 and IPv6 addresses and hostname. - Machine-readable lists : [/ips.json](/ips.json) (with city, country and hostname for each address), [/ipv4.txt](/ipv4.txt) and [/ipv6.txt](/ipv6.txt) (one address per line). - [Bot page](/bot) : the exact User-Agent our checks send, what they do and do not do, and how to allowlist or block them. - Reverse DNS on every monitoring IPv4 address points to a hostname under probe.watchfor.io , and that hostname resolves back to the same address. ## Example Your firewall only lets known addresses reach the admin API. Instead of pasting addresses once and forgetting them, a nightly job pulls the current list: curl -fsS https://watchfor.io/ipv4.txt -o /etc/nginx/watchfor-ipv4.txt When a new location is added, your allowlist picks it up on the next run. To check that a request in your logs really came from us, run dig -x and then look up the hostname it returns. ## Where to find it The [probe locations guide](/docs/reference/probe-locations) has the full list and a step-by-step Cloudflare rule. Share this update --- Canonical page: https://watchfor.io/changelog/2026-07-16-monitoring-ip-ranges-bot · Site guide: https://watchfor.io/llms.txt