L
Outage recap · Lambda Labs

Lambda outage — September 23, 2026

On September 23, 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.

US-SOUTH-3 Region Resources Not Visible on Dashboard, Impacting Launches and Terminations

minor
Started
Sep 23, 5:41 PM EDT
Resolved
Sep 23, 7:48 PM EDT
Duration
2h 6m

Lambda Labs's updates (3)

  1. investigating · Sep 23, 5:41 PM EDT

    **Severity Level:** Medium We’re currently investigating a potential issue with our us-south-3 region. Users may experience instance launches and terminations in a stuck state. 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. identified · Sep 23, 6:22 PM EDT

    **Severity Level:** High We've identified that this issue is affecting the status of instances and filesystems in the us-south-3 region within the API and Console. Some users may see these resources as unhealthy when checking their dashboard and API. For clarity, the alert/unhealthy status is a display issue, not a reflection of actual instance health. The underlying infrastructure is healthy. If you already have connection details for an instance in us-south-3, you can continue to access it normally. We're continuing to work on a resolution and will provide another update as soon as we have one. 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](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.

  3. resolved · Sep 23, 7:48 PM EDT

    **Severity Level:** High The incident has been resolved. us-south-3 services 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](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 25 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 91 ms, against 78 ms over the 24 hours before. Lambda Labs posted the incident at Sep 23, 5:41 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.