Ably experienced elevated connection errors in its US East (Northern Virginia) region over a 14.4-hour period, caused by a defective AWS Network Load Balancer that caused a fraction of connection attempts to fail. The affected region was disabled and traffic was rerouted to us-east-2 and us-west-1, eliminating ongoing service impact during the outage. The us-east-1 region was subsequently re-enabled once the issue was resolved, with a postmortem pending from AWS.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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.
us-east-1 remains disabled. All traffic is being routed to other regions so there is no ongoing impact on service.
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.
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with