Über UptizmBot
Gültig ab 2026-11-20
Dieses Dokument ist nur auf Englisch verfügbar.
Uptizm is an uptime monitoring service, and UptizmBot is the client that makes its availability checks. If it showed up in your access log and you want to know what it is, or you want it to stop, this page is the whole answer.
How to recognise it
By default it identifies itself with this string on every request:
UptizmBot/1.0 (+https://uptizm.com/bot)
It does not pretend to be a browser, and it does not send a browser User-Agent unless the customer who set up the check replaced ours with one of their own.
What it requests
An Uptizm customer has asked us to watch an address on your service, and we request that address on the schedule they chose, from the regions they chose, and record whether it answered, how quickly, and what it answered with. The customer decides the URL, the method, the headers and whether a redirect is followed, because the check is a measurement on their behalf. A check reads no other page, follows no links you did not redirect it to and submits no forms.
What else it reads
Uptizm also publishes public pages about well-known online services, and UptizmBot gathers what those services say about themselves. It reads two kinds of source and no others.
The first is the public status feeds the services publish themselves: Atlassian Statuspage
summary pages (the format most vendor status sites use), slack-status.com,
status.cloud.google.com, status.aws.amazon.com and azure.status.microsoft. Each feed is one
conditional request, made no more often than once a minute, and no redirect is followed. Note
that every feed request carries the User-Agent shown above, and a host that answers 403 or
429 is dropped for good, because we read that as a stop.
The second is the public page of an outage tracker, currently Downdetector, which we read to see whether it reports an outage. It is read at most once every ten minutes. A tracker page is fetched through a remote page-fetching service instead of directly, so the request that reaches the tracker may not carry the User-Agent shown above.
None of these requests is made directly from our own servers. If you would rather we did not read a host at all, write to us as described below and say which one.
How it backs off
It does not stop itself when refused, and we would rather say so than let you find out. It
keeps requesting on its schedule and records what came back, because a refusal is itself a
measurement and the customer is better served by "they refuse our requests" than by
silence. A 403 is recorded like any other answer. If you want that stopped, the section
below is the way.
There is one answer we do not record: an interactive bot challenge. If your edge replies to the check with a challenge page instead of a response, we have measured nothing about your service, so nothing is stored and nothing is reported as down over it. We do not try to solve the challenge or swap our User-Agent for a browser one. Our checks leave from more than one network, though, and a challenged address moves the next checks to another one for a while, under the same User-Agent.
How to reach a person
If you would prefer we did not request anything at all, or you just want to know why we are there, write to [email protected] and say which domain you are asking about. Blocking the User-Agent works too, and we will read that as the answer it is rather than routing around it.
One more thing worth saying plainly. Die Verfügbarkeitsprüfung geht nicht von einer eigenen Adresse aus, sondern von Austrittsadressen Dritter in einem rotierenden Pool des von Kodizm bereitgestellten Proxy-Netzwerks und vom Edge-Netzwerk von Cloudflare; das Sperren eines einzelnen Austritts hält diese Anfragen daher nicht lange fern. If you want us stopped for good, the reliable way is writing to us, as above, or blocking the User-Agent itself, which we honour the same way regardless of which address it arrives from.