Lambda GPU Cloud incident

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

Resolved after 2 hours 6 minutes, affecting Frontend (Cloud API) and Infrastructure (Network) and 1 more, on September 23, 2026.

resolved Sep 23, 2026, 11:48 PM UTC

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 To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button.

Started
Sep 23, 2026, 09:41 PM UTC
Resolved
Sep 23, 2026, 11:48 PM UTC
Duration
2h 6m
Detected by Pingoru
Sep 23, 2026, 09:41 PM UTC

Affected components

Frontend (Cloud API)Infrastructure (Network)Infrastructure (Virtual Machines)

Update timeline

  1. investigating Sep 23, 2026, 09:41 PM UTC

    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 To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button.

  2. identified Sep 23, 2026, 10:22 PM UTC

    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 To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button.

  3. resolved Sep 23, 2026, 11:48 PM UTC

    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 To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button.

Your product runs on more than Lambda GPU Cloud

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →