About UptizmBot

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. It reads no other page, follows no links you did not redirect it to and submits no forms.

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. The availability check leaves from third-party exit addresses in a rotating pool of the proxy network provided by Kodizm, and from the edge network provided by Cloudflare, rather than from one address of ours, so blocking a single exit will not keep those requests out for long. 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.