Live  /  Lambda  /  Incident

Lambda: Experiencing issues with instance launches/terminations in us-west-1

Lambda · lambdalabs.comResolved2026-10-12 21:39 UTC
Public — what happened

Summary

Lambda reported a problem affecting the starting and shutting down of cloud instances in its us-west-1 region, beginning at 18:43 UTC on October 12, 2026. In its update the company labeled the issue high severity and said its teams were working to find the underlying cause, though no cause was shared. Customers unsure whether they were affected were invited to open a support ticket. The incident was marked resolved at 21:39 the same day.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 43, 2026, our weekly internet health report.

The full archive is on the Lambda status & history page.

Related: Lambda status & history. SquidGrid is not affiliated with Lambda.