Sentry had two separate incidents on 21 October 2026. The first, a one-hour fault in the US region, stopped Sentry.io from loading and delayed event ingestion. The second, shorter one slowed integration webhooks for GitHub, Slack and Autofix PRs. Both were Sentry-side problems.
Started
08:54 UTC
Duration
Lasted 1h 0m
Source
IsDown
Next time
Sentry is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Slack, Error Ingestion
What happened?
Sentry logged two incidents on 21 October 2026, affecting its Error Ingestion and Slack components. The first began at 08:54 UTC, described as an issue affecting the US Sentry region where Sentry.io was not loading. By 09:23 Sentry said it had identified the problem and addressed the cause, moving to monitoring. At 09:40 it added that native events ingestion was still delayed while it worked through a backlog, and the incident was marked resolved at 09:53 once that backlog had caught up. Total duration was 1 hour 0 minutes. The second incident started at 17:53 UTC and lasted 22 minutes. Sentry's only update on it said it was mitigating increased latency processing integration webhooks, naming GitHub, Slack and Autofix PRs as affected, and stated explicitly that no data was being lost. No further updates were filed after that single entry, and no resolution message appears on the record for this second incident beyond the stated 22 minute duration. No user reports were filed during either window. Sentry's own status page is the only source for both incidents, so each entry is a single company-authored account of what it saw on its side, there is no independent confirmation. Over the past 90 days Sentry has logged 25 incidents with a median duration of 2 hours 6 minutes, so both of today's incidents resolved faster than that median.
Learning
UptimeRobot's own 30-day figures show 6 incidents against Sentry, all resolved, with a median duration of 57 minutes, a pattern consistent with what Sentry itself reported today. This matters because an external check watching whether Sentry.io responds can go green even while a specific pipeline, like native event ingestion or webhook delivery to Slack and GitHub, is degraded behind the scenes. The first incident today is a clear example: the front end came back before the backlog of native events had actually cleared, so a simple page load check could have reported healthy minutes before ingestion was truly caught up. The second incident shows the same shape from a different angle, latency in a specific integration path that would never show up in a check of the main domain. If your product depends on Sentry for error tracking or on its Slack and GitHub integrations, an outage in either of those paths can degrade your workflow without your own uptime checks ever flagging it, because your checks watch your endpoints, not Sentry's internal queues. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.