Sentry's error, transaction and attachment ingestion ran delayed for 1h 11m on 4 November 2026, starting at 17:31 UTC. Sentry says the fault was in its US region, and its own status page carries the record since no user reports were filed during the window.
Started
17:31 UTC
Duration
Lasted 1h 11m
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: Error Ingestion, Transaction Ingestion, Attachment Ingestion
What happened?
Sentry opened the incident at 17:31 UTC, reporting increased ingestion latency across all its datasets, meaning error, transaction and attachment events were arriving late rather than failing outright. By 17:46 UTC Sentry said it had identified the cause as specific to its US region and had deployed a fix, and it moved to burning the backlog of events that had piled up. At 18:10 UTC Sentry gave a more granular update: transaction events received more than an hour earlier were being backfilled, uptime event backlog in the US was still being worked through, and all other event types in that region were back to normal latency. The incident closed at 18:41 UTC, 1h 11m after it opened, with Sentry stating that all data had been backfilled and latency was back to normal. That is four updates across the window, all from Sentry's own status page, and no independent confirmation exists beyond that. No user reports were filed during the window, which is consistent with a delay rather than a hard failure: data still arrived, just late, so nothing necessarily broke visibly on dashboards. Sentry did not publish a post-mortem explaining what caused the latency in the US region, only that a fix was deployed. Over the past 90 days Sentry has logged 27 such incidents with a median duration of 1 hour 43 minutes, so this one resolved faster than typical. Across its history, Sentry has recorded 438 incidents at a rate of roughly 5.6 per month, putting ingestion delays of this kind in familiar territory for the service.
Learning
Ingestion delays like this one sit in the layer between your application and Sentry's backend, which is why a check against your own endpoints would not have caught it. Your product kept running and sending events the whole time, they just queued up on Sentry's side waiting to be processed, which is exactly the kind of fault that an uptime check pointed at your own infrastructure is structurally unable to see. UptimeRobot's own 30 day data on Sentry shows 10 incidents, all resolved, with a median duration of 1h 27m, which tells you this pattern recurs often enough to plan around rather than treat as a one off. If your alerting pipeline depends on Sentry events arriving promptly, a delay like this can look like silence on your end, which is worth remembering before you assume your own system has gone quiet. Sentry's status page is the only record of what happened and why, since no post-mortem was published to explain the US region cause beyond "a fix was deployed". Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.