Elevated connection errors in us-east-1

What to do

• Check whether you use Ably US East (Northern Virginia) in us, us-east-1, us-east-2, 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 14h 21m it lasted.

  Anything that failed between 2026-10-25 21:24 UTC and 2026-10-26 11:45 UTC may need a replay.

• Subscribe to Ably's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=ably works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Ably 4

1. investigatingOct 25, 2026, 9:24 PM UTC

   We are seeing an elevated rate of connection errors in the us-east-1 region, seemingly as a result of a partial loadbalancer failure. We are disabling the region so traffic will be routed to other US sites.

   provider

2. monitoringOct 25, 2026, 9:33 PM UTC

   Traffic is no longer being routed to us-east-1, but instead to us-east-2 and us-west-1. We are continuing to investigate the root cause of the networking issue in us-east-1.

   provider

3. monitoringOct 25, 2026, 10:55 PM UTC

   us-east-1 remains disabled. All traffic is being routed to other regions so there is no ongoing impact on service.

   provider

4. resolvedOct 26, 2026, 11:45 AM UTC

   us-east-1 is reenabled and the service is operating normally. The root cause has been confirmed to be a defective Network Load Balancer that was causing a small fraction of connection attempts in the region to fail. We are awaiting a postmortem from AWS on the issue, and will publish our own postmortem here once we have that.

   provider

Corrections

None so far.

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