- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 27of 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 21d 5h it lasted.
Anything that failed between 2026-08-03 22:30 UTC and 2026-08-25 04:23 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 5
- investigating
Severity Level: Medium We’re currently investigating a potential issue with our B200 cluster performance in us-midwest-2 impacting Managed Kubernetes, and 1-Click Cluster customers. 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:** Medium We identified an issue within the InfiniBand fabric and implemented changes to address it. Performance has returned to expected levels based on telemetry and internal testing. We are continuing to monitor for stability. 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:** Medium We’re currently investigating a potential issue with our B200 cluster performance in us-midwest-2 impacting Managed Kubernetes, and 1-Click Cluster customers. 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.
provider
- monitoring
**Severity Level:** Medium Performance has returned to acceptable levels based on current telemetry and internal testing. We are continuing to monitor for stability and will provide further updates as they become available. ----------------------------------------------------------------------------- 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:** Medium Performance has returned to expected levels based on current telemetry and internal testing after monitoring health over the weekend. ----------------------------------------------------------------------------- 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-f859cccac5
Is Lambda Cloud still down?
No, this incident was resolved 2026-08-25 04:23 UTC. For Lambda Cloud's live state, see https://down.guide/lambda.
How long did it last?
21d 5h, from 2026-08-03 22:30 UTC to 2026-08-25 04:23 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.