About our monitoring probes
What you are seeing
UptimeAgent is an uptime monitor. A customer asked us to check whether their site is reachable, and the requests in your log are those checks. Each one is a single HTTP request for the page they gave us (no crawling, no form submissions, no login attempts), and it identifies itself with this header:
User-Agent: UptimeAgent/1.0 (+https://uptimeagent.com/probe)How often we check
- Normally: once per interval the customer chose, from each region they selected. The default is every 60 seconds from one region.
- When a check fails: that region re-checks every 10 seconds until three checks in a row have failed, which confirms the outage (about twenty seconds). After that the checks slow down, doubling the gap each time until they are back at the normal interval. We do not hammer a site that is down.
- If your site says it is busy (HTTP 429 or 503, or refuses the connection) we back off further, immediately.
Where the requests come from
Every probe connects from one fixed address per region. Allow these if your firewall or bot rules are blocking us, and you can be sure a request claiming to be us really is:
| Region | Location | IP address |
|---|---|---|
DUB | Ireland (eu-west-1) | 34.251.215.59 |
IAD | N. Virginia, US (us-east-1) | 34.197.3.65 |
YUL | Montréal, Canada (ca-central-1) | 15.175.177.125 |
FRA | Frankfurt, Germany (eu-central-1) | 63.185.245.245 |
BOM | Mumbai, India (ap-south-1) | 13.202.211.239 |
SYD | Sydney, Australia (ap-southeast-2) | 16.178.39.97 |
Our own test environment, which only ever monitors sites we operate, probes from 52.215.194.27.
The same list, for a firewall or WAF rule to read: uptimeagent.com/probe/ips.json. One entry per region, each address as a /32. It is republished whenever an address changes, with the date it was last verified.
To have a site left alone
Email support@uptimeagent.com with the hostname. We will pause every monitor pointing at it and tell the customer who set it up. Blocking the addresses above also works. A blocked probe is recorded as a failed check on the customer's side and nothing more happens.
What we store about your site
The result of each check: whether it answered, the status code, how long it took, and the TLS certificate dates. On a failing check, the first few kilobytes of the error response and the response headers, with credentials and cookies removed. Nothing is stored about your visitors. Details are in our privacy policy.