Why is UptimeRobot requesting this endpoint?

A customer configured that URL as a monitor target. UptimeRobot checks the target rather than discovering pages through links.

Which HTTP method does UptimeRobot use?

HEAD is the documented default for HTTP monitoring. Customers on supported plans can configure GET instead.

How can I identify a default UptimeRobot request?

Match the complete `UptimeRobot/2.0` user agent, including the plus sign after `Mozilla/5.0`, and compare the source with UptimeRobot's current location list.

Does Uptime Robot respect robots.txt?

The record says yes, but UptimeRobot's HTTP documentation does not explain robots handling. Account settings and verified network controls are more dependable.

Does UptimeRobot affect AI search visibility?

No. It reports availability to the monitor owner and has no documented role in AI search or model training.

Uptime Robot - What It Is & How to Handle It

What is Uptime Robot?

UptimeRobot reaches a website when a customer points an HTTP monitor at one of its URLs. The monitor checks that target at the configured interval and reports whether it is available. Other UptimeRobot monitor types cover services such as ports, ping, heartbeat, and DNS without crawling website content.

The default HTTP user agent is Mozilla/5.0+(compatible; UptimeRobot/2.0; http://www.uptimerobot.com/). UptimeRobot asks teams to preserve the plus sign after Mozilla/5.0 when they allowlist the full value. A customer may configure a custom user agent, so the default string does not identify every monitor.

UptimeRobot uses HEAD for HTTP checks by default because it needs the response headers rather than the page body. Its distributed monitoring system performs an initial check from a server in the selected region. When that check finds a problem, other servers and providers in the same region can send additional requests to verify the downtime.

This traffic reports availability to the monitor owner. UptimeRobot is not documented as an AI search crawler or a source of model-training data. It may expose an outage that also blocks search crawlers, but receiving the monitor request does not improve AI visibility.

How to handle Uptime Robot

Let an expected monitor receive the response that the test is supposed to evaluate. If a firewall blocks only some locations, use UptimeRobot's current IP list or the exact configured user agent to make a narrow exception for the monitored target.

The stable product name permits this robots rule:

User-agent: UptimeRobot
Disallow: /

The bot record says UptimeRobot respects robots.txt, but its HTTP-monitor documentation does not present robots.txt as a control for probes. Treat the snippet as advisory. Pause or delete the monitor for a definitive stop, or use a verified server rule if the account is unknown. Blocking a live check can create a downtime incident and additional verification requests.

Examples

A monitor sends HEAD to `/status` and receives a successful response, producing one UptimeRobot log entry without the page's image or script requests.
A firewall blocks one monitoring server, and UptimeRobot sends verification checks from other servers in the same region before reporting the endpoint down.