Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Jun 5, 2026

  1. GitHubDisruption with some GitHub services

    Between June 1, 2026, 23:00 UTC and June 4, 2026 04:11 UTC, customers experienced delays in Dependabot scheduled version updates. <br /><br />Pull request creation for version updates was delayed, with delays increasing over time and reaching up to two days. Approximately 1.5 million repositories with active Dependabot version update configurations were affected. Dependabot security updates were not affected. The primary cause was changes to an internal platform service that routes requests for Dependabot and other services. <br /> <br />We mitigated the incident by deploying a fix that enables batch enqueuing of update jobs, which significantly increased processing throughput. Once the backlog was drained, Dependabot returned to normal processing times. <br /> <br />To reduce the risk of recurrence, we are working on tuning batch size and concurrency limits for Dependabot update job processing. We are also adding monitoring for job processing lag to enable earlier detection and faster mitigation of similar issues.

    Resolved

  2. TrueLayer EUR PIS Settlement Delays

    We experienced a degraded performance on our Payments products. You may have experienced delays in EUR Payment settlement. The service has recovered and payments are settling in a timely manner. Impact start time: 05/06/2026, 10:15 UTC Impact end time: 05/06/2026, 13:45 UTC Client actions: None

    Resolved

  3. StripeElevated declines on Cartes Bancaires

    Between 07:23 UTC on June 4th and 13:51 UTC on June 5th, we saw elevated error rates and response times with some Cartes Bancaires payments. This is now resolved.

    Resolved

  4. LiveKitElevated latency in Hyderabad region

    We identified a connectivity problem in the Hyderabad cluster. As mitigation, we've drained the cluster to route traffic away from it. Mumbai traffic is unaffected and serving normally. We'll undrain Hyderabad once we're confident it's functioning normally.

    Resolved

  5. LinodeService Issue - Paris (FR-PAR3)

    On May 22, 2026 between approximately 09:10 and 11:30 UTC, connectivity issues were experienced in Paris \(FR-PAR3\) datacenter. During the impact window, customers may have experienced intermittent connection timeouts and errors for services deployed in the Paris datacenter. Our investigation established that connectivity to the host was affected as both of our transits in FRA3 flapped at the exact same time and that triggered high route churn which in result caused packet loss. On analyzing further on why both of our transits flapped at the exact same time, we engaged our Data Center provider and it was identified that during a planned maintenance in the data center, both operator rooms, which support network connectivity, lost power for several minutes, resulting in a complete isolation of the availability zone. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent recurrence.  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. XeroGlobal: Resolved – Platform stable, Post Incident Summary to follow

    # **Post Incident Summary: Xero platform outages \(6 May to 15 May 2026\)** Between 6 and 15 May 2026, customers experienced a series of platform disruptions affecting login, navigation and some product areas. These stemmed from separate technical issues occurring across the period, each identified and resolved by our engineering teams. At no stage was personal data at risk, and there are no concerns relating to the security of the Xero platform. We apologise for the impact these caused. ## **What happened** ### **1. Database disruptions \(6 to 12 May\)** Customers experienced a series of short, repeated disruptions linked to a core platform system responsible for user recognition and organisation access. These intermittent outages occurred sporadically on 6-7 May and 12 May, affecting login and platform navigation. ### **2. AWS infrastructure outage \(8 May\)** A third-party AWS infrastructure incident caused degraded platform performance until traffic was redirected to healthy infrastructure in other locations.  1. Traffic routing incident \(11 May\) An internal traffic routing issue stemming from a configuration issue that resulted in degraded performance in some products until service fully recovered. ## **How we responded** * Around-the-clock engineering oversight to stabilise the platform and investigate root causes. * 24/7 coverage of our customer facing teams to keep customers informed as issues occurred.  * Continuous updates to the[ Xero Status Page](http://status.xero.com) and customer-facing channels throughout each incident.  * For the AWS outage, shifting traffic away from impacted infrastructure drawing on learnings from the October 2025 outage.  * Engineering teams worked in parallel to deployed targeted fixes to minimise impact while investigating the root cause, particularly for the database incident.  * Direct communications to impacted customers, including through Partner channels.  ## **What we’re doing next** We’re continuing work to:  * Improve the stability and resilience of the systems behind the database disruptions. * Enhance our release validation and database change controls * Monitor platform performance closely and continue to improve the speed and clarity of our customer communications during incidents. Our approach is to provide specific information as it becomes available, and where details are still being investigated, to keep customers informed with timely high-level updates while we work towards a resolution We're sorry for the disruption these incidents caused, and remain committed to improving the reliability of our platform and to communicating openly with customers when issues occur.

    Resolved

  7. GitHubDisruption with some GitHub services

    On June 2, 2026, between 21:54 UTC and June 3, 2026 06:45 UTC, the Spark service was degraded and users were unable to store or retrieve data for their Spark apps in one of our hosting regions. Users could still make changes to their app configuration during this time. The error rate peaked at 25% of affected requests to the service. Impact was limited to users whose requests were served through a single affected region; 43 users experienced errors during this window.<br /><br />The root cause was a configuration that referenced a service component by a fixed address rather than a dynamic service endpoint. When the component was replaced, requests could no longer reach the fixed address and began to fail. We resolved the incident by updating the configuration to use a our standard service endpoints that are resilient to component replacement. Recovery time was extended because replacing the component required overrides to a temporary deployment safeguard.<br /><br />We are working to add validation that prevents fixed infrastructure addresses from being used in application configuration outside of test environments and to improve our monitoring to reduce our time to detect.

    Resolved

  8. WorkOSEmail delivery delays

    The backlog of messages have been sent and system performance has returned to its expected state. Sending delays occurred between 2:50pm – 5:18pm PT.

    Resolved

Jun 4, 2026

  1. LiveKitDegraded SIP Connectivity in India

    Summary On June 2, 2026, a subset of users placing or receiving SIP calls through LiveKit Cloud's India region experienced call failures between 12:00 and 12:40 UTC. During a routine maintenance, both of our SIP-serving regions in India were temporarily disabled in error. With no SIP capacity available in India, traffic was routed to our Dubai region, where outbound calls to Indian numbers were rejected at the destination for region-pinned projects and inbound calls targeting India-specific endpoints failed to connect. We mitigated this by re-enabling SIP in the India region and restoring normal capacity. Timeline (UTC) 12:00 — Both India SIP regions disabled during maintenance; start of measurable customer impact 12:40 — India SIP regions re-enabled; customer impact ends Root cause The incident was caused by an operational error during planned maintenance. LiveKit operates three data centers in India, two of which serve SIP traffic. While disabling regions as part of our routine maintenance, the operator disabled both SIP-serving data centers, believing the third data center was also running SIP and would continue to carry customer traffic. Because the third data center does not serve SIP, this removed all SIP capacity in the India region and forced traffic to our Dubai region, where it could not complete region-pinned calls. Resolution Once we identified that India SIP capacity had been removed, we re-enabled SIP in the affected regions, which restored normal inbound and outbound calling in the region.

    Resolved

  2. NetlifyElevated error rates for a subset of sites using Edge Functions

    This incident has been resolved. Between approximately 17:00 and 20:30 UTC, a subset of sites using Edge Functions experienced elevated 504 error rates. We applied a mitigation and error rates have remained at normal levels since. We apologize for  the impact to your sites and visitors.

    Resolved

  3. ElevenLabsOpenAI Image and Video Model Failures

    Starting Thursday, June 4th at approximately 19:12 UTC, we experienced an issue with OpenAI image and video models (GPT Image and Sora) due to a provider-side issue. Requests that used any of these models would fail. This also impacted Flows and Templates. This was fully resolved at 19:52 UTC on the same day.

    Resolved

  4. LambdaSlow Instance Launches in Certain Regions

    Our team has resolved the issue impacting slow instance launches. Thank you for your patience and understanding during this time. ----------------------------------------------------------------------------- In the event you’re unsure as to whether your service was impacted by this incident, please open a support ticket. 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

Older incidents