L
Outage recap · Lambda Labs

Lambda outage — October 12, 2026

On October 12, 2026, Lambda had a reported incident on Lambda Labs's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Experiencing issues with instance launches/terminations in us-west-1

none
Started
Oct 12, 2:43 PM EDT
Resolved
Oct 12, 5:39 PM EDT
Duration
2h 56m

Lambda Labs's updates (2)

  1. investigating · Oct 12, 2:43 PM EDT

    **Severity Level:** [High] We’re currently investigating an issue with instance launches and terminations in our us-west-1 region. Our teams are actively working to identify the root cause and mitigate or resolve the issue. Thank you for your patience and understanding during this time. ----------------------------------------------------------------------------- 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](https://support.lambdalabs.com/hc/en-us/requests/new "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.

  2. resolved · Oct 12, 5:39 PM EDT

    **Severity Level:** High Instance launches and terminations in us-west-1 are now operational. Thank you for your patience and understanding during this time. ----------------------------------------------------------------------------- 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](https://support.lambdalabs.com/hc/en-us/requests/new "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.

What our checks recorded

We checked Lambda 35 times from Lambda Labs's start time to its resolution, once every five minutes. Every one of them reached Lambda's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 72 ms, against 69 ms over the 24 hours before. Lambda Labs posted the incident at Oct 12, 2:43 PM EDT.

Updates are Lambda Labs's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with Lambda Labs. This recap summarizes incidents published on Lambda Labs's official status page.