Skip to main content

UptrackBot and other Uptrack user agents

Last updated: October 14, 2026

Uptrack is an uptime monitoring service. This page lists the user agents that Uptrack sends, what each one requests and how often. If one of them causes a problem on your site, email [email protected].

UptrackBot

UptrackBot/1.0 (+https://uptrack.app/bot)

UptrackBot reads the public status data of services that Uptrack customers depend on, for example the JSON feed behind a public status page. It reads only URLs from a list that Uptrack keeps. A customer cannot make UptrackBot request a URL.

  • It reads each service 1 time per minute at most, however many customers watch it. When no customer watches a service, it stops.
  • Each read is 1 GET request with Accept: application/json. It sends If-None-Match with the last ETag, so an unchanged feed can answer 304 Not Modified.
  • It waits 10 seconds at most, reads 2 MB at most and does not follow redirects.
  • After a failed read it waits longer: 1, 2, 4, 8, then 10 minutes. If you answer 429 or 503 with a Retry-After header, it waits that long, up to 1 hour.
  • It does not crawl: it requests the known status URL and follows no links. It does not read robots.txt. To ask us to stop, email us (see the end of this page).

Uptrack Monitor

Uptrack Monitor checks the URLs that Uptrack customers add as monitors, for example a home page, an API health URL or a sitemap. It sends one of these user agents:

  • Uptrack Monitor/1.0 (Rust)
  • Uptrack Monitor/1.0 (Rust; sitemap)
  • Uptrack Monitor/1.0 (Edge; +https://uptrack.app/docs/check-locations)
  • Uptrack Monitor/1.0

It checks at the interval that the customer chose, as often as every 30 seconds, from one or more check locations. Each check requests the one URL of the monitor. It does not crawl the page or follow its links. The check locations are described in 22 Check Locations Without 22 Times the False Alarms.

Other Uptrack user agents

  • Uptrack Checker/1.0 looks at a site's TLS certificate to explain a failed check: when someone uses the website check tool on uptrack.app, or when an Uptrack monitor fails.
  • Uptrack-Webhook/1.0 sends alert messages to a webhook URL that an Uptrack customer set up.

For site owners

  • To let these requests through a firewall or bot filter, match the user agent UptrackBot or Uptrack Monitor.
  • To slow UptrackBot down, answer 429 with a Retry-After header.
  • To report a problem or ask us to stop, email [email protected]. Tell us the URL, the user agent and the time of the requests, with the time zone.