Skip to main content
Lambda Cloud

Experiencing issues with instance launches/terminations in us-west-1

Degraded Lasted 2h 56m · started · Lambda Cloud's page

Level
confirmed
Worst impact
Degraded
Regions
us, us-west-1
Down Index
28of 100

What to do

  • Check whether you use Lambda Cloud in us, us-west-1. 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 2h 56m it lasted.

    Anything that failed between 2026-10-12 18:43 UTC and 2026-10-12 21:39 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 2

  1. investigating

    **Severity Level:** [High] We’re currently investigating an issue with instance launches and terminations in our us-west-1 region. 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. resolved

    **Severity Level:** High Instance launches and terminations in us-west-1 are now operational. 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

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-8391fe111c

Is Lambda Cloud still down?

No, this incident was resolved 2026-10-12 21:39 UTC. For Lambda Cloud's live state, see https://down.guide/lambda.

How long did it last?

2h 56m, from 2026-10-12 18:43 UTC to 2026-10-12 21:39 UTC, by the times Lambda Cloud posted.

What was affected?

Lambda Cloud named in us, us-west-1.

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.