Skip to main content
Lambda Cloud

Slow Instance Launches in Certain Regions

Degraded Lasted 14m · started · Lambda Cloud's page

Level
confirmed
Worst impact
Degraded
Regions
apac, eu, me-west-1, us, us-east-1, us-west-1, us-west-2

What to do

  • Check whether you use Lambda Cloud in apac, eu, me-west-1, 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 14m it lasted.

    Anything that failed between 2026-06-04 19:31 UTC and 2026-06-04 19:45 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 a potential issue with our instance launches. Users may experience slower than normal instance launches in the following regions: • us-east-1 • us-midwest-1 • us-west-1 • us-west-2 • me-west-1 • europe-cental-1 • ap-southeaast-2 • asia-northeast-2 • asia-south-1 • asia-northeast-1 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

    Our team has resolved the issue impacting slow instance launches. Thank you for your patience and understanding during this time. ----------------------------------------------------------------------------- In the event you’re unsure as to whether your service was 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-b928727335

Is Lambda Cloud still down?

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

How long did it last?

14m, from 2026-06-04 19:31 UTC to 2026-06-04 19:45 UTC, by the times Lambda Cloud posted.

What was affected?

Lambda Cloud named in apac, eu, me-west-1, 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.