- Level
- confirmed
- Worst impact
- Major outage
- Regions
- ap-southeast-2, apac, eu, me-west-1, us, us-east-1, us-west-1, us-west-2
- Down Index
- 65of 100
What to do
Check whether you use Lambda Cloud in ap-southeast-2, apac, eu, me-west-1. 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 2d 19h it lasted.
Anything that failed between 2026-03-02 22:42 UTC and 2026-03-05 18:10 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 9
- investigating
**Severity Level:** Medium We’re currently investigating a potential issue with our us-east-1 instance launches. Users will currently experience instance launch failures in this region. Our engineers are actively working to identify the root cause of the issue. Other regions are not currently impacted. 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. • To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button. Thank you for your patience and understanding during this time.
provider
- monitoring
**Severity Level:** [Medium] A fix has been implemented and we’re monitoring the results. To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button. Thank you for your patience and understanding during this time.
provider
- investigating
**Severity Level:** High We’re currently investigating instance failure launches with our On-Demand Cloud. Currently, Instance launches are disabled. Our engineers are actively working to identify the root cause of the issue. 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. • To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button. Thank you for your patience and understanding during this time.
provider
- investigating
**Severity Level:** High We’re currently investigating instance failure launches with our On-Demand Cloud. Our engineers are actively working to identify the root cause of the issue. Instance Launches have been disabled for the following regions: • us-east-1 • us-midwest-1 • us-west-1 • us-west-2 • me-west-1 • europe-central-1 • ap-southeast-2 • asia-northeast-2 • asia-south-1 • asia-northeast-1 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. Thank you for your patience and understanding during this time.
provider
- investigating
**Severity Level:** [High] **UPDATE:** • The below is still accurate. We're continuing the investigation with our service provider. Please bear with us as we work to re-enable instance launches in the regions listed below. We’re currently investigating instance failure launches with our On-Demand Cloud. Our engineers are actively working to identify the root cause of the issue. Instance Launches have been disabled for the following regions: • us-east-1 • us-midwest-1 • us-west-1 • us-west-2 • me-west-1 • europe-central-1 • ap-southeast-2 • asia-northeast-2 • asia-south-1 • asia-northeast-1 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. Thank you for your patience and understanding during this time.
provider
- investigating
**Severity Level:** [High] We’re investigating instance launch failures for On-Demand Cloud with our service provider. Please bear with us as we work to re-enable instance launches in the following regions: • us-east-1 • us-midwest-1 • us-west-1 • us-west-2 • me-west-1 • europe-central-1 • ap-southeast-2 • asia-northeast-2 • asia-south-1 • asia-northeast-1 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. Thank you for your patience and understanding during this time.
provider
- identified
Severity Level: [High] We're currently investigating an issue with On-Demand Cloud instance launches across multiple regions. A disruption to the creation of new Firewall Rulesets is causing instance launches to fail or enter an Alert status for customers without existing Firewall Rulesets in the affected regions. We have re-enabled launches, however customers without existing Firewall Rulesets may still experience failures in the following regions: • us-east-1 • us-midwest-1 • us-west-1 • us-west-2 • me-west-1 • europe-central-1 • ap-southeast-2 • asia-northeast-2 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. Thank you for your patience and understanding during this time.
provider
- identified
Severity Level: [High] We're currently investigating an issue with On-Demand Cloud instance launches across multiple regions. An issue with Firewall Rulesets is causing instance launches to fail or enter an Alert status for customers when creating new Firewall Rulesets in the affected regions. We have re-enabled launches, however customers without existing Firewall Rulesets may still experience failures in the following regions: • us-east-1 • us-midwest-1 • us-west-1 • us-west-2 • me-west-1 • europe-central-1 • ap-southeast-2 • asia-northeast-2 Please note that you will not be charged for an instance until it has reached a healthy boot state. 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. Thank you for your patience and understanding during this time.
provider
- resolved
**Severity Level:** [High] Our Engineering team was able to identify and remediate the root cause of the issue. Users that were experiencing instance launch failures should no longer be impacted. In the event you’re unsure as to whether your service is still 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. Thank you for your patience and understanding during this time.
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-5259199011
Is Lambda Cloud still down?
No, this incident was resolved 2026-03-05 18:10 UTC. For Lambda Cloud's live state, see https://down.guide/lambda.
How long did it last?
2d 19h, from 2026-03-02 22:42 UTC to 2026-03-05 18:10 UTC, by the times Lambda Cloud posted.
What was affected?
Lambda Cloud named in ap-southeast-2, apac, eu, me-west-1.
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.