outages.live
Live
A

Ably

Ably is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

9

Days with an incident

9

Median duration

7 min

Longest incident

14 h 21 min

Components

15

Ably Pub/Sub

Asia-Pacific (Singapore) Operational
90 days ago1 day with an incidentToday
Asia Pacific (Sydney) Operational
90 days agoNo incidentsToday
Europe (Ireland) Operational
90 days agoNo incidentsToday
Europe (Frankfurt) Operational
90 days ago1 day with an incidentToday
US East (Northern Virginia) Operational
90 days ago2 days with an incidentToday
US East (Ohio) Operational
90 days ago1 day with an incidentToday
US West (Northern California) Operational
90 days ago1 day with an incidentToday

Ably Push Notifications

Push Notifications - Europe (Ireland) Operational
90 days agoNo incidentsToday
Push Notifications - US East (North Virginia) Operational
90 days agoNo incidentsToday

Ably Queues

Ably Queues - Europe (Ireland) Operational
90 days agoNo incidentsToday
Ably Queues - US East (Northern Virginia) Operational
90 days agoNo incidentsToday
Ably Platform Operational
90 days ago1 day with an incidentToday
Ably Control API Operational
90 days agoNo incidentsToday
Ably Website Operational
90 days ago1 day with an incidentToday
Integrations Operational
90 days ago1 day with an incidentToday

Past incidents

Provider status pageTimes in UTC

Oct 30, 2026

Duration1 min16:48 to 16:48Transient load-balancer issue in us-west-1Notice

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 25, 2026

Duration14 h 21 min21:24 to 11:45Elevated connection errors in us-east-1Degraded

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 20, 2026

Duration1 min13:00 to 13:00issue with rewind=1 and persist-last in some situationsNotice

Between about 14:00 UTC on the 20th and 17:00 on the 21st, on channels with the persist last message (https://ably.com/docs/channels#rules) channel rule enabled, attachments with `rewind=1` in situations where the most recent message was published over two minutes ago but still somewhat recently (and where the channel has been continuously active in a given region since the message was published) may not have had that rewound message correctly delivered to the attaching client. We apologise to anyone whose application was affected by this.

Oct 16, 2026

Duration1 min13:00 to 13:00MongoDB ingress rule issuesNotice

Between 10:35 and 12:20 UTC today, MongoDB ingress rules may have experienced errors publishing changestream events. If you were affected by this, please contact support@ably.com.

Oct 1, 2026

Duration27 min15:36 to 16:03Elevated API ErrorsPartial outage

On October 1, a distributed denial-of-service \(DDoS\) attack caused elevated token-request errors across all Ably Realtime regions for approximately six minutes and intermittent unavailability of [ably.com](http://ably.com). We restored token-request service by increasing capacity and added targeted traffic-blocking and rate-limiting rules to mitigate the attack. We are strengthening endpoint protection and reviewing our firewall controls to reduce the risk of recurrence.

Sep 7, 2026

Duration7 min11:25 to 11:32Ably documentation pages - ably.com/docsPartial outage

This incident has been resolved.

Aug 28, 2026

Duration1 h 24 min12:08 to 13:33Elevated API Errors - LiveObjectsDegraded

This incident has been resolved.

Aug 20, 2026

Duration55 min19:29 to 20:24Elevated Errors in ap-southeast-1Degraded

This incident has been resolved.

Duration3 min19:07 to 19:10Elevated Error Rate in ap-southeast-1Partial outage

This incident has been resolved.

Follow Ably

Your coding agent knows when Ably is down, and tells you when a failure is theirs, not yours. You can also get Ably incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "ably" and tell me if Ably has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=ably
Slack
/feed subscribe https://outages.cc/feed.xml?providers=ably

Go from tracking outages to fixing production issues with Polylane.

Try Polylane