Sentry Outage History

Sentry is up right now

Sentry had 79 outages in the last 2 years totaling 90h 25m of downtime — averaging 3.2 incidents per month.

There were 79 Sentry outages since October 11, 2025 totaling 90h 25m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getsentry.com

Critical July 27, 2026

Error and profile ingestion issues in US

Detected by Pingoru
Jul 27, 2026, 04:23 PM UTC
Resolved
Jul 27, 2026, 06:27 PM UTC
Duration
2h 3m
Affected: US Error IngestionUS Errors AlertingUS Profile IngestionUS Spans Alerting
Timeline · 4 updates
  1. 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.

  2. 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.

  3. monitoring Jul 27, 2026, 06:07 PM UTC

    We have resolved the incident and are monitoring our ingestion backlog.

  4. resolved Jul 27, 2026, 06:27 PM UTC

    The backlog has been cleared and ingestion is back to normal.

Read the full incident report →

Minor July 21, 2026

Delayed ingestion on us region

Detected by Pingoru
Jul 21, 2026, 10:30 AM UTC
Resolved
Jul 21, 2026, 02:14 PM UTC
Duration
3h 44m
Affected: US Span Ingestion
Timeline · 6 updates
  1. investigating Jul 21, 2026, 10:30 AM UTC

    We are actively investigating this issue

  2. investigating Jul 21, 2026, 11:26 AM UTC

    We are still actively investigating this issue

  3. investigating Jul 21, 2026, 12:20 PM UTC

    We are still actively investigating this issue

  4. 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.

  5. monitoring Jul 21, 2026, 01:55 PM UTC

    We're still burning through our spans backlog

  6. resolved Jul 21, 2026, 02:14 PM UTC

    We've burned through our spans backlog. Latency across span consumers are normal.

Read the full incident report →

Minor July 16, 2026

Github Integration Webhook processing delay

Detected by Pingoru
Jul 16, 2026, 09:06 PM UTC
Resolved
Jul 17, 2026, 06:57 AM UTC
Duration
9h 50m
Affected: DashboardSeer
Timeline · 8 updates
  1. 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.

  2. 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.

  3. identified Jul 17, 2026, 01:28 AM UTC

    The webhook backlog is processing.

  4. identified Jul 17, 2026, 02:44 AM UTC

    The webhook backlog is processing.

  5. identified Jul 17, 2026, 03:49 AM UTC

    The webhook backlog is processing. Estimated recovery is now 2-2.5 hours.

  6. identified Jul 17, 2026, 04:50 AM UTC

    The webhook backlog is processing.

  7. identified Jul 17, 2026, 05:49 AM UTC

    The webhook backlog is processing.

  8. resolved Jul 17, 2026, 06:57 AM UTC

    The webhook backlog is now resolved.

Read the full incident report →

Critical July 14, 2026

Error ingestion degraded in DE region

Detected by Pingoru
Jul 14, 2026, 02:44 PM UTC
Resolved
Jul 14, 2026, 07:32 PM UTC
Duration
4h 47m
Affected: US Error IngestionEU Error Ingestion
Timeline · 8 updates
  1. investigating Jul 14, 2026, 02:44 PM UTC

    We are currently investigating the issue.

  2. investigating Jul 14, 2026, 03:42 PM UTC

    We continue to investigate the issue.

  3. identified Jul 14, 2026, 04:42 PM UTC

    We have identified the problem and are working on recovery.

  4. 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.

  5. 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.

  6. 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.

  7. monitoring Jul 14, 2026, 06:16 PM UTC

    We are continuing to monitor ingestion, and a fix is being deployed to unblock feedback ingestion.

  8. resolved Jul 14, 2026, 07:32 PM UTC

    Feedback ingestion is back to realtime and the backlog has been processed.

Read the full incident report →

Minor July 13, 2026

Ingestion delays in US

Detected by Pingoru
Jul 13, 2026, 11:51 AM UTC
Resolved
Jul 13, 2026, 02:25 PM UTC
Duration
2h 33m
Affected: US Error IngestionUS Transaction IngestionUS Attachment IngestionUS Profile IngestionUS Replay IngestionUS Span Ingestion
Timeline · 4 updates
  1. investigating Jul 13, 2026, 11:51 AM UTC

    We are investigating ingestion delays.

  2. identified Jul 13, 2026, 12:24 PM UTC

    We identified the issue and restoring service.

  3. monitoring Jul 13, 2026, 12:41 PM UTC

    Service has been restored and we are actively monitoring the situation

  4. resolved Jul 13, 2026, 02:25 PM UTC

    Service has been restored.

Read the full incident report →

Critical July 13, 2026

Ingestion delayed for spans, logs, crons in US region

Detected by Pingoru
Jul 13, 2026, 12:58 AM UTC
Resolved
Jul 13, 2026, 02:56 AM UTC
Duration
1h 58m
Affected: US Spans AlertingUS Span IngestionUS Cron MonitoringUS Uptime Monitoring
Timeline · 4 updates
  1. investigating Jul 13, 2026, 12:58 AM UTC

    We are currently investigating the issue.

  2. identified Jul 13, 2026, 01:46 AM UTC

    We have identified the problem and are working to restore ingestion

  3. monitoring Jul 13, 2026, 02:01 AM UTC

    We have implemented a fix and are monitoring the situation. We expect ingestion to catch up in the next hour, approximately.

  4. resolved Jul 13, 2026, 02:56 AM UTC

    Ingestion has caught up and alerts have been restored.

Read the full incident report →

Critical July 10, 2026

Error ingestion degraded in US region

Detected by Pingoru
Jul 10, 2026, 10:43 PM UTC
Resolved
Jul 11, 2026, 03:34 AM UTC
Duration
4h 51m
Affected: US Error IngestionUS Errors Alerting
Timeline · 8 updates
  1. investigating Jul 10, 2026, 10:43 PM UTC

    We are currently investigating this issue.

  2. identified Jul 10, 2026, 11:02 PM UTC

    We have identified the problem and are working on a fix, ingested errors are delayed and will be processed once the fix is in place.

  3. identified Jul 11, 2026, 12:04 AM UTC

    We have identified the problem and are working on recovery. New errors are being processed in real time and we are in the process of consuming backlogged errors.

  4. identified Jul 11, 2026, 12:56 AM UTC

    We are still working on recovery. New errors should be processed in real time, and we are working on recovering historical data.

  5. identified Jul 11, 2026, 01:46 AM UTC

    We expect recovery of historical data to be complete within the next 2 hours.

  6. identified Jul 11, 2026, 02:37 AM UTC

    We have processed the majority of our backlog. We are now recovering an additional 25M error events ranging from 22:20 to 23:20 UTC, which should complete in the next 2 hours

  7. monitoring Jul 11, 2026, 03:28 AM UTC

    We have processed the majority of our backlog. We are now recovering the tail of the backlog.

  8. resolved Jul 11, 2026, 03:34 AM UTC

    We have processed the backlog.

Read the full incident report →

Notice July 7, 2026

Incoherent number of processed logs

Detected by Pingoru
Jul 07, 2026, 08:49 AM UTC
Resolved
Jul 07, 2026, 02:36 PM UTC
Duration
5h 46m
Timeline · 2 updates
  1. investigating Jul 07, 2026, 08:49 AM UTC

    We are currently investigating reports of inconsistent reported number of processed logs in Sentry for the last day

  2. resolved Jul 07, 2026, 02:36 PM UTC

    Between July 6th 20:25 UTC and July 7th 12:25 UTC, a wrong configuration change was deployed causing over-sampling of logs, spans and metrics. The configuration change is now reverted and the issue is fixed.

Read the full incident report →

Notice July 6, 2026

DE items ingestion delayed

Detected by Pingoru
Jul 06, 2026, 09:56 PM UTC
Resolved
Jul 07, 2026, 12:55 AM UTC
Duration
2h 58m
Timeline · 4 updates
  1. monitoring Jul 06, 2026, 09:56 PM UTC

    API and dashboards for traces, logs, spans should be restored. Ingestion is still behind but is expected to catch up in the next few hours

  2. monitoring Jul 06, 2026, 11:00 PM UTC

    We are now processing the backlog in EU. Expect delays in ingestion and alerting for spans, logs, and metrics on the order of hours. We will keep this page updated as we make progress.

  3. monitoring Jul 06, 2026, 11:55 PM UTC

    We're continuing to burn down the EU spans, logs, and metrics ingestion backlog.

  4. resolved Jul 07, 2026, 12:55 AM UTC

    The backlgo has been consumed and ingestion and alerting has returned to normal operation

Read the full incident report →

Notice July 2, 2026

Traces, spans, logs inaccesible for query or ingestion in de and us

Detected by Pingoru
Jul 02, 2026, 12:17 AM UTC
Resolved
Jul 02, 2026, 03:56 AM UTC
Duration
3h 39m
Timeline · 4 updates
  1. investigating Jul 02, 2026, 12:17 AM UTC

    We are currently investigating the issue.

  2. identified Jul 02, 2026, 12:34 AM UTC

    We have identified a migration as the cause of the issue. We have reverted the migration in EU and are working on doing so in the US

  3. monitoring Jul 02, 2026, 12:46 AM UTC

    The migration has been reversed in EU and US. Application functionality is restored but there is a 45 minute delay in ingestion in the US and no delay in EU

  4. resolved Jul 02, 2026, 03:56 AM UTC

    All operations are back to normal, as of ~7:30PM PT

Read the full incident report →

Minor June 24, 2026

Delayed Span ingestion, Replay ingestion, and Issue creation in our US region

Detected by Pingoru
Jun 24, 2026, 06:52 PM UTC
Resolved
Jun 24, 2026, 08:48 PM UTC
Duration
1h 56m
Affected: US Replay IngestionUS Span Ingestion
Timeline · 3 updates
  1. identified Jun 24, 2026, 06:52 PM UTC

    We have identified an issue in our US region causing delayed ingestion of spans and replays, as well as delayed creation of some issue types.

  2. monitoring Jun 24, 2026, 07:53 PM UTC

    We have implemented a fix for the problem and are monitoring the situation. We are burning our US region ingestion backlog for replays, spans, and performance issues and will update here as the situation progresses.

  3. resolved Jun 24, 2026, 08:48 PM UTC

    The issue in our US region has been resolved, and ingestion latency is back to normal.

Read the full incident report →

Notice June 12, 2026

Missing SDK Client Reports and Rate Limiting Outcomes

Detected by Pingoru
Jun 12, 2026, 11:30 AM UTC
Resolved
Jun 12, 2026, 11:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 12, 2026, 11:30 AM UTC

    From approximately 10:55 UTC to 11:10 UTC we experienced a loss of outcomes which power the "Stats" in the organization settings. The data loss is purely informational without impact on billing or ingested data.

Read the full incident report →

Notice June 11, 2026

Notification delivery

Detected by Pingoru
Jun 11, 2026, 09:50 AM UTC
Resolved
Jun 11, 2026, 02:48 PM UTC
Duration
4h 57m
Timeline · 7 updates
  1. investigating Jun 11, 2026, 09:50 AM UTC

    We're currently investigating degraded notification delivery.

  2. investigating Jun 11, 2026, 10:53 AM UTC

    We are continuing to investigate the degraded notifications.

  3. investigating Jun 11, 2026, 11:51 AM UTC

    We are continuing to investigate the degraded notifications.

  4. monitoring Jun 11, 2026, 01:13 PM UTC

    Notifications delivery is now close to fully functional in US and DE. We have identified the root cause as caused by one of our cloud providers, and are closely monitoring the situation.

  5. monitoring Jun 11, 2026, 01:23 PM UTC

    We have identified an issue with one of our cloud providers that might have caused some alert notifications to not fire starting at around 4:00 AM GMT+2. Since around 1:30 PM GMT+2, alert notifications are now fully operational in the US region, while delivery is still partially degraded in the EU region.

  6. monitoring Jun 11, 2026, 02:18 PM UTC

    The issue involving some alerts not firing has been mitigated. We will continue to monitor the situation to ensure it does not reoccur.

  7. resolved Jun 11, 2026, 02:48 PM UTC

    This issue has been resolved.

Read the full incident report →

Notice June 10, 2026

Users unable to login to sentry.io

Detected by Pingoru
Jun 10, 2026, 10:05 AM UTC
Resolved
Jun 10, 2026, 10:28 AM UTC
Duration
22m
Timeline · 4 updates
  1. investigating Jun 10, 2026, 10:05 AM UTC

    We are currently investigating the issue.

  2. monitoring Jun 10, 2026, 10:15 AM UTC

    We deployed a fix and are monitoring the situation.

  3. monitoring Jun 10, 2026, 10:17 AM UTC

    We rolled back a configuration change we identified as the root cause of the issue. We'll keep monitoring our systems

  4. resolved Jun 10, 2026, 10:28 AM UTC

    Our auth systems are back operational

Read the full incident report →

Notice June 2, 2026

Elevated errors (EU)

Detected by Pingoru
Jun 02, 2026, 07:45 AM UTC
Resolved
Jun 02, 2026, 07:45 AM UTC
Duration
—
Affected: API
Timeline · 1 update
  1. resolved Jun 02, 2026, 07:45 AM UTC

    Between 06:00-07:00 UTC, we saw increased numbers of API errors in the EU region. The largest impact was between 06:46-07:00. We've implemented a fix and we're no longer seeing elevated errors.

Read the full incident report →

Notice May 28, 2026

Codereview, Autofix, and Ask Seer outage

Detected by Pingoru
May 28, 2026, 01:40 PM UTC
Resolved
May 28, 2026, 02:28 PM UTC
Duration
48m
Timeline · 4 updates
  1. investigating May 28, 2026, 01:40 PM UTC

    We are currently investigating the issue

  2. identified May 28, 2026, 01:55 PM UTC

    We have identified the cause of the issue and are deploying a fix

  3. monitoring May 28, 2026, 02:20 PM UTC

    The fix has been deployed and we are monitoring the situation

  4. resolved May 28, 2026, 02:28 PM UTC

    The issue has been resolved

Read the full incident report →

Notice May 26, 2026

sentry.io DE Region Outage

Detected by Pingoru
May 26, 2026, 08:11 AM UTC
Resolved
May 26, 2026, 08:28 AM UTC
Duration
17m
Timeline · 3 updates
  1. investigating May 26, 2026, 08:11 AM UTC

    We are currently investigating an issue causing 500 errors and preventing access to Sentry.io organizations in the DE region. The US region remains fully operational.

  2. monitoring May 26, 2026, 08:19 AM UTC

    We have implemented a fix and are monitoring.

  3. resolved May 26, 2026, 08:28 AM UTC

    Access to sentry.io is now fully operational

Read the full incident report →

Notice May 22, 2026

Higher than expected latency on sentry.io

Detected by Pingoru
May 22, 2026, 07:42 AM UTC
Resolved
May 22, 2026, 08:23 AM UTC
Duration
40m
Timeline · 3 updates
  1. investigating May 22, 2026, 07:42 AM UTC

    We are currently investigating slow page loads on sentry.io.

  2. monitoring May 22, 2026, 08:08 AM UTC

    We have implemented a fix and are monitoring.

  3. resolved May 22, 2026, 08:23 AM UTC

    Latency for sentry.io has returned to normal.

Read the full incident report →

Notice May 19, 2026

Error Ingestion Delayed in US Region

Detected by Pingoru
May 19, 2026, 03:58 PM UTC
Resolved
May 19, 2026, 06:48 PM UTC
Duration
2h 50m
Timeline · 3 updates
  1. investigating May 19, 2026, 03:58 PM UTC

    We are experiencing ingestion delays for errors in the US region.

  2. investigating May 19, 2026, 05:41 PM UTC

    We are implementing a fix and monitoring the situation. Non-symbolicated issues are not experiencing delays.

  3. resolved May 19, 2026, 06:48 PM UTC

    Ingestion for symbolicated issues is back to normal.

Read the full incident report →

Notice May 18, 2026

Ingestion and alerting delays in US

Detected by Pingoru
May 18, 2026, 01:41 AM UTC
Resolved
May 18, 2026, 07:11 AM UTC
Duration
5h 29m
Timeline · 6 updates
  1. investigating May 18, 2026, 01:41 AM UTC

    We are experiencing ingestion and alerting delays in us for spans, trace metrics, and logs

  2. investigating May 18, 2026, 02:29 AM UTC

    We are still investigating the issue.

  3. investigating May 18, 2026, 03:27 AM UTC

    We are still investigating the issue.

  4. investigating May 18, 2026, 04:27 AM UTC

    We are still investigating the issue.

  5. investigating May 18, 2026, 05:35 AM UTC

    We are continuing to investigate the issue.

  6. resolved May 18, 2026, 07:11 AM UTC

    We have implemented a fix. Ingestion and alerting have returned to normal operation

Read the full incident report →

Notice May 13, 2026

Ingestion and alerting delays in us

Detected by Pingoru
May 13, 2026, 02:38 PM UTC
Resolved
May 13, 2026, 05:56 PM UTC
Duration
3h 17m
Timeline · 3 updates
  1. investigating May 13, 2026, 02:38 PM UTC

    We are experiencing ingestion and alerting delays in us for spans, transactions, and replays

  2. monitoring May 13, 2026, 03:49 PM UTC

    Ingestion and alerting are back to normal. We continue to monitor the situation

  3. resolved May 13, 2026, 05:56 PM UTC

    Ingestion and alerting are back to steady state in the US region.

Read the full incident report →