Cloudflare integration

Integrations → Cloudflare. A connected Cloudflare account does three things: it keeps your Cloudflare rules from blocking or challenging our probes, it verifies the account's zones as your domains, and it creates monitors from the zone list.

Connecting

Connect with Cloudflare: you sign in at Cloudflare and approve access to IP lists, WAF rules and your zone list, nothing else. Or use an API token created in Cloudflare under My Profile → API Tokens → Create Custom Token, with exactly these permissions: Account · Account Filter Lists · Edit, Zone · Zone WAF · Edit and Zone · Zone · Read, for your account and for all its zones or only the ones you want. If you only want the IP list, the first permission is enough. The token is stored encrypted and never shown again; replace or delete it at any time. A token that can see several accounts asks you which one.

Letting the probes through

Cloudflare rules can challenge or block our probes, which would show a site as blocked instead of up or down. The connection keeps an IP list named pingwise_probes in your account, updated whenever our fleet changes. Then either:

• you select zones, and in each we add one custom rule above your own, «PingWise probes: skip challenges»: requests from our probe addresses that identify as PingWise-probe/ skip the remaining custom rules, rate limiting, managed rules and Super Bot Fight Mode. Your rules stay exactly as they are; we only add, update or remove this one, and unselecting a zone removes it; or
• you use the list in a rule of your own (ip.src in $pingwise_probes) and we add nothing.

Sync now re-reads the zones and re-applies the rule; a token that stops working is flagged on the page, with your list and rules left in Cloudflare.

Verifying domains

Every active zone of the connected account can be verified as a domain in one click from Domains → Cloudflare, with no TXT record or file. Verification is what unlocks the faster intervals and the custom checks, see Domain verification.

Creating monitors from zones

On the connection's page, Create monitors (or the Cloudflare zones card under Monitors → Import) opens the usual import preview: one HTTPS monitor per zone apex, plus www where it resolves (ticked by default), in a group named «Cloudflare · » or any you pick, at our default interval or one you choose. The monthly credits and the outlook are shown before anything is created, and zones that are already monitored here are unticked. Zones that are paused, still pending (name servers not switched) or without an A, AAAA or CNAME record at the apex are listed with the reason and skipped; the lookups go through public resolvers, so the token needs no DNS permission. Verify these domains through Cloudflare, on by default, verifies the ticked zones first. New zones are not picked up on their own: run it again. There is no 14-day comparison for this source.

Last change: 7 November 2026.