Who is down right now

Lambda · AISep 23, 2026, 21:41 UTC 2 weeks ago

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

MinorNot disclosedUpdated 2h ago
Sep 23, 21:41 UTCSep 23, 23:48 UTC
Duration
2h 6m
Impact
Minor
Root cause
Not disclosed
Lambda, 90 days
9 incidents
Affected
Not listed by the vendor.
Status page

Final update

**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.

Timeline

  1. Resolved · Sep 23, 23:48 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](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, 22:22 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](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. Investigating · Sep 23, 21:41 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](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.

More from Lambda

Full history
IncidentDuration
Issue with Cloud Services API KeysSep 10, 07:09 UTC8h 54m
Instances Unreachable in us-south-2 regionAug 15, 18:28 UTC2d 2h
Degraded Performance in us-midwest-2Aug 3, 22:30 UTC21d 5h
Network Issues in us-midwest-2Aug 2, 16:56 UTC22d 10h
Investigating network connectivity issues in us-east-2Jul 30, 19:46 UTC3h 3m
Network issues in us-east-2Jul 29, 19:54 UTC22h 25m