Skip to main content
Lambda Cloud

US-SOUTH-2 Scheduled Maintenance

Maintenance Lasted 2h 24m · started · Lambda Cloud's page

Level
confirmed
Worst impact
Maintenance
Regions
us, us-south-2

What to do

  • Check whether you use Lambda Cloud in us, us-south-2. 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.
  • Check that everything you run on Lambda Cloud came back after the window closed 2026-10-05 20:34 UTC.

  • 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 2

  1. monitoring

    Severity Level: Low We have identified that a small portion of servers in our datacenter in us-south-2​ requires an update to their configuration in order to address some power redundancy issues. Our engineers in this datacenter are addressing this issue currently. Due to how the maintenance is being conducted, we do not anticipate any customer impact during this timeframe. We are currently monitoring us-south-2​ while this maintenance is underway. If we identify an issue affecting customer instances, we will provide an update here. 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. resolved

    The us-south-2 power maintenance is now complete. ----------------------------------------------------------------------------- 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-397ed50711

Is this Lambda Cloud maintenance still going on?

No, it ended 2026-10-05 20:34 UTC.

How long did it last?

2h 24m, from 2026-10-05 18:10 UTC to 2026-10-05 20:34 UTC, by the times Lambda Cloud posted.

What was affected?

Lambda Cloud named in us, us-south-2.

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.