Skip to main content
Lambda Cloud

US-SOUTH-2 Booting Failures of Newly Launched Instance

Degraded Lasted 4d 6h · started · Lambda Cloud's page

Level
confirmed
Worst impact
Degraded
Regions
us, us-south-2
Down Index
31of 100

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.
  • Confirm your retries, queues and scheduled jobs caught up after the 4d 6h it lasted.

    Anything that failed between 2026-06-20 06:51 UTC and 2026-06-24 13:04 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

  1. investigating

    **Severity Level:** [Medium] We're currently investigating a potential issue in the US-SOUTH-2 region. Users may experience slow booting of newly launched instance. 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. investigating

    **Severity Level:** [High] We’re currently investigating an issue with our [SERVICE]. Users are experiencing [specific impact]. Our teams are actively working to identify the root cause and mitigate or resolve the issue. New instance launches in [SERVICE] have been temporarily disabled. 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. investigating

    **Severity Level:** [Low/Medium/High/Critical] We’re currently investigating a potential issue in US-SOUTH-2. Users are experience new instance launch failing to boot. Our teams are actively working to identify the root cause and mitigate or resolve the issue. Currently new instance launches in US-SOUTH-2 have been temporarily disabled until the issue has been remediated. 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

  4. monitoring

    **Severity Level:** [High] Our engineers have pushed a fix to remediate the problem of new instance launches failing to boot in US-SOUTH-2. New instance launches have now been reactivated for this region. Our engineers will continue to monitor this issue closely. 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

  5. resolved

    **Severity Level:** High 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

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-edc1df6397

Is Lambda Cloud still down?

No, this incident was resolved 2026-06-24 13:04 UTC. For Lambda Cloud's live state, see https://down.guide/lambda.

How long did it last?

4d 6h, from 2026-06-20 06:51 UTC to 2026-06-24 13:04 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.