Live / Lambda / Incident
Lambda: US-SOUTH-3 Region Resources Not Visible on Dashboard, Impacting Launches and Terminations
Lambda · lambdalabs.comMinor incidentResolved2026-09-23 23:48 UTC
Public — what happened
Summary
Lambda reported a problem in its US-SOUTH-3 region in which resources did not appear on the dashboard, which interfered with customers launching and terminating instances there. The issue began on 2026-09-23 at 21:41 UTC, and Lambda did not share a cause in its update. The company marked it resolved at 23:48 the same day, saying services in the region were back to normal, and asked anyone still unsure whether they were affected to contact support.
Timeline
- Started — 2026-09-23 21:41 UTC
- Resolved — 2026-09-23 23:48 UTC · 2h 06m after it started
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 →
More from Lambda
Covered in The Squid’s Ink, Week 40, 2026, our weekly internet health report.