What Sentry Uptime does
SentryUptimeBot performs uptime checks against endpoints that a Sentry user has configured for monitoring, and Sentry generates downtime issues when a check detects a problem. Requests identify themselves with the user agent string "SentryUptimeBot/1.0 (+https://docs.sentry.io/product/monitors-and-alerts/monitors/uptime-monitoring/)". Sentry recommends allowlisting the bot by this user agent rather than by IP address, because its IP addresses can change without notice, and it maintains a separate document listing the IP ranges used for uptime checks.
How to control Sentry Uptime
Target Sentry Uptime in your robots.txt with the SentryUptimeBot token. Rules apply per bot, so you can allow this one while blocking others, or the reverse.
Allow Sentry Uptime
User-agent: SentryUptimeBot
Allow: /Block Sentry Uptime
User-agent: SentryUptimeBot
Disallow: /Sentry publishes the IP ranges used for uptime checks in a separate document but recommends allowlisting by the SentryUptimeBot user agent string, since the IP addresses can change without notice.
How to identify Sentry Uptime
Temso identifies Sentry Uptimetraffic 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.
SentryUptimeBotSentry Uptime FAQ
What is Sentry Uptime?
Sentry Uptime is the checker behind Sentry's uptime monitoring feature: it periodically requests URLs that a Sentry user has configured and creates downtime issues when problems are detected. It identifies itself with the user agent "SentryUptimeBot/1.0 (+https://docs.sentry.io/product/monitors-and-alerts/monitors/uptime-monitoring/)".
How do I block Sentry Uptime?
Add a robots.txt group with "User-agent: SentryUptimeBot" followed by "Disallow: /". Sentry's documentation does not state whether the checker honors robots.txt; because the checks target URLs someone configured in Sentry and the IP addresses can change without notice, filtering by the SentryUptimeBot user agent at the server or firewall level is the approach Sentry's docs describe.
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.
