Skip to main content
Lambda Cloud

lambda.ai Unreachable Due to DNS Issue

Partial outage Lasted 2h 32m · started · Lambda Cloud's page

Level
confirmed
Worst impact
Partial outage
Down Index
29of 100

What to do

  • Check whether your product depends on Lambda Cloud. 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 32m it lasted.

    Anything that failed between 2026-10-31 04:35 UTC and 2026-10-31 07:07 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.

Root cause

Our teams are actively working to identify the root cause and mitigate or resolve the issue.
Read the postmortem

Updates from Lambda Cloud 3

  1. investigating

    **Severity Level:** [High] We’re currently investigating a potential issue with the Cloud Dashboard. Users may experience timeouts when logging in or out of the portal. 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. • To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button.

    provider

  2. monitoring

    **Severity Level:** [High] Service is beginning to recover, though some users may continue to experience disruptions. We’re monitoring progress. 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

  3. resolved

    **Severity Level:** [High] The incident has been resolved. [lambda.ai](http://lambda.ai) is now working as expected. ----------------------------------------------------------------------------- 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. • 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-1348cbd513

Is Lambda Cloud still down?

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

How long did it last?

2h 32m, from 2026-10-31 04:35 UTC to 2026-10-31 07:07 UTC, by the times Lambda Cloud posted.

What caused it?

Lambda Cloud wrote: "Our teams are actively working to identify the root cause and mitigate or resolve the issue." The postmortem: https://status.lambda.ai/incidents/01M683W20M5EA4M9A6WKWXV1D1

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.