Better Stack: IPs & Locations

The list at uptime.betterstack.com/ips.txt is the canonical source and changes infrequently. Better Stack recommends fetching it programmatically if you automate firewall rules.

Yes — the official list contains both IPv4 and IPv6 addresses, and checks can be performed over both protocols. Whitelist both if your infrastructure is dual-stacked.

Better Stack confirms incidents from multiple regions before alerting. If some probes are blocked, you get false incidents or delayed confirmations. Whitelisting the full list keeps the confirmation logic reliable.

Both — wherever requests can be blocked. If your site sits behind a CDN or WAF (Cloudflare, AWS WAF, Akamai…), add an allow/skip rule there so probes are never challenged; if your origin firewall also filters traffic, whitelist them there too. A single missed layer is enough to cause false alerts.

Most providers expose a machine-readable source (linked above). Fetch it on a schedule — a small cron job that pulls the list and updates your firewall ruleset — instead of hardcoding addresses by hand. This page is re-verified against the official source regularly, but automation on your side is the most reliable option.

No. Allow-listing only exempts known monitoring addresses from blocking and rate-limiting rules — it grants no access beyond what your site already serves publicly, and authentication, authorization, and TLS are unchanged. You are simply telling your firewall "these are not attackers".

A blocklist keeps known-bad addresses out; an allow/whitelist makes sure known-good addresses — here, the monitoring probes — never end up caught in a block or rate-limit rule. The two coexist: you keep blocking attackers while explicitly exempting the probes.