Is Sentry down?
Last checked 1m agoNo incidents right now.
Sentry is operational right now. Last checked 1m ago; the most recent incident resolved 5d ago.
Real-time Sentry status, recent outages, and incident history — pulled directly from Sentry's official status page at https://status.getsentry.com every 5 minutes. Pingoru tracks 37 Sentry services and has captured 28 incidents in the last 90 days (98.76% uptime). Get email, Slack, Discord, or webhook alerts the moment Sentry reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- US Error IngestionUS Errors AlertingUS Profile IngestionUS Spans Alerting
Timeline · 4 updates
- investigating · Jul 27, 2026, 04:23 PM UTC
We are experiencing issues with error and profile ingestion in our US region and are investigating the issue.
- identified · Jul 27, 2026, 04:56 PM UTC
We have identified the issue and error and profile ingestion is back up in US. Expect delays in ingestion and alerting for errors and profiles.
- monitoring · Jul 27, 2026, 06:07 PM UTC
We have resolved the incident and are monitoring our ingestion backlog.
- resolved · Jul 27, 2026, 06:27 PM UTC
The backlog has been cleared and ingestion is back to normal.
Latest: The backlog has been cleared and ingestion is back to normal.
-
- US Span Ingestion
Timeline · 6 updates
- investigating · Jul 21, 2026, 10:30 AM UTC
We are actively investigating this issue
- investigating · Jul 21, 2026, 11:26 AM UTC
We are still actively investigating this issue
- investigating · Jul 21, 2026, 12:20 PM UTC
We are still actively investigating this issue
- monitoring · Jul 21, 2026, 01:04 PM UTC
We've found and fixed the root cause and are burning through our spans backlog. Ingestion should be back to normal in around an hour.
- monitoring · Jul 21, 2026, 01:55 PM UTC
We're still burning through our spans backlog
- resolved · Jul 21, 2026, 02:14 PM UTC
We've burned through our spans backlog. Latency across span consumers are normal.
Latest: We've burned through our spans backlog. Latency across span consumers are normal.
-
- EU Error IngestionEU Errors AlertingEU Attachment Ingestion
Timeline · 10 updates
- investigating · Jul 20, 2026, 11:11 AM UTC
we are investigating an issue affecting errors ingestion in the DE/EU region
- identified · Jul 20, 2026, 11:41 AM UTC
We have identified the issue causing errors, attachments, and feedback events to have high ingest latency in our EU region and are working on a fix.
- identified · Jul 20, 2026, 12:10 PM UTC
We have identified the issue causing errors, attachments, and feedback events to have high ingest latency in our EU region and are continuing to work on a fix.
- identified · Jul 20, 2026, 12:24 PM UTC
We have identified the issue causing errors, attachments, and feedback events to have high ingest latency in our EU region and are continuing to work on a fix.
- identified · Jul 20, 2026, 01:19 PM UTC
We have identified the issue causing errors, attachments, and feedback events to have high ingest latency in our EU region and are continuing to work on a fix.
- identified · Jul 20, 2026, 01:47 PM UTC
We have implemented a fix for errors and feedback ingestion in our EU region, and latency for those pipelines has returned to normal. We are still working on fixing our attachments ingestion pipeline in EU.
- monitoring · Jul 20, 2026, 02:30 PM UTC
We have implemented a fix for our attachment ingestion issue in our EU region, and are monitoring while the backlog burns. We will update here when latency is back to normal.
- monitoring · Jul 20, 2026, 02:50 PM UTC
The backlog on attachments in our EU region is fully burned, and latency is back to normal. While new error events are being processed with normal latency, we have a backlog of old error events that we are now burning through.
- monitoring · Jul 20, 2026, 04:09 PM UTC
We are still burning the backlog of EU region error events received during the incident. We are around halfway through the backlog.
- resolved · Jul 20, 2026, 04:57 PM UTC
We have fully burned the backlog of EU error events ingested during the incident. Latency is normal across all event types.
Latest: We have fully burned the backlog of EU error events ingested during the incident. Latency is normal across all event types.
-
- DashboardSeer
Timeline · 8 updates
- identified · Jul 16, 2026, 09:06 PM UTC
The issue is mitigated and the webhook backlog is being processed. Seer code reviews will run and linked Github issues and PRs will update incrementally.
- identified · Jul 17, 2026, 12:44 AM UTC
The webhook backlog is being processed, ETA ~3 hours until fully caught up. Seer code reviews will run and linked Github issues and PRs will update incrementally.
- identified · Jul 17, 2026, 01:28 AM UTC
The webhook backlog is processing.
- identified · Jul 17, 2026, 02:44 AM UTC
The webhook backlog is processing.
- identified · Jul 17, 2026, 03:49 AM UTC
The webhook backlog is processing. Estimated recovery is now 2-2.5 hours.
- identified · Jul 17, 2026, 04:50 AM UTC
The webhook backlog is processing.
- identified · Jul 17, 2026, 05:49 AM UTC
The webhook backlog is processing.
- resolved · Jul 17, 2026, 06:57 AM UTC
The webhook backlog is now resolved.
Latest: The webhook backlog is now resolved.
-
- US Error IngestionEU Error Ingestion
Timeline · 8 updates
- investigating · Jul 14, 2026, 02:44 PM UTC
We are currently investigating the issue.
- investigating · Jul 14, 2026, 03:42 PM UTC
We continue to investigate the issue.
- identified · Jul 14, 2026, 04:42 PM UTC
We have identified the problem and are working on recovery.
- identified · Jul 14, 2026, 04:49 PM UTC
We are still working on recovery. New errors should be processed in real time, and we are working on recovering historical data.
- identified · Jul 14, 2026, 05:02 PM UTC
We are still working on recovery. New errors should be processed in real time, and we are working on recovering historical data. We are working to start allowing user feedback in DE.
- monitoring · Jul 14, 2026, 05:40 PM UTC
We are processing errors in realtime, and error backlogs have been processed. We're continuing to monitor the situation before restoring feedback ingestion.
- monitoring · Jul 14, 2026, 06:16 PM UTC
We are continuing to monitor ingestion, and a fix is being deployed to unblock feedback ingestion.
- resolved · Jul 14, 2026, 07:32 PM UTC
Feedback ingestion is back to realtime and the backlog has been processed.
Latest: Feedback ingestion is back to realtime and the backlog has been processed.
-
See the full Sentry outage history
23 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Sentry outage history →Or sign up free to get alerts when Sentry breaks · 10 free monitors · No credit card
- Started Jul 27, 2026, 04:23 PM UTC · Resolved Jul 27, 2026, 06:27 PM UTC · 2h 3m
- Delayed ingestion on us region ResolvedStarted Jul 21, 2026, 10:30 AM UTC · Resolved Jul 21, 2026, 02:14 PM UTC · 3h 44m
- Started Jul 20, 2026, 11:11 AM UTC · Resolved Jul 20, 2026, 04:57 PM UTC · 5h 46m
- Started Jul 16, 2026, 09:06 PM UTC · Resolved Jul 17, 2026, 06:57 AM UTC · 9h 50m
- Started Jul 14, 2026, 02:44 PM UTC · Resolved Jul 14, 2026, 07:32 PM UTC · 4h 47m
- Ingestion delays in US ResolvedStarted Jul 13, 2026, 11:51 AM UTC · Resolved Jul 13, 2026, 02:25 PM UTC · 2h 33m
- Started Jul 13, 2026, 12:58 AM UTC · Resolved Jul 13, 2026, 02:56 AM UTC · 1h 58m
- Started Jul 10, 2026, 10:43 PM UTC · Resolved Jul 11, 2026, 03:34 AM UTC · 4h 51m