Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Jun 4, 2026

  1. Fly.ioConsul cluster degradation

    We have restored the degraded Consul cluster. All affected functionality is now working correctly: Unmanaged Postgres and LiteFS with dynamic leases.

    Resolved

  2. GitHubWebhook APIs and UI Degraded

    On May 28, 2026, between 00:54 UTC and 01:19 UTC, some users experienced errors when interacting with the Webhooks API, including webhook delivery history and configuration endpoints. On average, the error rate was 0.28% and peaked at 0.45%. This was due to a bug that caused a single Kubernetes pod to enter a CrashLoopBackOff after receiving a 500 with an empty response body from Cosmos DB.<br /><br />We mitigated the incident by restarting the service. To prevent future incidents, we are pushing a change to handle this response scenario from Cosmos DB appropriately.

    Resolved

  3. LinearIn-App Contact Form experiencing issues

    We've resolved the issue affecting submissions through our in-app contact form, and new support requests are being received successfully again. Our team will continue reviewing and replying to delayed support requests as quickly as possible. We apologize for the delay and appreciate your patience.

    Resolved

  4. LiveKitDegraded Connectivity in US Central

    **Summary** On June 2, 2026, a small subset of users connected to LiveKit Cloud US Central region experienced elevated connection failures between 12:06 and 14:38 UTC. A single node in the region entered a degraded state in which it continued to accept new connections but could not reliably complete the real-time media connection those calls depend on. As a result, a portion of participant connections, including inbound and outbound SIP calls routed through Chicago failed to connect or dropped shortly after starting. We mitigated this by routing SIP traffic away from the affected server, suspending and removing the faulty node, and restoring normal service to the region. **Timeline \(UTC\)** * 12:06 — Start of measurable customer impact * 14:04 — Chicago SIP traffic drained as mitigation * 14:38 — Problematic server suspended; customer impact ends * 15:07 — Chicago SIP service fully restored **Root cause** The incident was caused by a "gray failure" of a single node in the Chicago region, a partial failure in which a server appears healthy to automated systems but is not actually functioning correctly. The server continued to be assigned new calls and reported itself as available, but could not reliably bring the underlying real-time media connections to a fully active state. **Resolution** We first drained SIP traffic out of the Chicago region to route the traffic to other regions, and once the failing node was identified, we suspended and removed the faulty node. After confirming error rates had returned to normal, we restored full SIP service to the region. **Corrective actions and prevention** We are actively addressing the two gaps that allowed a single failing node to impact the region: * **Error aversion in load balancing:** configuring our load balancing servers to automatically detect and steer traffic away from nodes exhibiting this class of failure. * **Monitoring:** closing the alerting gap so that "gray failure" servers which appear healthy but cannot complete connections are detected and alerted promptly.

    Resolved

  5. LinodeService Issue - Block Storage Newark, US

    Between 22:50 UTC on June 2, 2026 and 19:00 UTC on June 3, 2026, some customers experienced intermittent performance degradation and long access times when interacting with the Compute Block Storage cluster in Newark, US. During this period, intermittent component instability triggered intensive background recovery operations. This elevated system load resulted in a temporary degradation of data redundancy, higher read/write latency, and reduced throughput for the affected volumes.  To mitigate the impact, Akamai successfully restored the affected storage drives to operation, stabilizing the cluster and eliminating active customer impact. Following this, additional actions aim to fully restore standard system redundancy. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

    Resolved

  6. DigitalOceanDNS API Service

    Between 09:41 and 11:24 UTC, our Engineering team identified an issue impacting the DNS API service. During this period, users may have experienced issues performing domain and DNS record management operations through the Control Panel and API. Services dependent on DNS API operations, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, were also impacted. Our Engineering team has confirmed that the underlying issue affecting the DNS API service has been fully resolved, and all affected services are now operating normally. If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.

    Resolved

  7. RetoolSign-in issues on Retool Mobile

    This incident is resolved. If you are having issues signing in, please first try the following: - Android: Clear the app cache. Open your Settings, go to Apps (or Applications), tap Retool Mobile, select Storage, and tap Clear cache. - iOS: Delete and reinstall the Retool Mobile app (you'll be prompted to sign in again afterward). Or reach out to support@retool.com

    Resolved

  8. Box[Medium] Degradation of Enterprise Events API

    We recently addressed issues affecting **Enterprise Events API**. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future. ‌ Between 2:31am and 4:45pm PDT on May 14, 2026, some users may have experienced difficulties while working in Box. During this time, customers using the streaming Enterprise Events API experienced delivery delays of up to 6.5 hours. The issue occurred when an internal indexing service unexpectedly generated events at an unconstrained rate, which caused a significant concentrated spike in the total events volume. We were able to resolve the issue by redirecting those events from our streaming enterprise events pipeline for later processing. In addition, we will exclude events originating from internal services from our enterprise events processing pipelines and proactively deprioritize unexpected surges in events to prevent similar issues from occurring in the future. ‌ **Analysis** ‌ There were a number of contributing factors leading to this incident and a reoccurrence on May 18, 2026 between 11:52am and 2:03pm PDT with delivery delays of up to 1.1 hours: ‌ Our internal search indexing service produced events, which should not have been created, at a rate significantly exceeding enterprise usage. These events were published to a queue to be written to the persistent datastore. Also, these events were concentrated in certain access patterns causing hot spotting in some database partitions. The significantly reduced throughput of these partitions caused the subscriber to fall behind. Once these access patterns were identified and the corresponding events removed, service was resolved promptly. Moving forward, these events will not be published. ‌ **Corrective Actions** ‌ The following corrective actions have been completed or are planned: ‌ * **Disable Event Publishing for Search Services** - We are disabling enterprise events from being produced and processed from Box internal services. * **Deprioritize Surge Workloads** - We will monitor for workloads generating significant volumes of event data and deprioritize those events from the primary pipeline. * **Update Incident Response Procedures** - We are updating our runbooks to account for these conditions and related actions. ‌ We are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.  Sincerely, The Box Team

    Resolved

  9. SnykSnyk Recurring Test Email Notification

    We are no longer observing delays affecting Recurring Tests. All tests have caught up, and services are operating normally. The Snyk Incident Response has now been stood down.

    Resolved

  10. LambdaUS-SOUTH-3 Instance Launch / Termination Issues

    Severity Level: [Medium] The incident has been resolved. US-SOUTH-3 launches and terminations are now working as expected. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to whether your service is still impacted by this, please open a support ticket and we’ll get back to you as soon as possible. • https://support.lambdalabs.com/hc/en-us/requests/new To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button.

    Resolved

Jun 3, 2026

  1. HootsuiteX and LinkedIn video publishing

    We can confirm that the video publishing issues impacting X and LinkedIn from Hootsuite have been resolved. Thanks for your patience while our team sorted this out. If you encounter any difficulties with publishing, please contact our Customer Support team.

    Resolved

  2. SlackAdministrators may experience errors in member management.

    The Slack engineering team identified the cause as a recent update that introduced a code change which caused the invite modal to fail when accessed from the Admin page. We rolled back the change and have confirmed the fix is fully deployed and the issue is resolved. Some workspace Admins were unable to add new members to their workspaces via the Manage Members Admin page. In addition, some users attempting to invite people from this page may have encountered an error or been unable to run macros on their workspaces. Workspace Admins should now be able to add new members via the Manage Members admin page. A page refresh may be required. We apologize for the disruption to your work.

    Resolved

  3. KlaviyoShopify API Outage

    The issue affecting Shopify integrations has been resolved, and Shopify data syncing has returned to normal. Automated retry processes will continue to work through the backlog of affected requests. Some customers may see their integration in a failed state, but the retry processes will automatically fix this. Customers who saw errors while setting up a new Shopify integration can retry. This incident has been resolved.

    Resolved

  4. ZapierShopify Service Disruption

    Shopify Service Restored We're pleased to report that Shopify's services have fully recovered and are operating normally. Our Shopify app is now functioning as expected, and Zap triggers and actions are executing successfully. What happened Between approximately 13:06 UTC and 15:28 UTC on June 3rd, Shopify experienced a widespread outage affecting their Admin API, GraphQL endpoints, and multiple other services. This caused failures in both Zap triggers and Zap actions that rely on Shopify integrations. What we did Once Shopify's services were restored, we automatically replayed all impacted Zap runs to ensure your workflows could complete successfully. Any remaining failed runs will be handled by our automatic replay system. No further action is required from you. We've completed our investigation and confirmed all systems are stable. If you experience any further issues with your Shopify integrations, please don't hesitate to reach out to our support team. Thank you for your patience during this incident.

    Resolved

  5. TrueLayerSandbox PIS Settlement Delays

    Payments processed in the Sandbox Merchant Account during the impact window experienced delayed settlement. Impact start time: 29/05/2026, 09:36 UTC Impact end time: 29/05/2026, 13:58 UTC Client actions: None

    Resolved

Older incidents