Bots
UptimeRobot: the uptime monitor
UptimeRobot is a monitoring service that requests a URL on a schedule to check it responds. It visits only because someone configured a monitor, usually you, and feeds no search or AI engine. Allowlist it by its published IP files, not by user agent; block it only if nobody at your organisation set it up.
7 days free · card required
0AI-view requests from UptimeRobot · 30 days
filed as conventional traffic (SEO tools, uptime checks, link unfurlers)
We do not name UptimeRobot. It falls through to the wildcard group, which allows everything except /api/.
# No group names UptimeRobot, so# it reads the wildcard group.User-agent: *Allow: /Disallow: /api/
Analyst · reads the AI traffic boardAI traffic board, read over the Attensira MCP; it files UptimeRobot as conventional traffic, off its AI view · · n=143,601 AI requests
Karl-Gustav Kallasmaa, Founder & CEOLast updated Who runs UptimeRobot, and what is it for?
UptimeRobot runs it, and we file it under product operations. Requests a URL on a schedule because someone configured a monitor, usually you, to check that it responds. It feeds no search or AI engine.
From UptimeRobot’s documentation, read .
How do I allow or block UptimeRobot in robots.txt?
Paste this into the robots.txt at the root of your domain. The operator does not say whether the agent reads it.
# Records intent only: UptimeRobot# states no robots.txt position.# The real control is an allowlist# of its published IPs.User-agent: UptimeRobotAllow: /Why does a user-agent exception for UptimeRobot fall short?
The common failure is self-inflicted. Bot rules at the CDN start challenging the monitor, it records a non-200, and you get paged for downtime that never happened. UptimeRobot's own diagnosis of false positives is "a strong chance that the IPs used are blocked by your hosting provider".6It confirms an outage from different servers and providers in the same region, so a rule that challenges unfamiliar addresses catches the confirmation too.5
The tempting fix, a user-agent exception, lets through anything willing to type UptimeRobot into a header. Key the exception on the published addresses instead, and have the firewall read the current list rather than a pasted copy. A stale snapshot produces the same false alert you set out to remove.
How do I verify that a visit really came from UptimeRobot?
Check the source address against the lists UptimeRobot publishes for allow-listing: the IPv4 and combined IPv4/IPv6 text files, the DNS endpoint at ip.uptimerobot.com,3 or the JSON at api.uptimerobot.com/meta/ips, which UptimeRobot says always returns the latest list.4 The general methods are in verifying a crawler.
- IP range files
- IPv4.txtIPv4andIPv6.txt
UptimeRobot publishes no reverse-DNS suffix for UptimeRobot; verify by the range files.
ResearcherTranscribed from UptimeRobot documentation · What user-agent string does UptimeRobot send?
Match the token, never the version. A rule pinned to a version stops matching silently the next time the operator ships.
The version in this string changes; check UptimeRobot’s page before relying on the exact text.
What if nobody at my company set it up?
Then someone outside it added a monitor for your URL; UptimeRobot only requests URLs its users configured.1 This page cannot tell you who or why. If you want it stopped, block or rate-limit the published addresses. A robots.txt rule addresses an operator that has stated no robots.txt position.
What does allowing UptimeRobot cost?
Allowing it costs the requests each scheduled check makes, which is what keeps the monitor working. Blocking it breaks that monitor and gives up nothing else, because it feeds no search or AI engine.
Mozilla/Should I allow UptimeRobot in my situation?
Concrete cases, and what each one implies for this agent.
Your bot-management rules are challenging your own uptime monitor and you are getting false downtime alerts.
Allowlist UptimeRobot's published addresses, not its user-agent string.
UptimeRobot publishes its monitoring IPs specifically for allow-listing, as downloadable IPv4 and IPv6 files and via a DNS endpoint. An address-based exception cannot be triggered by anything that simply copies the header, which a user-agent exception can.
Traffic analytics shows steady, evenly-spaced visits with a near-zero session duration.
Exclude the UptimeRobot token from analytics rather than from the server.
The user agent begins with "Mozilla/5.0", so a classifier that reads the front of the header files these as human visits. The traffic is legitimate and should keep reaching the server; it just should not be counted as an audience.
UptimeRobot checks are arriving and nobody on your team set up an account.
Treat it as third-party observation, and decide whether that matters to you.
UptimeRobot only requests URLs that one of its users configured, so a check against your site means someone outside your organisation added a monitor for it. If you want it stopped, block the published addresses rather than writing a robots.txt rule.
What else do people ask?
Does UptimeRobot obey robots.txt?
Where do I get the current UptimeRobot IP list?
Why is monitoring traffic in my analytics as a real visitor?
Does UptimeRobot check my site from one place or several?
Where do these facts come from?
6 claims on this page, each with the page it was read from; last checked . The numbers in the text point here.
UptimeRobot operates a monitoring service that requests configured URLs from its monitoring locations on a schedule, and publishes those locations' IP addresses so site owners can allow-list them.
uptimerobot.com · retrieved
“Here is the list of our IPs so you can allow-list them if needed.”
UptimeRobot publishes its user-agent string as "Mozilla/5.0+(compatible; UptimeRobot/2.0; http://www.uptimerobot.com/)".
help.uptimerobot.com · retrieved · changes often, check the source
“The user agent we use is: Mozilla/5.0+(compatible; UptimeRobot/2.0; http://www.uptimerobot.com/)”
UptimeRobot publishes its monitoring IP addresses for allow-listing as downloadable IPv4 and combined IPv4/IPv6 text files, and also serves them from a dedicated DNS endpoint at ip.uptimerobot.com.
uptimerobot.com · retrieved
UptimeRobot publishes its monitoring IPs as JSON at api.uptimerobot.com/meta/ips, an API it describes as always returning the latest list.
uptimerobot.com · retrieved
“To keep your IPs up to date, we've released a dedicated API that always returns the latest list of UptimeRobot monitoring IPs.”
UptimeRobot performs initial checks from one region using randomly selected servers, and verifies detected downtime with additional checks from different servers and providers within the same region.
uptimerobot.com · retrieved
“When an issue is detected, we verify the downtime by conducting additional checks from different servers and providers within the same region.”
UptimeRobot states that if a site owner receives false positives, there is a strong chance its IPs are blocked by the hosting provider.
uptimerobot.com · retrieved
“If you receive any false positives, there is a strong chance that the IPs used are blocked by your hosting provider.”
Want whatever it takes to win the answer?
7 days free · card required