All Systems Operational

Ably Platform Operational
Ably Pub/Sub Operational
Asia-Pacific (Singapore) Operational
Asia Pacific (Sydney) Operational
Europe (Ireland) Operational
Europe (Frankfurt) Operational
US East (Northern Virginia) Operational
US East (Ohio) Operational
US West (Northern California) Operational
Ably Push Notifications Operational
Push Notifications - Europe (Ireland) Operational
Push Notifications - US East (North Virginia) Operational
Ably Queues Operational
Ably Queues - Europe (Ireland) Operational
Ably Queues - US East (Northern Virginia) Operational
Ably Control API Operational
Ably Website Operational
Integrations Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

Nov 4, 2026

No incidents reported today.

Nov 3, 2026

Resolved - Traffic is once again flowing to the region as normal, we are continuing to monitor.
Nov 3, 22:57 UTC
Monitoring - From 21:55 UTC we have been seeing a 2% rate of connection errors in the eu-west-1 region, which looks similar to the loadbalancer issue last week. We are routing new traffic away from that region towards other regions (which will mostly land at eu-central-1, the next nearest region).
Nov 3, 22:40 UTC

Nov 2, 2026

No incidents reported.

Nov 1, 2026

No incidents reported.

Oct 31, 2026

No incidents reported.

Oct 30, 2026

Resolved - Between 16:27-16:35 UTC, connection attempts to us-west-1 had an ~18% chance of being refused with an error due to a network load balancer issue. An Ably SDK will have been automatically retried to a fallback region, so an end user will have experienced no impact other than a slight increase in connection establishment latency.
Oct 30, 16:48 UTC

Oct 29, 2026

No incidents reported.

Oct 28, 2026

No incidents reported.

Oct 27, 2026

No incidents reported.

Oct 26, 2026

Resolved - 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.

Oct 26, 11:45 UTC
Update - us-east-1 remains disabled. All traffic is being routed to other regions so there is no ongoing impact on service.
Oct 25, 22:55 UTC
Monitoring - 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.

Oct 25, 21:33 UTC
Investigating - 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.
Oct 25, 21:24 UTC

Oct 25, 2026

Oct 24, 2026

No incidents reported.

Oct 23, 2026

No incidents reported.

Oct 22, 2026

No incidents reported.

Oct 21, 2026

No incidents reported.