- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 24of 100
What to do
Check whether you use Lambda Cloud in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 59m it lasted.
Anything that failed between 2026-07-27 08:46 UTC and 2026-07-27 11:45 UTC may need a replay.Subscribe to Lambda Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=lambda works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Lambda Cloud 3
- investigating
**Severity Level:** High We’re currently investigating a potential issue with our launches and termination from multiple regions. Users may experience their machines being stalled while booting up or terminating. 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.
provider
- monitoring
**Severity Level:** High We’re currently investigating a potential issue with our launches and termination from multiple regions. Users may experience their machines being stalled while booting up or terminating. Services have been restarted and the launches are enabled again. We will continue to monitor the situation. 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.
provider
- resolved
**Severity Level:** High The incident has been resolved. Launches and terminations 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-207388d239
Is Lambda Cloud still down?
No, this incident was resolved 2026-07-27 11:45 UTC. For Lambda Cloud's live state, see https://down.guide/lambda.
How long did it last?
2h 59m, from 2026-07-27 08:46 UTC to 2026-07-27 11:45 UTC, by the times Lambda Cloud posted.
What was affected?
Lambda Cloud named in us.
What caused it?
Lambda Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
Lambda Cloud's official status page, https://status.lambda.ai, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.