Skip to main content
Lambda Cloud

Network Issues in us-midwest-2

Degraded Lasted 22d 10h · started · Lambda Cloud's page

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 22d 10h it lasted.

    Anything that failed between 2026-08-02 16:56 UTC and 2026-08-25 03:53 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

  1. investigating

    **Severity Level:** Medium We’re currently investigating a potential issue with our network in us-midwest-2. Users may experience degraded egress to the internet. 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

  2. monitoring

    **Severity Level:** Medium Our team has applied a fix to mitigate the network issue affecting us-midwest-2. We are currently monitoring the results to confirm full recovery. We will provide another update as soon as we have more information. 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

  3. resolved

    **Severity Level:** Medium The incident has been resolved. Networking in the us-midwest-2 region is confirmed restored after monitoring. ----------------------------------------------------------------------------- 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-e401556708

Is Lambda Cloud still down?

No, this incident was resolved 2026-08-25 03:53 UTC. For Lambda Cloud's live state, see https://down.guide/lambda.

How long did it last?

22d 10h, from 2026-08-02 16:56 UTC to 2026-08-25 03:53 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.