Probe IPs
Where our checks come from.
Every request from PingWise comes from one of these addresses and identifies itself in the User-Agent. If you see us in your logs and didn't ask to be monitored, write to abuse@pingwise.com.
Loading the live list…
- user-agent
- PingWise-probe/1.0 (+https://pingwise.com/probes)
- json
- /probes.json
- ipv4 list
- /probes/ipv4.txt one per line
- ipv6 list
- /probes/ipv6.txt one per line
- opt out
- Don’t want to be checked by us? Write to abuse@pingwise.com with your IP or domain. We stop every monitor against it and block new ones.
- changes
- Announced by email to every account 14 days before an address is added or removed.
- protocols
- HTTP, HTTPS, TLS, TCP, SMTP, DNS and ping (ICMP), over IPv4 and IPv6.
- rate
- One check per monitor per interval: every 15 seconds at most for verified domains, every minute otherwise. A global cap per hostname and per IP across all accounts.
Behind Cloudflare
Let the probes through.
The easy way: in your PingWise panel, open Cloudflare and connect your account with a token limited to IP lists and WAF rules. We create the list and the skip rule in each zone you pick and keep them current. The manual way is below.
An IP Access rule set to “Allow” does not skip a managed challenge from a WAF custom rule. Use a skip rule instead.
- In Cloudflare, go to Manage account → Configurations → Lists and create an IP list named uptimebox_probes from /probes/ipv4.txt and /probes/ipv6.txt.
- In your zone, open Security → WAF → Custom rules and create a rule at the top of the list.
- Expression below, action Skip, and tick every remaining custom rule, rate limiting, managed rules and Super Bot Fight Mode.
(ip.src in $uptimebox_probes and http.user_agent contains "PingWise-probe/")
Until the rule is in place, a Cloudflare challenge shows as blocked in your dashboard, never as down.