Ably Outage History

12 incidents recorded over the last 365 days, 10 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Ably status99.95% uptime history

Every Recorded Ably Incident

Ably incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 20, 2026Elevated Errors in ap-southeast-1This incident has been resolved.55 minResolved
Aug 20, 2026Elevated Error Rate in ap-southeast-1This incident has been resolved.2 minResolved
Jun 23, 2026Scheduled maintenance on Ably QueuesThe scheduled maintenance to Ably Queues has been completed.6h 0mScheduled
Apr 28, 2026Scheduled maintenance on Ably QueuesThe scheduled maintenance has been completed.2h 0mScheduled
Feb 17, 2026Elevated realtime publish error rate in ap-southeast-1This incident has been resolved.12 minResolved
Feb 14, 2026Elevated Attach Error Rate in eu-west-1This incident has now been resolved.8 minResolved
Jan 21, 2026SMS based 2FA is currently unavailableThis incident has been resolved.1h 41mResolved
Dec 11, 2025Push delivery errors for messages published in ap-southeast-2This incident has been resolved.23 minResolved
Dec 5, 2025Ably website, customer dashboard & Control API issuesThis incident has been resolved.19 minResolved
Nov 25, 2025High pusher, pubnub and mqtt adaptor error rateThe incident is now resolved. The elevated protocol adaptor error rate affected EU regions for 36 minutes from 11.25am-12.01pm UTC, for 15 minutes in US regions from 11.50am-12.05pm UTC, and for 14 minutes in AP regions…32 minResolved
Oct 29, 2025Webhook delivery failures# Summary of incident affecting the Ably production service on 28-29 October - investigation and conclusions ## Overview There was an incident affecting Ably's service between 28 and 29 October 2025, which affected…44 minResolved
Oct 9, 2025Ably website, customer dashboard & Control API issuesCustomers may be experiencing connectivity issues affecting our website (ably.com), customer dashboards, the Control API (control.ably.net), the Ably blog and documentation. Our realtime services are not affected by…0 minResolved

How to Read This Ably Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Ably acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Ably outage in this window ran 6h, against a mean recovery of 1h 5m. If you depend on Ably in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.