Cloudflare Verified Bot status

Please apply to Cloudflare's Verified Bots program so Uptime.com probe traffic is recognized as a verified bot.

Why Uptime.com is a strong candidate

Cloudflare's Verified Bot designation exists for non-malicious automated agents that honestly self-identify and demonstrate non-abusive behavior. Uptime.com already meets Cloudflare's published criteria:

• Self-identifying user agent — probes send Mozilla/5.0 … Uptime/1.0 (https://uptime.com), which is unique to Uptime.com and free of special characters.

• Publicly documented behavior — probe server IPs, locations, and user agents are documented in Uptime.com's support portal and exportable from the dashboard.

• Traffic volume and breadth — Uptime.com far exceeds the 1,000-requests-per-day-across-multiple-domains threshold, monitoring many zones for many customers rather than crawling a single site.

• Predictable, non-abusive patterns — scheduled checks at customer-defined intervals against customer-owned endpoints.

The problem this solves for customers

Without verification, Uptime.com probes are scored as automated traffic by Cloudflare Bot Management and are blocked or challenged by standard bot rules. Because a synthetic probe cannot solve a Managed Challenge, this surfaces as false downtime alerts — the check fails for reasons unrelated to the monitored service.

The current workaround requires every affected customer to:

1. Export the probe-server list and maintain it as a Cloudflare IP List — in our environment that's 322 addresses across 149 probe servers.

2. Re-sync that list whenever Uptime.com adds or changes probe servers.

3. Configure a custom secret header on every individual check.

4. Author and maintain skip rules in every zone and at the account level, correctly ordered ahead of all bot and rate-limiting rules.

That's brittle, easy to get subtly wrong, and has to be rebuilt by each customer independently.

Impact

Verified Bot status eliminates all of it. Cloudflare's standard bot rules already exclude verified bots by default, so customers would get both working monitoring and full bot protection with no custom configuration. It would also remove a recurring class of Uptime.com support tickets caused by edge security rather than by the monitored service.

How to apply

Cloudflare accepts submissions in the dashboard under Manage Account → Configurations → Bot Submission Form.

Sources: Verified bots · Verified Bots Policy · Allow traffic from verified bots