Sentry Outage History

Sentry is up right now

There were 22 Sentry outages since February 9, 2026 totaling 52h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getsentry.com

Notice April 27, 2026

Ingestion delays and intermittent query failures

Detected by Pingoru
Apr 27, 2026, 04:52 PM UTC
Resolved
Apr 27, 2026, 08:59 PM UTC
Duration
4h 7m
Timeline · 4 updates
  1. investigating Apr 27, 2026, 04:52 PM UTC

    We are experiencing delays on our ingestion pipeline. Explorer views are in a degraded state

  2. investigating Apr 27, 2026, 05:31 PM UTC

    Ingestion is now back to normal, we are slowly increasing write traffic to reduce intermittent API failures

  3. monitoring Apr 27, 2026, 05:48 PM UTC

    The system is operating as normal, we are still investigating the root cause

  4. resolved Apr 27, 2026, 08:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 23, 2026

Application errors in Sentry [us]

Detected by Pingoru
Apr 23, 2026, 02:06 AM UTC
Resolved
Apr 23, 2026, 02:17 AM UTC
Duration
10m
Timeline · 3 updates
  1. investigating Apr 23, 2026, 02:06 AM UTC

    We are currently investigating this issue.

  2. monitoring Apr 23, 2026, 02:12 AM UTC

    Ingestion for spans and replays is about 10 minutes behind and catching up. API and Dashboard performance has returned to normal.

  3. resolved Apr 23, 2026, 02:17 AM UTC

    All application features are now operating as normal.

Read the full incident report →

Notice April 22, 2026

Ingestion Issue in US Legacy

Detected by Pingoru
Apr 22, 2026, 08:26 AM UTC
Resolved
Apr 22, 2026, 08:26 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 22, 2026, 08:26 AM UTC

    Between 07:25 UTC and 07:28 UTC, customers sending data to the legacy ingestion endpoint in our US region experienced a brief ingestion disruption lasting approximately 3 minutes. The issue has been fully resolved and ingestion is operating normally. Customers using modern DSN endpoints (`*.ingest.us.sentry.io`) were not affected. The disruption occurred during a scheduled configuration change. We're investing in additional tooling to detect and mitigate this class of issue faster. We apologize for the inconvenience and appreciate your patience.

Read the full incident report →

Notice April 17, 2026

sentry.io intermittent availability

Detected by Pingoru
Apr 17, 2026, 07:04 PM UTC
Resolved
Apr 17, 2026, 07:16 PM UTC
Duration
11m
Timeline · 3 updates
  1. investigating Apr 17, 2026, 07:04 PM UTC

    We are currently investigating this issue.

  2. monitoring Apr 17, 2026, 07:13 PM UTC

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

  3. resolved Apr 17, 2026, 07:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 16, 2026

Span Ingestion Delayed in the EU region

Detected by Pingoru
Apr 16, 2026, 01:36 PM UTC
Resolved
Apr 16, 2026, 04:08 PM UTC
Duration
2h 32m
Timeline · 4 updates
  1. investigating Apr 16, 2026, 01:36 PM UTC

    We are currently investigating this issue.

  2. identified Apr 16, 2026, 02:30 PM UTC

    We have identified the issue and are working on a fix.

  3. monitoring Apr 16, 2026, 03:05 PM UTC

    The delay has recovered and we are monitoring the fix.

  4. resolved Apr 16, 2026, 04:08 PM UTC

    The fix has been rolled out and ingestion is recovered.

Read the full incident report →

Notice April 13, 2026

SSO login broken with Chromium browser

Detected by Pingoru
Apr 13, 2026, 08:31 PM UTC
Resolved
Apr 13, 2026, 09:52 PM UTC
Duration
1h 21m
Timeline · 2 updates
  1. identified Apr 13, 2026, 08:31 PM UTC

    Login with SSO in Chromium browser is broken right now. Signing in using cmd or ctrl + click on the "Login with Provider" button is a workaround you can use while our team fixes the issue.

  2. resolved Apr 13, 2026, 09:52 PM UTC

    Login with SSO in Chromium browser was broken. Users experienced form submission failures due to a bug in CSP. The problem is now fixed.

Read the full incident report →

Notice April 13, 2026

Data ingestion and alerts delayed for US customers

Detected by Pingoru
Apr 13, 2026, 07:13 PM UTC
Resolved
Apr 13, 2026, 07:57 PM UTC
Duration
43m
Timeline · 2 updates
  1. investigating Apr 13, 2026, 07:13 PM UTC

    US customers may experience delay in data ingestion and alerts. The issue is resolved and we are burning the backlog.

  2. resolved Apr 13, 2026, 07:57 PM UTC

    Ingestion and alerts should be back to normal

Read the full incident report →

Notice April 10, 2026

Ingestion Delay – All Data Types

Detected by Pingoru
Apr 10, 2026, 09:20 AM UTC
Resolved
Apr 10, 2026, 11:44 AM UTC
Duration
2h 24m
Timeline · 2 updates
  1. monitoring Apr 10, 2026, 09:20 AM UTC

    We experienced a delay in data ingestion affecting all data types between 08:40 – 08:55 UTC.

  2. resolved Apr 10, 2026, 11:44 AM UTC

    Following the ingestion delay experienced between 08:40 – 08:55 UTC, all systems are now fully operational. Data ingestion is running normally across all data types.

Read the full incident report →

Notice April 7, 2026

Subcription management page not working

Detected by Pingoru
Apr 07, 2026, 09:36 PM UTC
Resolved
Apr 07, 2026, 11:42 PM UTC
Duration
2h 5m
Timeline · 3 updates
  1. identified Apr 07, 2026, 09:36 PM UTC

    We have identified an issue for customers trying to access their subscription page. we are working on a fix

  2. monitoring Apr 07, 2026, 10:28 PM UTC

    We are rolling out a fix

  3. resolved Apr 07, 2026, 11:42 PM UTC

    Hot fix merged, all customers can access their subscription pages now.

Read the full incident report →

Notice April 7, 2026

US delays and ingestion and issues in querying across pipelines

Detected by Pingoru
Apr 07, 2026, 09:02 PM UTC
Resolved
Apr 07, 2026, 09:23 PM UTC
Duration
21m
Timeline · 2 updates
  1. monitoring Apr 07, 2026, 09:02 PM UTC

    We performed a manual change that caused degraded performance and delayed ingestion in spans, crons, replays, and uptime that caused issues between 13:45 and 13:52 PT. The change has been cancelled and operations have returned to normal

  2. resolved Apr 07, 2026, 09:23 PM UTC

    This incident has been resolved

Read the full incident report →

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 12, 2026

Ingestion delays for spans, logs, traces, and metrics in US

Detected by Pingoru
Feb 12, 2026, 05:34 AM UTC
Resolved
Feb 13, 2026, 12:57 AM UTC
Duration
19h 22m
Timeline · 10 updates
  1. investigating Feb 12, 2026, 05:34 AM UTC

    We are currently investigating the issue

  2. identified Feb 12, 2026, 08:34 AM UTC

    We identified a problem with our Zookeeper cluster and fixed it. We now need to ingest the backlog.

  3. investigating Feb 12, 2026, 09:43 AM UTC

    We are investigating the resurfaced Zookeeper issue

  4. monitoring Feb 12, 2026, 03:00 PM UTC

    We've identified and fixed the issue. We are burning the backlog and actively monitoring the progress.

  5. monitoring Feb 12, 2026, 04:54 PM UTC

    We are continuing to process the backlog and are still monitoring the recovery.

  6. monitoring Feb 12, 2026, 07:17 PM UTC

    We are still continuing to process the backlog and are still monitoring the recovery.

  7. monitoring Feb 12, 2026, 09:35 PM UTC

    We are still continuing to process the backlog and are still monitoring the recovery.

  8. monitoring Feb 12, 2026, 11:44 PM UTC

    We are still continuing to process the backlog and are still monitoring the recovery.

  9. monitoring Feb 13, 2026, 12:38 AM UTC

    Ingestion is back to normal, alerts may still be delayed. We will continue to monitor the recovery.

  10. resolved Feb 13, 2026, 12:57 AM UTC

    We have resolved the issue, and our system is now working as expected

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 →

Looking to track Sentry downtime and outages?

Pingoru polls Sentry's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Sentry reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Sentry alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Sentry for free

5 free monitors · No credit card required