Sentry

Affected: Slack, Integration Pipeline

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

Started during GitHub: Delays for Pull Requests and Webhook deliveries.

1. investigating 2026-10-21 17:53 UTC

   We are working on mitigating an incident that affects external integrations such as GitHub, Slack, and Autofix PRs. No data is being lost.

2. resolved 2026-10-21 18:14 UTC

   We are working on mitigating an incident that affects external integrations such as GitHub, Slack, and Autofix PRs. No data is being lost.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-21 08:54 UTC

   We are currently investigating an issue affecting US Sentry region

2. monitoring 2026-10-21 09:23 UTC

   We have identified the problem, and addressed the cause of the outage. We will continue monitoring the fix

3. monitoring 2026-10-21 09:40 UTC

   Native events ingestion is still delayed, we are processing the backlog of native events

4. resolved 2026-10-21 09:53 UTC

   Native events ingestion has caught up, everything should be operational now

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-20 18:20 UTC

   Users are experiencing issues loading the Sentry dashboard. We are investigating the problem.

2. investigating 2026-10-20 18:58 UTC

   We have mitigated the immediate problem, but are continuing to investigate the cause. You may continue to experience interruptions using our UI and API. We will update as we know more.

3. investigating 2026-10-20 19:51 UTC

   The impact is mitigated and the dashboard/API are currently operational. We are continuing to work on a more durable fix. We will update the statuspage again as things progress.

4. monitoring 2026-10-20 20:44 UTC

   We have put a better mitigation in place while we work on a fix. Things continue to be operational and we are monitoring the situation.

5. resolved 2026-10-20 21:38 UTC

   We have a mitigation in place that should prevent this from occurring again in the short term while we continue to work on a proper fix. We are going to close the Statuspage incident for now, but will reopen it if things become unstable again.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-19 20:39 UTC

   Sentry.io is taking a long time to load and ingestion may be impacted. We will update as we know more.

2. investigating 2026-10-19 20:43 UTC

   Impact is isolated to our US region customers. Alerting is also impact by this incident.

3. monitoring 2026-10-19 20:53 UTC

   We have identified and addressed the cause of the outage. Things are moving again and we are burning through ingestion backlogs. We will update the statuspage again as things progress.

4. monitoring 2026-10-19 21:10 UTC

   We are still working through our ingestion backlogs. At this point, it looks like we'll be caught up in the next 20 minutes.

5. resolved 2026-10-19 21:32 UTC

   Backlogs have been processed and we are back to normal.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-14 05:46 UTC

   In the EU we've identified an issue with ingestion into EAP and are working towards a fix.

2. identified 2026-10-14 06:09 UTC

   In the EU we've identified an issue with ingestion into EAP and have implemented a fix. Waiting on ingestion burn down.

3. monitoring 2026-10-14 07:46 UTC

   In the EU we've identified an issue with ingestion into EAP and have implemented a fix. Waiting on ingestion lag burn down.

4. resolved 2026-10-14 08:20 UTC

   The issue with EAP ingestion in EU has been resolved.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-06 18:57 UTC

   We are investigating an issue impacting our dashboard in both US and EU regions

2. identified 2026-10-06 19:04 UTC

   We have identified the issue and are working on a fix

3. monitoring 2026-10-06 19:20 UTC

   We have deployed a fix and are things are recovering. We are continuing to monitor the situation.

4. resolved 2026-10-06 19:40 UTC

   Dashboard is back to operational.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-18 10:17 UTC

   We are currently investigating an issue affecting spans ingestion in the EU region

2. investigating 2026-09-18 10:56 UTC

   We have identified a networking issue with an upstream provider and are working on mitigations.

3. resolved 2026-09-18 10:58 UTC

   We have identified a networking issue with an upstream provider and are working on mitigations.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-18 08:36 UTC

   We are currently investigating an issue that causes new errors to be delayed in the EU region.

2. investigating 2026-09-18 09:00 UTC

   We have implemented a mitigation and are starting to recover.

3. investigating 2026-09-18 09:53 UTC

   We are processing real-time data again and are working on burning our backlog.

4. monitoring 2026-09-18 09:54 UTC

   We are processing real-time data again and are working on burning our backlog.

5. monitoring 2026-09-18 10:56 UTC

   We have identified a networking issue with an upstream provider and are working on mitigations.

6. identified 2026-09-18 10:58 UTC

   We have identified a networking issue with an upstream provider and are working on mitigations.

7. identified 2026-09-18 11:45 UTC

   Error ingestion is fully operational. We are currently working on recovering real-time processing of spans.

8. resolved 2026-09-18 11:57 UTC

   We are processing real-time data for all data types again.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-10 16:13 UTC

   We are investigating degraded ingestion in US.

2. investigating 2026-09-10 16:52 UTC

   We are continuing to monitor delayed ingestion.

3. resolved 2026-09-10 17:10 UTC

   Ingestion is now operating normally.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-10 15:25 UTC

   During migration to new control silo region we started to observe increased number of 500 errors. Migration procedure was rolled back.

2. monitoring 2026-09-10 16:07 UTC

   Issue were identified and fixes were applied. We continue to monitor situation

3. resolved 2026-09-10 16:26 UTC

   Issue fully resolved

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-01 14:16 UTC

   We are experiencing slow ingestion for spans in US

2. investigating 2026-09-01 15:40 UTC

   We are continuing to investigate an issue that affects spans ingestion latency

3. investigating 2026-09-01 16:41 UTC

   We are continuing to investigate an issue that affects spans ingestion latency

4. investigating 2026-09-01 17:50 UTC

   We are continuing to investigate an issue that affects spans ingestion latency

5. monitoring 2026-09-01 18:30 UTC

   A fix has been implemented, and latency is coming down.

6. monitoring 2026-09-01 19:31 UTC

   Latency is almost fully recovered.

7. resolved 2026-09-01 20:29 UTC

   Spans ingestion is now operating normally.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-01 08:01 UTC

   We are currently investigating what's going on and why requests timing out

2. monitoring 2026-09-01 08:57 UTC

   We identified the issue and rolled out a configuration change

3. monitoring 2026-09-01 09:03 UTC

   We're monitoring the implemented fix

4. resolved 2026-09-01 11:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sentry's status page.

Affected: US Error Ingestion, US Errors Alerting, API, US Transaction Ingestion, US Attachment Ingestion, US Profile Ingestion, US Spans Alerting, US Replay Ingestion, US Span Ingestion, US Cron Monitoring, US Uptime Monitoring, Integration Pipeline, Custom Metrics (beta), US Size Analysis Ingestion, Seer, US Snapshot Ingestion

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-31 20:31 UTC

   we are investigating a failure in our infrastructure that is delaying ingestion

2. investigating 2026-08-31 20:52 UTC

   We have identified the culprit and are rolling out a fix

3. monitoring 2026-08-31 21:02 UTC

   The fix has been deployed and our ingestion backlogs are recovering

4. investigating 2026-08-31 21:12 UTC

   API is experiencing issues

5. monitoring 2026-08-31 21:16 UTC

   Our systems are recovering from an ingestion backlog

6. monitoring 2026-08-31 21:26 UTC

   Our systems are recovering from an ingestion backlog, webhooks are currently delayed

7. resolved 2026-08-31 22:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-27 09:24 UTC

   We are currently investigating an issue that affects the availability of our product and API

2. investigating 2026-08-27 09:53 UTC

   We are continuing to investigate an issue that affects the availability of our product and API

3. investigating 2026-08-27 09:56 UTC

   We are continuing to investigate an issue that affects the availability of our product and API

4. investigating 2026-08-27 10:49 UTC

   We are continuing to investigate an issue that affects the availability of our product and API

5. investigating 2026-08-27 11:25 UTC

   We are continuing to investigate an issue that affects the availability of our product and API

6. monitoring 2026-08-27 11:44 UTC

   We have identified and mitigated an issue that affected the availability of our product and API, and are now monitoring while our systems recover

7. monitoring 2026-08-27 12:48 UTC

   We are continuing to monitor while our systems recover after an issue that affected the availability of our product and API

8. monitoring 2026-08-27 13:39 UTC

   We keep monitoring our systems while we recover to our usual latency

9. monitoring 2026-08-27 13:58 UTC

   Our latency is now back to normal. We'll keep monitoring our systems a few more time before declaring the incident as resolved

10. resolved 2026-08-27 15:41 UTC

    Our latency is now back to normal. Incident resolved

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-26 16:17 UTC

   We are experiencing slower page loads and API responses due to a database issue in us

2. identified 2026-08-26 17:53 UTC

   We have identified a potential cause of excess traffic and are working on a fix.

3. monitoring 2026-08-26 18:47 UTC

   We have put a fix into place and are monitoring the situation

4. monitoring 2026-08-26 20:04 UTC

   We have put a fix into place and are monitoring the situation

5. resolved 2026-08-26 20:36 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-25 09:38 UTC

   We are investigating delays in error alerts in the US region, up to 10 minutes

2. investigating 2026-08-25 11:09 UTC

   We are continuing to investigate the issue

3. identified 2026-08-25 12:27 UTC

   We have identified the issue and implemented a fix.

4. resolved 2026-08-25 12:38 UTC

   Error alerting is back to normal.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-18 21:42 UTC

   We are currently investigating a delay in evaluating alerts in the US region.

2. identified 2026-08-18 21:56 UTC

   We have identified the cause and are working to determine a mitigation. This is only affecting US right now.

3. monitoring 2026-08-18 22:15 UTC

   We have implemented a fix and the systems are recovering. We are monitoring to ensure that backlogs are proessed.

4. resolved 2026-08-18 22:21 UTC

   The problem has been resolved, all backlogs have cleared and everything is operational again.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: A configuration change caused the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-13 17:47 UTC

   We are currently investigating ingestion delays for spans and transactions in DE

2. investigating 2026-08-13 17:59 UTC

   We are currently investigating ingestion delays for spans and transactions in DE and US

3. investigating 2026-08-13 18:07 UTC

   We are currently investigating ingestion delays for spans, transactions and alerts in DE and US

4. identified 2026-08-13 18:35 UTC

   We've identified the source of latency and are reverting that change.

5. monitoring 2026-08-13 19:34 UTC

   The problematic change has been reverted and we're processing backlogs.

6. monitoring 2026-08-13 19:53 UTC

   The problematic change has been reverted and we're processing backlogs.

7. monitoring 2026-08-13 20:32 UTC

   We've recovered all ingestion latency in DE. In US, errors have processed their backlog and we continue to make progress on spans in US.

8. monitoring 2026-08-13 21:22 UTC

   We're continuing to make progress on the span ingestion backlog in US.

9. monitoring 2026-08-13 22:13 UTC

   We continue to make progress on the spans backlog with an estimated completion time of 15 minutes.

10. resolved 2026-08-13 22:27 UTC

    All backlogs have been processed.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-12 21:58 UTC

   We are currently investigating error ingestion latency in US.

2. identified 2026-08-12 22:43 UTC

   We've mitigated the source of ingestion latency and are processing the backlog.

3. resolved 2026-08-12 22:52 UTC

   Backlogs have been processed

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-12 12:58 UTC

   We are currently investigating reports of API timeouts for the Sentry API in our US region.

2. monitoring 2026-08-12 13:14 UTC

   API performance has returned to expected levels. We are continuing to monitor.

3. resolved 2026-08-12 14:24 UTC

   API performance has returned to expected levels.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-12 11:45 UTC

   We are actively investigating this issue.

2. investigating 2026-08-12 12:36 UTC

   We've identified the root cause and are actively working on mitigation.

3. identified 2026-08-12 13:28 UTC

   A fix has been made and the backlog is being processed.

4. monitoring 2026-08-12 14:21 UTC

   We're processing new events and alerts in realtime, and continue to process the tail of the backlog.

5. resolved 2026-08-12 14:48 UTC

   The backlog has been processed

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-07 16:21 UTC

   We are currently investigating the issue

2. identified 2026-08-07 16:30 UTC

   We've put a fix in place and are monitoring. We anticipate catching up to ingestion within 1 hour

3. monitoring 2026-08-07 16:48 UTC

   Ingestion latency for spans, crons, and logs is back to normal levels.

4. resolved 2026-08-07 17:08 UTC

   The ingestion delay is resolved

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-06 08:59 UTC

   We are actively investigating this issue.

2. investigating 2026-08-06 09:55 UTC

   We are still actively investigating this issue.

3. investigating 2026-08-06 10:25 UTC

   We've identified the issue causing delays in ingestion and have applied a fix. We'll update again when we return to real time processing.

4. monitoring 2026-08-06 10:50 UTC

   We're processing new events in real time, and are working through a backlog of events now.

5. resolved 2026-08-06 11:21 UTC

   We've processed all backlogged events and have fully recovered.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-27 16:23 UTC

   We are experiencing issues with error and profile ingestion in our US region and are investigating the issue.

2. identified 2026-07-27 16:56 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 2026-07-27 18:07 UTC

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

4. resolved 2026-07-27 18:27 UTC

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

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-21 10:30 UTC

   We are actively investigating this issue

2. investigating 2026-07-21 11:26 UTC

   We are still actively investigating this issue

3. investigating 2026-07-21 12:20 UTC

   We are still actively investigating this issue

4. monitoring 2026-07-21 13:04 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 2026-07-21 13:55 UTC

   We're still burning through our spans backlog

6. resolved 2026-07-21 14:14 UTC

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

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-20 11:11 UTC

   we are investigating an issue affecting errors ingestion in the DE/EU region

2. identified 2026-07-20 11:41 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.

3. identified 2026-07-20 12:10 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.

4. identified 2026-07-20 12:24 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.

5. identified 2026-07-20 13:19 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.

6. identified 2026-07-20 13:47 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.

7. monitoring 2026-07-20 14:30 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.

8. monitoring 2026-07-20 14:50 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.

9. monitoring 2026-07-20 16:09 UTC

   We are still burning the backlog of EU region error events received during the incident. We are around halfway through the backlog.

10. resolved 2026-07-20 16:57 UTC

    We have fully burned the backlog of EU error events ingested during the incident. Latency is normal across all event types.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-16 21:06 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 2026-07-17 00:44 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 2026-07-17 01:28 UTC

   The webhook backlog is processing.

4. identified 2026-07-17 02:44 UTC

   The webhook backlog is processing.

5. identified 2026-07-17 03:49 UTC

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

6. identified 2026-07-17 04:50 UTC

   The webhook backlog is processing.

7. identified 2026-07-17 05:49 UTC

   The webhook backlog is processing.

8. resolved 2026-07-17 06:57 UTC

   The webhook backlog is now resolved.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-14 14:44 UTC

   We are currently investigating the issue.

2. investigating 2026-07-14 15:42 UTC

   We continue to investigate the issue.

3. identified 2026-07-14 16:42 UTC

   We have identified the problem and are working on recovery.

4. identified 2026-07-14 16:49 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 2026-07-14 17:02 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 2026-07-14 17:40 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 2026-07-14 18:16 UTC

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

8. resolved 2026-07-14 19:32 UTC

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

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-13 11:51 UTC

   We are investigating ingestion delays.

2. identified 2026-07-13 12:24 UTC

   We identified the issue and restoring service.

3. monitoring 2026-07-13 12:41 UTC

   Service has been restored and we are actively monitoring the situation

4. resolved 2026-07-13 14:25 UTC

   Service has been restored.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-13 00:58 UTC

   We are currently investigating the issue.

2. identified 2026-07-13 01:46 UTC

   We have identified the problem and are working to restore ingestion

3. monitoring 2026-07-13 02:01 UTC

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

4. resolved 2026-07-13 02:56 UTC

   Ingestion has caught up and alerts have been restored.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-10 22:43 UTC

   We are currently investigating this issue.

2. identified 2026-07-10 23:02 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 2026-07-11 00:04 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 2026-07-11 00:56 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 2026-07-11 01:46 UTC

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

6. identified 2026-07-11 02:37 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 2026-07-11 03:28 UTC

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

8. resolved 2026-07-11 03:34 UTC

   We have processed the backlog.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-07 08:49 UTC

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

2. resolved 2026-07-07 14:36 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.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-07-06 21:56 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 2026-07-06 23:00 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 2026-07-06 23:55 UTC

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

4. resolved 2026-07-07 00:55 UTC

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

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-06 00:35 UTC

   We are investigating consumers for spans, logs and metrics are not ingested

2. monitoring 2026-07-06 00:44 UTC

   The issue was fixed and we are now monitoring the fix

3. monitoring 2026-07-06 02:07 UTC

   Backlog is being consumed and we’re still monitoring recovery

4. monitoring 2026-07-06 05:48 UTC

   We're still consuming the backlog and monitoring the situation.

5. investigating 2026-07-06 13:30 UTC

   We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.

6. investigating 2026-07-06 14:26 UTC

   We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.

7. investigating 2026-07-06 15:22 UTC

   We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.

8. investigating 2026-07-06 16:18 UTC

   We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.

9. investigating 2026-07-06 17:14 UTC

   We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.

10. monitoring 2026-07-06 18:30 UTC

    We've taken steps to mitigate the issue in the US and we're burning our backlog and expect to be have it fully consumed in about 4 hours. We're continuing to investigate the delayed ingestion in our EU region.

11. monitoring 2026-07-06 19:26 UTC

    We're continuing burning our backlog in US and expect to be have it fully consumed in about 1 hour. We're continuing to investigate the delayed ingestion in our EU region.

12. monitoring 2026-07-06 20:29 UTC

    We're continuing burning our backlog in US and expect to be have it fully consumed within the next hour. We're continuing to investigate the delayed ingestion in our EU region. EU API and dashboards are also affected by this incident.

13. monitoring 2026-07-06 21:28 UTC

    We're still burning the last of our backlog in US and expect to be back to normal the next hour. We're continuing to investigate the delayed ingestion in our EU region. EU API and dashboards are also affected by this incident.

14. resolved 2026-07-06 22:18 UTC

    US ingestion is back to normal. EU ingestion is still delayed, but we are now recovering. We have created a new Statuspage incident for tracking EU, follow that for further updates: https://status.sentry.io/incidents/7tfjf5k3m0g3

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-02 00:17 UTC

   We are currently investigating the issue.

2. identified 2026-07-02 00:34 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 2026-07-02 00:46 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 2026-07-02 03:56 UTC

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

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-30 21:16 UTC

   We are currently investigating the issue

2. investigating 2026-06-30 21:42 UTC

   We continue to investigate the issue. Ingestion delays are around 40 minutes now.

3. investigating 2026-06-30 22:50 UTC

   We continue to investigate the issue

4. investigating 2026-06-30 23:31 UTC

   We continue to investigate the issue.

5. investigating 2026-07-01 00:27 UTC

   Our database is stabilized. We are attempting a fix to increase the ingestion rate.

6. investigating 2026-07-01 01:29 UTC

   Our ingestion fix was not successful. We are continuing to investigate possible solutions

7. investigating 2026-07-01 02:25 UTC

   We are attempting additional mitigations to restore ingestion for logs, spans, and traces in the US

8. monitoring 2026-07-01 03:30 UTC

   We are currently burning down the ingestion backlog, and estimate that it will be complete by 2AM PT 2026-07-01.

9. monitoring 2026-07-01 04:26 UTC

   We continue to monitor the situation

10. monitoring 2026-07-01 05:22 UTC

    We continue to monitor the situation

11. monitoring 2026-07-01 06:14 UTC

    We continue to monitor the fix. Ingestion is around 45 minutes behind and improving. APIs and dashboards are functioning normally (outside of data waiting to be ingested).

12. resolved 2026-07-01 10:00 UTC

    Data is now processed live and the system are fully operational.

Excerpts are shortened. Read the full incident on Sentry's status page.

Affected: US Replay Ingestion, US Span Ingestion

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-24 18:52 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 2026-06-24 19:53 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 2026-06-24 20:48 UTC

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

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-06-12 11:30 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.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-11 09:50 UTC

   We're currently investigating degraded notification delivery.

2. investigating 2026-06-11 10:53 UTC

   We are continuing to investigate the degraded notifications.

3. investigating 2026-06-11 11:51 UTC

   We are continuing to investigate the degraded notifications.

4. monitoring 2026-06-11 13:13 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 2026-06-11 13:23 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...

6. monitoring 2026-06-11 14:18 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 2026-06-11 14:48 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-10 10:05 UTC

   We are currently investigating the issue.

2. monitoring 2026-06-10 10:15 UTC

   We deployed a fix and are monitoring the situation.

3. monitoring 2026-06-10 10:17 UTC

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

4. resolved 2026-06-10 10:28 UTC

   Our auth systems are back operational

Excerpts are shortened. Read the full incident on Sentry's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-06-02 07:45 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.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-28 13:40 UTC

   We are currently investigating the issue

2. identified 2026-05-28 13:55 UTC

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

3. monitoring 2026-05-28 14:20 UTC

   The fix has been deployed and we are monitoring the situation

4. resolved 2026-05-28 14:28 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-26 08:11 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 2026-05-26 08:19 UTC

   We have implemented a fix and are monitoring.

3. resolved 2026-05-26 08:28 UTC

   Access to sentry.io is now fully operational

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-22 07:42 UTC

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

2. monitoring 2026-05-22 08:08 UTC

   We have implemented a fix and are monitoring.

3. resolved 2026-05-22 08:23 UTC

   Latency for sentry.io has returned to normal.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-19 15:58 UTC

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

2. investigating 2026-05-19 17:41 UTC

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

3. resolved 2026-05-19 18:48 UTC

   Ingestion for symbolicated issues is back to normal.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-05-19 14:05 UTC

   We've put in fixes and are monitoring the situation

2. resolved 2026-05-19 14:18 UTC

   Ingestion and alerting back to normal

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-18 01:41 UTC

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

2. investigating 2026-05-18 02:29 UTC

   We are still investigating the issue.

3. investigating 2026-05-18 03:27 UTC

   We are still investigating the issue.

4. investigating 2026-05-18 04:27 UTC

   We are still investigating the issue.

5. investigating 2026-05-18 05:35 UTC

   We are continuing to investigate the issue.

6. resolved 2026-05-18 07:11 UTC

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

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-13 14:38 UTC

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

2. monitoring 2026-05-13 15:49 UTC

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

3. resolved 2026-05-13 17:56 UTC

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

Excerpts are shortened. Read the full incident on Sentry's status page.

Affected: Dashboard, API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-12 12:28 UTC

   We are seeing increased UI and API timeouts and errors, due to an overloaded database cluster. Ingestion and alerting should not be affected.

2. investigating 2026-05-12 13:51 UTC

   We are continuing to investigate increased UI and API timeouts and errors

3. investigating 2026-05-12 15:43 UTC

   We are continuing to investigate increased UI and API timeouts and errors.

4. monitoring 2026-05-12 17:00 UTC

   We've applied a configuration change to mitigate the API/UI errors being experienced.

5. resolved 2026-05-12 22:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-11 15:32 UTC

   We are seeing increased UI and API timeouts and errors, due to an overloaded database cluster. Ingestion and alerting should not be affected

2. investigating 2026-05-11 18:57 UTC

   We are continuing to investigate degraded database performance.

3. investigating 2026-05-11 19:28 UTC

   Ingestion for spans, replays, and crons is delayed by about 15 minutes.

4. investigating 2026-05-11 20:25 UTC

   Our event database continues to have issues and we are actively investigating the issue.

5. investigating 2026-05-11 21:08 UTC

   We are working on restoring normal service. API and application performance should be improved, ingestion still has delays.

6. monitoring 2026-05-11 21:39 UTC

   We have implemented a fix and are monitoring the situation

7. resolved 2026-05-11 22:11 UTC

   Database performance has returned to normal

Excerpts are shortened. Read the full incident on Sentry's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-06 07:42 UTC

   We are currently investigating the issue.

2. resolved 2026-05-06 07:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sentry's status page.