Live / Incidents / Lambda
Lambda: US-SOUTH-3 Region Resources Not Visible on Dashboard, Impacting Launches and Terminations
Lambda · lambdalabs.comImpact: minorResolved2026-09-23 23:48 UTC
Public — what happened
Summary
**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
- Started — 2026-09-23 21:41 UTC
- Last update — 2026-09-23 23:48 UTC
- Resolved — 2026-09-23 23:48 UTC
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Lambda against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Lambda: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Lambda report →