Minor incident
Ably: Elevated connection errors in us-east-1
Oct 25, 2026, 21:24 UTC
started
11:45 UTC
resolved October 26, 2026
14 h 21 min
duration
Affected: US East (Northern Virginia)
Current status of Ably: Operational — live Ably status
Timeline
- Oct 25, 2026, 21:24 UTCinvestigatingWe 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.
- Oct 25, 2026, 21:33 UTCmonitoringTraffic 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.
- Oct 25, 2026, 22:55 UTCmonitoringus-east-1 remains disabled. All traffic is being routed to other regions so there is no ongoing impact on service.
- Oct 26, 2026, 11:45 UTCresolvedus-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.
Updates as published by Ably (original).
Other services with incidents at the same time
- Convivastatus 21:09 UTC · Data Delay for SEI App customers
- Check Point Services 20:42 UTC · Service Down due to incident
More Ably incidents
- October 20, 2026 issue with rewind=1 and persist-last in some situations
- October 16, 2026 MongoDB ingress rule issues
- October 1, 2026 Elevated API Errors
- September 7, 2026 Ably documentation pages - ably.com/docs
- August 20, 2026 Elevated Error Rate in ap-southeast-1