Degraded instance launches and terminations in us-east-3

What to do

• Check whether you use Lambda Cloud in us, us-east-3. 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 0m it lasted.

  Anything that failed between 2026-10-28 23:10 UTC and 2026-10-28 16:40 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 1

1. resolvedOct 28, 2026, 4:40 PM UTC

   **Severity Level:** [Low] Our public cloud experienced a network configuration issue in Lambda Cloud. Region:US-EAST-3 Impact: October 28, 2026 Start: 15:40 UTC End: 16:50 UTC Duration: 1 hour 10 minutes During that time, users may have seen fewer instances available to launch in us-east-3, and instance termination requests that were accepted but not completed. Running instances were not affected, and we have successfully repaired the issue. We're continuing to monitor. If you were affected or have questions, please contact Lambda Support. ----------------------------------------------------------------------------- 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

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.