Help center
Allowlisting BigTimeUp
BigTimeUp checks your sites every 5 minutes. Firewalls, CDNs, and bot protection can block or challenge those checks, which hides real outages or causes false alerts. This guide shows how to recognize our checks and let them through.
How to recognize BigTimeUp checks
Every check sends this User-Agent header:
BigTimeUp/1.0 (+https://bigtimeup.com/help/allowlisting)- Checks are plain
GETrequests over HTTPS to the exact URL you added. - Checks do not follow redirects, run JavaScript, or solve challenges.
- A failed check is retried up to two more times within the same minute.
Cloudflare
- In the Cloudflare dashboard, open your domain and go to Security, then WAF, then Custom rules.
- Create a rule with the field User Agent, the operator contains, and the value
BigTimeUp/. - Set the action to Skip, and select the features that block checks, such as Super Bot Fight Mode, managed rules, and rate limiting rules.
- Place the rule first and deploy it.
If you use Bot Fight Mode on a free plan, it cannot be skipped by a custom rule. Turn it off for the monitored hostname or monitor a path it does not cover.
Other firewalls and bot protection
Most web application firewalls (AWS WAF, Sucuri, Wordfence, ModSecurity, and others) support an allow rule that matches the User-Agent header. Match requests whose User-Agent starts with BigTimeUp/ and exempt them from bot detection, challenges, and rate limits.
Keep the exception narrow
Anyone can send a User-Agent header, so an allow rule based on it alone should only skip bot checks and rate limits, not authentication or access controls.
- Limit the rule to the hostname and path you monitor.
- Monitor a lightweight public page or a health check URL rather than a page behind a login.
Still seeing false alerts? See the troubleshooting guide or contact [email protected].