- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 26of 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 6h 53m it lasted.
Anything that failed between 2026-07-26 18:48 UTC and 2026-07-27 01:41 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
- identified
**Severity Level:** Medium DAL01 - COLO Internet Connectivity Disruption (Upstream Provider) We are currently investigating a loss of internet connectivity affecting colocation customers in our DAL01 (Dallas) facility. The disruption is due to a down Dedicated Internet Access (DIA) circuit with one of our upstream providers. Customers with IP addresses in the **38.147.81.0/24** range may be unable to send or receive traffic over the affected circuit. We have opened a ticket with the upstream provider and are actively working with them to restore service. We will provide another update as soon as additional information becomes available. 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
- identified
**Severity Level: Medium** DAL01 - COLO Internet Connectivity Disruption (Upstream Provider) We continue to work with our upstream provider to resolve the DIA circuit outage affecting DAL01. Our team is actively engaged and we're in regular contact as we work toward restoration. Customers with IP addresses in the **38.147.81.0/24** range remain impacted until service is restored. We do not have an ETA at this time but will share another update as soon as we have new information. Thank you for your patience while we work through this with our provider. ----------------------------------------------------------------------------- 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 The incident has been resolved. The network is now working as expected. Thank you for your patience. ----------------------------------------------------------------------------- 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-5ad8357a9c
Is Lambda Cloud still down?
No, this incident was resolved 2026-07-27 01:41 UTC. For Lambda Cloud's live state, see https://down.guide/lambda.
How long did it last?
6h 53m, from 2026-07-26 18:48 UTC to 2026-07-27 01:41 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.