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

- Provider: [Lambda Cloud](https://down.guide/lambda)
- Level: confirmed
- Impact: Degraded
- lasted 2h 6m
- started 2026-09-23 21:41 UTC
- us, us-south-3
- id: DWN-d9c281fc48
- Official page: https://status.lambda.ai/incidents/01M383F6H4SVRBDYWEEJJ9M8W6

## Updates from Lambda Cloud
### 2026-09-23 21:41 UTC: investigating
\*\*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.

### 2026-09-23 22:22 UTC: identified
\*\*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.

### 2026-09-23 23:48 UTC: resolved
\*\*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.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).