Probe locations, IPs & allowlisting

When you need this

Bot-management services (Cloudflare, Akamai, DataDome, AWS WAF and similar) sometimes answer our checks with HTTP 403 or an empty challenge page. When that happens we mark the check blocked — never as downtime — and once every probing region is refused, the monitor shows a Limited monitoring banner: your site is clearly alive, but we can no longer verify it. Blocked checks are excluded from uptime and never trigger alerts. Allowlisting restores full coverage.

You only need the rows for the region your monitor is hosted in — a monitor in our EU West region is probed only from the EU West cities below.

Allowlist by User-Agent

The quickest fix: allow these User-Agent strings in your WAF or bot-management rules.

• Uptime-Monitor/1.0
• Uptime-Monitor-Content/1.0
• Uptime-Monitor-Dependency/1.0

Allowlist by IP address

Our probes use static egress addresses per city. These addresses are stable — they survive infrastructure changes on our side — and this page is the canonical list.

US East

EU West

Asia Pacific

Any row marked provisioning is being assigned a static address and temporarily probes from our platform's shared address pool. Check back after infrastructure changes.

How to request unblocking

1. If you manage the WAF yourself: add a rule allowing the User-Agents or IPs above, scoped to the URL path we check.
2. If a vendor manages it (Cloudflare, Akamai, DataDome, hosting provider): send them this page and ask them to allowlist "FlareWarden uptime monitoring probes".
3. Prefer path-scoped rules over global ones — we only need to reach the exact URL your monitor checks.

Once the rules are in place, monitoring recovers on its own: the first successful check clears the Limited state and full verification resumes — no action needed in FlareWarden.