OncalmOwlBot
If you see OncalmOwlBot in your logs, one of our customers monitors the availability of your website, API, certificate or server with Oncalm Owl - usually because it is their own site or a service they depend on. The bot only reads: it never submits forms, logs in, runs JavaScript or crawls links.
User-Agent
Every HTTP check sends this User-Agent:
Mozilla/5.0 (compatible; OncalmOwlBot/1.6; +https://oncalmowl.com/bot)
The version number changes with new releases; match on OncalmOwlBot.
What it does
- HTTP checks: one request to the exact URL the customer entered (GET unless they chose another method), as often as every 30 seconds, with a timeout of up to 10 seconds. Redirects and the response body are only read to check the status code or a keyword.
- Confirmation: when a check fails, a probe in another region repeats it right away before anyone is alerted, so you may see two requests from different addresses within a few seconds.
- Other checks: TLS handshake to read the certificate, TCP connect to a port, ICMP ping and DNS lookups. These carry no User-Agent.
- It does not: follow links, read robots.txt (the checks are requested for specific URLs, not crawling), store your pages or use them for anything else.
IP addresses
Requests come only from these addresses. Machine-readable lists: ips.txt (one address per line) and ips.json.
| Role | Location | IPv4 | IPv6 |
|---|---|---|---|
| Probe eu-fi | Helsinki, Finland | 2.29.187.89 | 2a01:4f9:c015:e9bd::1 |
| Probe eu-de | Falkenstein, Germany | 138.199.228.42 | 2a01:4f8:c010:ab7c::1 |
| Webhooks & alerts | Nuremberg, Germany | 2.31.159.34 | 2a01:4f8:1c1c:fe73::1 |
"Webhooks & alerts" sends webhook, Slack, Teams, Discord, PagerDuty and Opsgenie notifications and looks up domain registrations. Allow it if your alert endpoints are behind a firewall. We announce new probe addresses on this page before they start checking.
Allow-list or filter it
- Firewall or WAF: allow the addresses above, or the User-Agent containing
OncalmOwlBot. In Cloudflare a custom rule with(ip.src in {2.29.187.89 2a01:4f9:c015:e9bd::1 138.199.228.42 2a01:4f8:c010:ab7c::1 2.31.159.34 2a01:4f8:1c1c:fe73::1})and the action Skip keeps bot protection from blocking the checks. - Web analytics: exclude the addresses (Matomo: Administration > Websites > Global list of excluded IPs; Google Analytics: a data filter or an internal traffic rule) or the User-Agent, so checks are not counted as visits. Most analytics tools already ignore it because it runs no JavaScript.
- Rate limits: one monitor causes at most two requests a minute per URL, plus confirmation re-checks during an outage.
Questions or a problem
If the bot causes you trouble, or you want checks of your site stopped, write to [email protected] with the URL and a time stamp from your logs. We will contact the customer or stop the checks.