Allow UptimeObserver on Cloudflare
Cloudflare may block or challenge automated monitoring requests. If your site works in a browser but UptimeObserver reports a failure, use this guide to identify the blocking feature and configure an exception.
Cloudflare verified bot
UptimeObserver is a Cloudflare verified bot and automatically signs HTTP checks with Web Bot Auth; you do not need to configure signing. Custom security rules and origin firewalls can still block checks. Follow the steps below if your monitor is affected.
1. Find the blocked check
- Note the failed check's URL, monitoring region, timestamp and timezone, and HTTP status from UptimeObserver.
- Log in to Cloudflare and select the domain receiving the request.
- Go to Security > Analytics > Events (Security Events).
- Filter around the check timestamp and find the request using the monitored hostname, path, or one of your region's monitoring IPs.
- Open the event and note its Service and rule details. Use them to choose the exception in step 3 below. If the service is Bot Fight Mode, go directly to Bot Fight Mode troubleshooting.
If no matching event appears, inspect your origin firewall and application logs as well. A Cloudflare exception will not resolve an origin-level block or missing application credentials.
2. Add the monitoring IPs to a list
Create a list named uptimeobserver_ips for the rule in the next step:
- Open your account's Configurations page and select Lists.
- Select Create new list, enter
uptimeobserver_ipsas the name, and choose IP as the content type. - Create the list, then select Add items.
- Add the IPv4 addresses and available IPv6 CIDR ranges for every region used by your monitors from the monitoring IP table. Do not add entries marked "Not available."
- Save the items. Update the list if you change monitoring regions or the published addresses change.
IP lists are available on all Cloudflare plans. If you cannot create a list, check your account permissions and list limit.
3. Create an exception for the blocking feature
- Select your domain and open Security > Security rules. In older dashboard layouts, custom rules may appear under Security > WAF.
- Select Create rule > Custom rules and name the rule
UptimeObserver monitoring. -
Select Edit expression and enter:
(ip.src in $uptimeobserver_ips)This uses the IP list you created in step 2.
-
Set the action to Skip, then choose the option for the feature identified in Security Events:
Blocking feature Exception to configure Super Bot Fight Mode Select All Super Bot Fight Mode rules. WAF managed rules Use an exception for the specific blocking rule where available. If you select All managed rules, limit the exception to your monitored endpoint. Rate limiting rules Select All rate limiting rules. A custom rule Select All remaining custom rules and place this Skip rule before the blocking rule. -
Keep Log matching requests enabled, place the exception before any custom rule that blocks your checks, and select Deploy.
Select only the options needed for the blocking feature you found. For other services, see Cloudflare's Skip options or contact support.
4. Confirm your monitor works
- Wait for the next monitoring check.
- Confirm that your monitor receives the expected response rather than a block or challenge page.
- If it still fails, check Cloudflare events again to see whether the exception matched or another feature blocked the request.
- Confirm checks succeed from every selected monitoring region. If your URL redirects, check that the destination is accessible too.
If a check returns 401 or 403 without a Cloudflare block event, check your application's credentials and origin firewall. Configure any required API key or authorization header in your HTTP monitor settings.
If Bot Fight Mode is blocking checks
Bot Fight Mode cannot be bypassed using a WAF Skip rule. If the blocked event identifies Bot Fight Mode as the service, use these steps instead:
- Go to Security > Settings and filter by Bot traffic.
- Turn Bot fight mode off to remove those challenges. This changes protection for the domain, not only the monitored endpoint.
- If your Cloudflare plan includes Super Bot Fight Mode, you can enable it and use the targeted Skip rule above for monitoring traffic.
After updating the setting, confirm your monitor works. For details, see Cloudflare's Bot Fight Mode limitations and Super Bot Fight Mode exceptions.
Limit the exception to a monitored endpoint
To apply the exception only to one hostname and path, use this expression instead. Replace example.com and /health with the values for your monitor:
(ip.src in $uptimeobserver_ips and http.host eq "example.com" and http.request.uri.path eq "/health")
If your monitor follows redirects, include the destination hostname and path in the rules protecting them. For a blocking custom rule, you can also edit that rule to exclude uptimeobserver_ips instead of skipping all remaining custom rules.
Need assistance?
Contact support using the "Need Help?" button in the dashboard or email support@uptimeobserver.com. Include the monitor URL, region, timestamp and timezone, HTTP status, blocking service or rule, and Cloudflare Ray ID if available.