What Updown.io does
Updown.io periodically checks a URI its customer configures and reports any anomaly, including downtime, bad responses, degraded performance, or a broken SSL certificate. It supports HTTP(S), TCP, and ICMP checks as well as monitoring of periodic tasks and cron jobs, and sends alerts through channels such as Slack, Teams, Telegram, email, SMS, Zapier, and webhooks. Checks originate from ten monitoring nodes located in Los Angeles, Miami, Toronto, Roubaix, Frankfurt, Cape Town, Helsinki, Singapore, Tokyo, and Sydney, and requests include "updown.io" in the User-Agent header.
How to identify Updown.io
Temso identifies Updown.iotraffic by matching the request's User-Agent header against this pattern. User-agent strings can be spoofed, so treat a match as an indication, not proof.
updown\.ioUpdown.io FAQ
What is Updown.io?
Updown.io is an uptime monitoring service that periodically checks a customer-configured URI over HTTP(S), TCP, or ICMP and reports downtime, bad responses, degraded performance, or broken SSL certificates. Its requests include "updown.io" in the User-Agent header and come from ten monitoring nodes around the world.
Can I block Updown.io with robots.txt?
Updown.io is an uptime checker that only requests URIs its customers have configured for monitoring, and its documentation does not mention robots.txt, so a robots.txt rule is not the documented way to stop it. To block it, filter requests whose User-Agent contains "updown.io", or block its published node IPs, which are also available through the ips.updown.io DNS entry.
About Operational Bots
Monitoring, security scanning, link previews, webhooks, and feed fetchers: the utility traffic that keeps integrations and shared links working.
Most of this traffic is service-critical or user-triggered. Webhooks and previews don't follow robots.txt, and blocking them tends to break things you rely on.
