Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Aug 26, 2026

  1. LambdaNetwork Maintenance in us-east-3

    Severity Level: [Low] Status Completed (Maintenance) Summary The scheduled maintenance on our networking infrastructure in us-east-3 has been completed successfully. Service health was monitored throughout the work and all systems are operating normally. Thank you for your patience. ----------------------------------------------------------------------------- In the event you’re unsure as to whether your service is 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

  2. LiveKitElevated inference errors — US East

    Between 08:47 and 08:54 UTC, the service that routes LLM, STT and TTS requests through LiveKit Inference in our US East region was unavailable, causing inference requests from agents in that region to fail or time out. Sessions depending on those responses may have degraded or ended prematurely. Replacement capacity came online at 08:54 UTC and request volumes returned fully to normal levels by 09:02 UTC. We have confirmed no further impact since then. The cause was a loss of capacity during automated infrastructure maintenance. We have identified fixes to prevent a recurrence.

    Resolved

  3. MakeDelay in scenario executions affecting the EU1 (eu1.make.com)

    There was an issue causing delays with scenario executions on the EU1 (eu1.make.com) region between 10:45 and 11:05 CEST. The issue has been resolved, and the service is now fully operational and working normally. Thank you for your patience, and we apologize for any inconvenience this may have caused.

    Resolved

  4. InngestConnect Message Routing Delays - for Connect users only

    Between August 26 00:31 to 01:13 UTC, a subset of customers using Inngest Connect experienced delayed and failed function runs due to an internal networking issue that disrupted connectivity between Connect services. We reverted the change and restored service. Although Connect buffers worker responses, stalled internal API calls delayed acknowledgements and subsequent replies. In some cases, request forwarding failed even after a buffered response had been received. We fixed the root cause, improved Connect’s failure handling, and enhanced our internal observability so we can detect and respond more quickly to similar problems in the future. Affected customers should review failed Connect runs during the incident window and replay them after confirming that doing so is safe and idempotent.

    Resolved

Aug 25, 2026

  1. CircleCIGitHub Login Disruption

    Between 19:49 UTC and 21:07 UTC on August 25, 2026, customers attempting to log in to CircleCI using GitHub were unable to sign in, and received an error from GitHub stating the callback URL was invalid. Customers who were already logged in were not affected. The issue has been resolved and GitHub login is functioning normally. We thank you for your patience while our team worked on implementing a fix.

    Resolved

  2. SnowflakeINC20000163

    Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000163](https://community.snowflake.com/s/article/INC20000163)

    Resolved

  3. BunnyDatabase Controller Outage

    After monitoring the affected services, we have confirmed that Database management and idle Database activation are operating normally.

    Resolved

  4. AmplitudeBrief Service Disruption

    Incident timeline Resolved — Amplitude is accessible once again, and customers should be able to access the platform as expected. Posted Aug 25, 2026 - 14:03 PT Investigating — Since approximately 13:48 PT, some customers may have experienced a brief interruption when using Amplitude. Posted Aug 25, 2026 - 13:48 PT We apologize for the disruption.

    Resolved

  5. GitHubDisruption with Copilot for access to some models

    On August 10, 2026, between 19:48 UTC and 20:49 UTC, GitHub Copilot users saw an incomplete list of available models. During this window, the service could return as few as one model instead of the full catalog. Requests that tried to use a model missing from that shortened list failed with a "model not found" error. Copilot requests that used an available model were not affected. This did not affect customers on data-residency (Proxima) environments.<br /><br />The issue was caused by a change to how model data was published, which our systems could not read back correctly and fell back to a limited default list.<br /><br />We mitigated the incident by 20:49 UTC and deployed a fix to prevent immediate recurrence by 21:50 UTC. We are adding validation and retry safeguards so that model data is verified before it is served.<br /><br />We apologize for the disruption.

    Resolved

  6. GitHubDisruption with Login and Release Asset downloads

    On August 12 and 13, 2026, some anonymous (logged-out) requests to github.com experienced HTTP 5xx errors when loading pages like the sign-in page, and when downloading release assets, due to an unusual traffic pattern that repeatedly overloaded a part of our infrastructure that serves these types of requests. There were three windows of impact: (1) August 12 from 16:34 to 18:34 UTC, with an average error rate of 16.16% that peaked at 28.6%; (2) August 12 from 19:00 to 22:56 UTC, with an average error rate of 16.55% that peaked at 24.18%; and (3) August 13 from 06:19 to 08:05 UTC, with an average error rate of 2.01% that peaked at 7.49%.<br />Requests from signed-in users were unaffected.<br /><br />We mitigated the incidents by applying traffic controls at our network edge that limited any requests matching the pattern identified previously, thereby preventing overload on our systems.<br /><br />Since these incidents occurred, we have tightened our monitoring systems to alert server-side errors that affect logged-out traffic. We are also working to further strengthen our edge protections and reduce the time to detect and mitigate similar incidents.

    Resolved

  7. Deepgram[Deepgram EU API] Flux-Multi STT Outage

    Resolved Between 07:13 and 09:00 UTC, flux-general-multi Speech-to-Text requests on api.eu.deepgram.com failed shortly after the WebSocket connection was established, returning an internal server error on the first audio and closing the connection. Affected clients saw abnormal closures and reconnect loops. A low rate of residual failures continued until 11:30 UTC. This has been fully investigated, mitigated and resolved, service has fully recovered.

    Resolved

  8. Deepgram[Deepgram API] Elevated Streaming STT Error Rates

    Between 23:18 and 23:45 UTC, a portion of streaming STT connection requests failed with 5XX errors and timeouts. While rolling out a new data center, we detected streaming errors and immediately removed it from rotation. Traffic to the new site had been intentionally limited to a small percentage while we verified the rollout, which limited the number of affected requests. This is now fully resolved.

    Resolved

  9. GitHubIntermittent failures creating agent tasks

    Between 13:57 UTC on August 20 and 00:37 UTC on August 21, 2026, some users of the Copilot Cloud Agent experienced delays of up to 60 to 90 minutes in seeing the status and results of their agent tasks. The agent tasks themselves continued to run and complete during this time; only the visibility of their status was delayed.<br /><br />The cause was a regional outage in a third-party cloud database service that Copilot uses to store agent task status. We failed over the affected database to a healthy region, added processing capacity to work through the backlog, and restored normal operation once the underlying service recovered. No task data was lost during the incident.<br /><br />To prevent repetition of similar incidents, we are removing the database configuration that made us vulnerable to this regional outage and improving our database failover procedures.

    Resolved

Older incidents