What does DigitalOcean consider a successful web check?

For HTTP and HTTPS targets, status codes from 200 through 299 count as success. Any response outside that range is treated as an outage.

Why are requests arriving from several regions?

A check can be enabled in more than one of DigitalOcean's monitoring regions. Each selected location records its own availability and latency data.

Is robots.txt support confirmed for DigitalOceanUptimeBot?

No. The catalog supplies a token and flag, but the operator's Uptime documentation does not confirm the HTTP identity or explain robots processing.

Does this monitor affect AI answers?

No AI search or training use is documented. A block changes the Uptime result and may trigger alerts, but it does not control use of the page by AI systems.

DigitalOceanUptimeBot Bot Guide

What is DigitalOceanUptimeBot?

DigitalOcean Uptime repeatedly tests a target selected by a DigitalOcean customer. Each check points to one URL or IP address, so its purpose is to report whether that endpoint is reachable and how long the connection takes. It does not discover additional pages from links.

The customer chooses HTTPS, HTTP, or PING. Web checks treat status codes from 200 through 299 as successful, and HTTPS monitoring also watches certificate expiration. PING uses ICMP against a host or IPv4 address, which means it will not leave an ordinary HTTP request in an access log.

Checks can run from selected locations in Asia, Europe, or the United States. Results are recorded by region and combined into a global view. Alert rules can send email or Slack notifications for downtime, latency thresholds, and expiring certificates.

The DigitalOceanUptimeBot token comes from this catalog record, but DigitalOcean's Uptime documentation does not publish an HTTP user agent or describe robots.txt behavior. It also gives the service no AI indexing or training function. Blocking a check can create an outage result for its owner, but it does not change AI search visibility.

Not relevant for AI search

Is DigitalOceanUptimeBot relevant for AI search?

No. DigitalOceanUptimeBot is not part of AI search or training, so allowing or blocking it does not change your AI visibility.

DigitalOceanUptimeBot runs synthetic monitoring or uptime checks on a schedule. It is not collecting content for any index or model, so it has no bearing on search rankings or AI answers. You usually see it because your own team or a service you use set up a check.

How to handle DigitalOceanUptimeBot

If the check is yours, direct it to a small health route that returns an expected success status and exposes no private information. Change or disable the check in DigitalOcean when it is obsolete. Blocking it at the edge is likely to be recorded as downtime and may fire an alert.

The recorded token allows an advisory rule:

User-agent: DigitalOceanUptimeBot
Disallow: /

Both identification and compliance remain unverified. DigitalOcean's current Uptime pages do not confirm that header or say that a probe requests robots.txt. Rely on account settings, endpoint authentication, or a server rule when you need a definite outcome.

Examples

An API owner monitors `/ready` from Europe and Asia East. A 204 response counts as available, while the regional response times appear separately in DigitalOcean.
Requests claiming to be DigitalOceanUptimeBot hit a private status page, but nobody can find the check in the company account. The team keeps authentication enabled because the token is not an official proof of origin.

Frequently asked questions about DigitalOceanUptimeBot

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

The customer specifies one URL for an HTTP or HTTPS check, or one hostname or IP address for PING. The monitor repeats that target rather than exploring the site.