Live  /  Lambda  /  Incident

Lambda: Service disruption in us-east-3

Lambda · lambdalabs.comResolved2026-11-07 17:26 UTC
Public — what happened

Summary

Lambda reported a service disruption affecting its On-Demand Cloud in the us-east-3 region, starting at 16:08 UTC on 2026-11-07. The company said customers might have trouble connecting to instances they already had running there, and that new instances could not be launched in the region. Lambda said its teams were working to find the cause and reduce the impact, and the incident is now marked resolved as of 17:26 UTC. The text provided does not say what caused the problem.

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 46, 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.