Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Oct 26, 2026

  1. GitHubDisruption with Dependabot Alerts

    We identified that an advisory-publication driven fan-out was overwhelming Dependabot alert processing on repositories by saturating the queue with its own events, delaying processing of events related to repository pushes.<br /><br />We have now isolated this fan-out and applied a throttle so it runs at a fixed rate and cannot delay other events. This remediation has successfully prevented a new fan-out process impacting users.

    Resolved

  2. SinchService Degradation - Customer Dashboard and Account Balance

    At 2026-10-26 12:58, UTC a planned change caused unforeseen issues affecting the Sinch customer dashboard and our balance calculations. Our engineering teams immediately investigated the issue. Once identified, the change was successfully rolled back and functionality was restored. During the below time frame customers may have experienced issues reaching the Sinch customer dashboard, or experienced problems sending traffic over a subset of accounts due to a block caused by the balance calculation discrepancy. Incident Start Time: 2026-10-26 12:58 UTC Incident End Time: 2026-10-26 15:11 UTC For any inquiries, please contact support@sinch.com

    Resolved

  3. CursorElevated errors for Claude Sonnet 5.5

    We are seeing improvement for Claude Sonnet 5.5 requests. We are continuing to monitor the situation. Some users may still see occasional errors when using this model.

    No longer active

  4. OVHcloud - Public Cloud[EU-WEST-PAR-A][Storage] - Volume Ceph incident notification

    We would like to inform you that an incident affected our Public Cloud Volume (Ceph) offering in the EU-WEST-PAR-A zone. This incident has since been resolved. Please find the details of this incident below : <b>Start time :</b> 25/10/2026 00:00 UTC <b>End time :</b> 26/10/2026 00:00 UTC <b>Impacted Service(s) :</b> Some Volumes experienced degraded performance in the specified zone. <b>Customers Impact :</b> Customers may have experienced high latency on their volumes. Volumes remained available throughout the incident. We thank you for your understanding and patience throughout this incident.

    Resolved

  5. AblyElevated connection errors in us-east-1

    us-east-1 is reenabled and the service is operating normally. The root cause has been confirmed to be a defective Network Load Balancer that was causing a small fraction of connection attempts in the region to fail. We are awaiting a postmortem from AWS on the issue, and will publish our own postmortem here once we have that.

    Resolved

  6. SnykSnyk Test Down in SNYK-US-01

    Services have remained stable throughout the weekend, and we do not expect any further impact. The Snyk Incident Response has been stood down.

    Resolved

  7. CloudflareNetwork Performance Issues in Chicago (ORD)

    Between 08:21 and 09:03 UTC, Cloudflare observed localized network degradation affecting traffic routed through the Chicago (ORD) data center. Customers may have experienced intermittent latency and connection timeouts during this period.

    Resolved

  8. Scaleway[Support] Call Handling Delays

    Due to a high volume of requests, it may be difficult to reach our teams by phone. If needed, we invite you to contact us directly by submitting a ticket so that your request can be processed as quickly as possible. Thank you for your understanding. En raison d’un nombre élevé de demandes, il peut être difficile de joindre nos équipes par téléphone. Au besoin, nous vous invitons à nous contacter directement par ticket afin que votre demande soit prise en charge dans les meilleurs délais. Merci de votre compréhension.

    Degraded

  9. Scaleway[Support] Delays in ticket processing

    En raison d’un volume exceptionnellement élevé de demandes, le traitement des tickets en cours peut prendre plus de temps que d’habitude. Nos équipes sont pleinement mobilisées afin de rétablir la situation et de traiter les demandes dans les meilleurs délais. Nous vous remercions pour votre patience et votre compréhension. Due to a high volume of requests, the processing of ongoing tickets may take longer than usual. Our teams are fully mobilized to restore normal service and handle requests as quickly as possible. Thank you for your patience and understanding.

    Degraded

  10. SnykSnyk Container Degradation in SNYK-US-01

    Services have recovered, and Snyk Container is operating normally in <a href="https://app.snyk.io/">SNYK-US-01</a>. Services have remained stable throughout our monitoring period. The Snyk Incident Response has been stood down.

    Resolved

  11. Fly.ioPacket loss in IAD

    The congestion affecting our upstream provider has been resolved. We are observing a return to normal levels of networking performance in IAD region.

    Resolved

Older incidents