Sentry Outage History

Sentry is up right now

Sentry had 66 outages in the last 2 years totaling 63h 50m of downtime — averaging 2.7 incidents per month.

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

Source: https://status.getsentry.com

Notice April 6, 2026

Error & Span processing delays in US

Detected by Pingoru
Apr 06, 2026, 03:56 PM UTC
Resolved
Apr 06, 2026, 09:26 PM UTC
Duration
5h 29m
Affected: US Error IngestionUS Span Ingestion
Timeline · 7 updates
  1. investigating Apr 06, 2026, 03:56 PM UTC

    We are investigating processing delays for errors and spans in the US region

  2. identified Apr 06, 2026, 05:11 PM UTC

    We have identified the problem as a load issue in our caching layer and are working to mitigate the issue.

  3. identified Apr 06, 2026, 06:26 PM UTC

    We're continuing to mitigate load in our caching and postgres infrastructure.

  4. identified Apr 06, 2026, 07:04 PM UTC

    We are continuing to mitigate load in our postgres clusters.

  5. identified Apr 06, 2026, 08:04 PM UTC

    We are continuing to mitigate load in our postgres clusters.

  6. monitoring Apr 06, 2026, 08:52 PM UTC

    We have identified the source of postgres load and mitigated it. We are continuing to monitor conditions as backlogs process.

  7. resolved Apr 06, 2026, 09:26 PM UTC

    This incident has been resolved and backlogs have been processed.

Read the full incident report →

Notice March 20, 2026

Ingestion and alerts delayed in US

Detected by Pingoru
Mar 20, 2026, 09:42 PM UTC
Resolved
Mar 21, 2026, 01:09 AM UTC
Duration
3h 27m
Timeline · 2 updates
  1. monitoring Mar 20, 2026, 09:42 PM UTC

    Customers may experience some delay in ingestion and alerts. We are currently burning the backlog

  2. resolved Mar 21, 2026, 01:09 AM UTC

    Ingestions and alerts are caught up and the incident is resolved.

Read the full incident report →

Notice March 16, 2026

Ingestion delayed for transactions, uptime, spans, crons in US

Detected by Pingoru
Mar 16, 2026, 08:17 PM UTC
Resolved
Mar 16, 2026, 10:21 PM UTC
Duration
2h 4m
Timeline · 4 updates
  1. investigating Mar 16, 2026, 08:17 PM UTC

    We are currently investigating the issue. Some alerts may be dropped if they are for older time windows.

  2. identified Mar 16, 2026, 09:39 PM UTC

    We are actively mitigating the issue

  3. monitoring Mar 16, 2026, 10:11 PM UTC

    Ingestion is back to normal, alerts may still be delayed

  4. resolved Mar 16, 2026, 10:21 PM UTC

    The incident has been resolved

Read the full incident report →

Notice March 9, 2026

Alerts delayed for US customers

Detected by Pingoru
Mar 09, 2026, 05:59 PM UTC
Resolved
Mar 09, 2026, 08:37 PM UTC
Duration
2h 38m
Timeline · 3 updates
  1. identified Mar 09, 2026, 05:59 PM UTC

    US customers may experience delay in alerts. We've identified the issue and will be putting in a fix.

  2. monitoring Mar 09, 2026, 06:17 PM UTC

    We are burning the backlog and actively monitoring the progress.

  3. resolved Mar 09, 2026, 08:37 PM UTC

    Ingestion and alert latency is back to normal.

Read the full incident report →

Notice March 2, 2026

Ingestion delays in US and EU regions

Detected by Pingoru
Mar 02, 2026, 07:57 PM UTC
Resolved
Mar 02, 2026, 09:09 PM UTC
Duration
1h 11m
Timeline · 5 updates
  1. investigating Mar 02, 2026, 07:57 PM UTC

    We are currently investigating this issue.

  2. identified Mar 02, 2026, 08:09 PM UTC

    The issue has been identified and the fix is being implemented.

  3. monitoring Mar 02, 2026, 08:29 PM UTC

    We have implemented a fix and are monitoring

  4. monitoring Mar 02, 2026, 08:57 PM UTC

    EU ingestion has been restored and latency is back to normal levels. US continues to recover and will likely be caught up within the next hour.

  5. resolved Mar 02, 2026, 09:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 26, 2026

Intermittent dashboard failures & increased US ingest latency

Detected by Pingoru
Feb 26, 2026, 07:15 PM UTC
Resolved
Feb 26, 2026, 08:56 PM UTC
Duration
1h 41m
Timeline · 3 updates
  1. investigating Feb 26, 2026, 07:15 PM UTC

    We're investigating intermittent failures loading our dashboard (all regions) and increased latency for ingestion of all events types in US

  2. monitoring Feb 26, 2026, 08:02 PM UTC

    Our cloud provider has resolved an underlying problem and our dashboard availability issues have been resolved. We're continuing to process our ingestion backlog and monitor the situation.

  3. resolved Feb 26, 2026, 08:56 PM UTC

    Ingestion backlog has finished processing and our system is now operating normally.

Read the full incident report →

Minor February 26, 2026

Ingestion Issue in US

Detected by Pingoru
Feb 26, 2026, 06:59 PM UTC
Resolved
Feb 26, 2026, 07:41 PM UTC
Duration
41m
Affected: US Transaction Ingestion
Timeline · 3 updates
  1. investigating Feb 26, 2026, 06:59 PM UTC

    We are experiencing an ingestion issue with spans, logs, and metrics. Our teams are currently investigating the problem.

  2. investigating Feb 26, 2026, 07:07 PM UTC

    We also identified that transaction ingestion was also affected.

  3. resolved Feb 26, 2026, 07:41 PM UTC

    We have identified that the core problem is related to the Intermittent dashboard failures. Please follow https://status.sentry.io/incidents/z3g2bjxxwv9l for the latest updates. In the meantime, this will be marked as resolved.

Read the full incident report →

Notice February 24, 2026

Increased error rate in South America ingestion region

Detected by Pingoru
Feb 24, 2026, 01:00 PM UTC
Resolved
Feb 24, 2026, 01:31 PM UTC
Duration
30m
Timeline · 2 updates
  1. investigating Feb 24, 2026, 01:26 PM UTC

    We are currently investigating the issue.

  2. resolved Feb 24, 2026, 01:31 PM UTC

    This incident has been resolved. Ingestion in our South America point-of-presence is fully functional.

Read the full incident report →

Notice February 22, 2026

Calls to Seer in DE are failing

Detected by Pingoru
Feb 22, 2026, 04:21 AM UTC
Resolved
Feb 22, 2026, 04:36 AM UTC
Duration
14m
Timeline · 3 updates
  1. identified Feb 22, 2026, 04:21 AM UTC

    Due to a transient error, some calls to Seer are failing in EU. We identified the issue and are in the process of deploying a fix.

  2. monitoring Feb 22, 2026, 04:32 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 22, 2026, 04:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 9, 2026

EU explore page performance degraded

Detected by Pingoru
Feb 09, 2026, 07:33 PM UTC
Resolved
Feb 09, 2026, 07:39 PM UTC
Duration
5m
Timeline · 2 updates
  1. investigating Feb 09, 2026, 07:33 PM UTC

    We are currently investigating

  2. resolved Feb 09, 2026, 07:39 PM UTC

    The incident has been resolved

Read the full incident report →

Major January 29, 2026

Investigating Issues with Dashboard

Detected by Pingoru
Jan 29, 2026, 11:02 PM UTC
Resolved
Jan 29, 2026, 11:43 PM UTC
Duration
41m
Timeline · 4 updates
  1. investigating Jan 29, 2026, 11:02 PM UTC

    We are currently investigating this issue.

  2. investigating Jan 29, 2026, 11:05 PM UTC

    We are investigating an issue where the Sentry Dashboard may be slow to load.

  3. monitoring Jan 29, 2026, 11:24 PM UTC

    We have identified an issue related to database contention and have issued a fix. We are continuing to monitor the system as it returns to health.

  4. resolved Jan 29, 2026, 11:43 PM UTC

    We have resolved the issue and all systems are working as expected.

Read the full incident report →

Notice January 27, 2026

Delay in span ingestion

Detected by Pingoru
Jan 27, 2026, 02:51 PM UTC
Resolved
Jan 27, 2026, 06:56 PM UTC
Duration
4h 5m
Timeline · 3 updates
  1. investigating Jan 27, 2026, 02:51 PM UTC

    We are investigating a delay in ingesting spans in the US region.

  2. identified Jan 27, 2026, 06:03 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Jan 27, 2026, 06:56 PM UTC

    Ingestion has recovered.

Read the full incident report →

Notice January 23, 2026

Crons ingestion backlogged

Detected by Pingoru
Jan 23, 2026, 06:38 PM UTC
Resolved
Jan 24, 2026, 12:27 AM UTC
Duration
5h 48m
Timeline · 3 updates
  1. investigating Jan 23, 2026, 06:38 PM UTC

    We are currently investigating this issue.

  2. identified Jan 23, 2026, 09:46 PM UTC

    The issue has been identified and we working through backlogs.

  3. resolved Jan 24, 2026, 12:27 AM UTC

    Backlog has been processed and crons should be running as normal

Read the full incident report →

Notice January 12, 2026

UI unavailable

Detected by Pingoru
Jan 12, 2026, 03:30 PM UTC
Resolved
Jan 12, 2026, 05:56 PM UTC
Duration
2h 25m
Timeline · 5 updates
  1. investigating Jan 12, 2026, 03:30 PM UTC

    We are currently investigating this issue.

  2. monitoring Jan 12, 2026, 03:44 PM UTC

    The UI availability issue has been resolved, we're continuing to monitor the situation.

  3. investigating Jan 12, 2026, 04:10 PM UTC

    Our UI is unavailable again, we're investigating the issue.

  4. monitoring Jan 12, 2026, 04:53 PM UTC

    Our UI has recovered from intermittent availability issues due to an increase in load on our DB, the load has recovered and the UI shouldn't experience any further issues. We're continuing to monitor.

  5. resolved Jan 12, 2026, 05:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 12, 2026

Ingestion delays for transactions in EU regions

Detected by Pingoru
Jan 12, 2026, 01:33 PM UTC
Resolved
Jan 12, 2026, 03:16 PM UTC
Duration
1h 43m
Timeline · 4 updates
  1. investigating Jan 12, 2026, 01:33 PM UTC

    We are investigating an issue affecting transaction ingestion in the EU region

  2. investigating Jan 12, 2026, 02:16 PM UTC

    We have implemented a fix and are monitoring the situation closely. No data has been lost.

  3. investigating Jan 12, 2026, 02:21 PM UTC

    We are now ingesting recent transaction data again and are processing old data in the background.

  4. resolved Jan 12, 2026, 03:16 PM UTC

    All backlogs have been processed and no data was lost.

Read the full incident report →

Minor January 8, 2026

Processing delays for spans in US

Detected by Pingoru
Jan 08, 2026, 08:47 PM UTC
Resolved
Jan 08, 2026, 10:21 PM UTC
Duration
1h 33m
Affected: US Span Ingestion
Timeline · 4 updates
  1. investigating Jan 08, 2026, 08:47 PM UTC

    We are currently investigating a delay in processing spans in the US region.

  2. identified Jan 08, 2026, 09:46 PM UTC

    We have identified the issue and a fix is being deployed.

  3. monitoring Jan 08, 2026, 10:04 PM UTC

    A fix has been implemented and we are processing the backlog that formed during the incident.

  4. resolved Jan 08, 2026, 10:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 30, 2025

Increased request timeouts and 50x errors across multiple API endpoints

Detected by Pingoru
Dec 30, 2025, 04:15 PM UTC
Resolved
Dec 30, 2025, 08:04 PM UTC
Duration
3h 49m
Timeline · 3 updates
  1. investigating Dec 30, 2025, 04:15 PM UTC

    We are investigating increased request timeouts and 50x errors across multiple API endpoints that may be impacting service availability.

  2. monitoring Dec 30, 2025, 05:50 PM UTC

    A fix has been implemented, and we are monitoring the results.

  3. resolved Dec 30, 2025, 08:04 PM UTC

    The issue has been resolved, and services are operating normally.

Read the full incident report →

Major December 23, 2025

Database data corruption

Detected by Pingoru
Dec 23, 2025, 12:42 AM UTC
Resolved
Dec 23, 2025, 02:46 AM UTC
Duration
2h 3m
Affected: DashboardSlackPassword-BasedAPIGoogleMicrosoft Symbol ServerStripeGitHubPagerDutyAzure DevOpsElectron Symbol ServerMicrosoft TeamsSAML-Based Single Sign-OnIntegration Pipeline
Timeline · 7 updates
  1. investigating Dec 23, 2025, 12:42 AM UTC

    We are currently investigating this issue.

  2. investigating Dec 23, 2025, 12:49 AM UTC

    We detected a data corruption in one of our databases and investigating the issue

  3. identified Dec 23, 2025, 12:56 AM UTC

    We're implementing a fix for the issue

  4. monitoring Dec 23, 2025, 01:03 AM UTC

    We implemented a fix for the issue and monitoring

  5. monitoring Dec 23, 2025, 01:32 AM UTC

    We are continuing to monitor for any further issues.

  6. monitoring Dec 23, 2025, 01:51 AM UTC

    We restored the impacted services to operational state, while investigating the full impact of the incident

  7. resolved Dec 23, 2025, 02:46 AM UTC

    We had a database corruption where new org creation, user sign-ups, new API Token generation, and new integrations made between 3:45PM and 5:00PM PST were affected and will need to be re-created. No other data were affected. We are very sorry for this inconvenience.

Read the full incident report →

Notice December 20, 2025

Sentry Login Issues

Detected by Pingoru
Dec 20, 2025, 05:14 AM UTC
Resolved
Dec 20, 2025, 08:34 AM UTC
Duration
3h 19m
Timeline · 5 updates
  1. investigating Dec 20, 2025, 05:14 AM UTC

    We are investigating an issue with logging in to the Sentry frontend.

  2. investigating Dec 20, 2025, 06:38 AM UTC

    We are continuing to investigate the issue related to logging in to the Sentry frontend in our US and DE regions.

  3. identified Dec 20, 2025, 06:40 AM UTC

    We have identified the cause of our current login issues and are working on a fix.

  4. monitoring Dec 20, 2025, 07:18 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Dec 20, 2025, 08:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 18, 2025

UI was unavailable between 14:20 and 14:23 UTC

Detected by Pingoru
Dec 18, 2025, 03:05 PM UTC
Resolved
Dec 18, 2025, 03:05 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 18, 2025, 03:05 PM UTC

    Our UI was unavailable between 14:20 UTC and 14:23 UTC due to a bad configuration change, we have reverted the change and service has been restored.

Read the full incident report →

Notice December 10, 2025

Ingestion delays in US

Detected by Pingoru
Dec 10, 2025, 10:38 PM UTC
Resolved
Dec 10, 2025, 10:38 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 10, 2025, 10:38 PM UTC

    All backlogged errors and transactions have been processed, and ingestion is fully functional.

Read the full incident report →

Major December 4, 2025

Unavailability of Sentry Web UI

Detected by Pingoru
Dec 04, 2025, 12:27 AM UTC
Resolved
Dec 04, 2025, 01:19 AM UTC
Duration
52m
Timeline · 4 updates
  1. investigating Dec 04, 2025, 12:27 AM UTC

    We are investigating an issue with the unavailability of the Sentry UI, particularly in the EU region.

  2. identified Dec 04, 2025, 01:00 AM UTC

    We have identified an issue related to networking configuration and are currently deploying a fix.

  3. monitoring Dec 04, 2025, 01:06 AM UTC

    The fix has been deployed and systems are returning to health. We are continuing to monitor the recovery.

  4. resolved Dec 04, 2025, 01:19 AM UTC

    The issue has been resolved.

Read the full incident report →

Notice December 3, 2025

Issues and Discover Page Outage

Detected by Pingoru
Dec 03, 2025, 08:57 PM UTC
Resolved
Dec 03, 2025, 08:57 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 03, 2025, 08:57 PM UTC

    There was an outage of the issues page and discover feature between approximately 12:30 to 12:40pm PST. The issue has been resolved.

Read the full incident report →