We started checking Ably on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Ably reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Ably's own status page declared. Below it, any public chatter we saw about Ably and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Ably's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Ably in the last 24 hours, which is not evidence that nothing is wrong.
Ably's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Ably's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Ably next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
443
US-West
100.00%
351
Europe
100.00%
319
Asia-Pacific
100.00%
195
Their declared record
Ably's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
eu-west-1 NLB issuesMinor incident
Nov 3, 2026, 10:40 PM UTC to Nov 3, 2026, 10:57 PM UTC (18 min)resolved
their latest update (Nov 3, 2026, 10:57 PM UTC): Traffic is once again flowing to the region as normal, we are continuing to monitor.
Transient load-balancer issue in us-west-1All systems operational
Oct 30, 2026, 4:48 PM UTC to Oct 30, 2026, 4:48 PM UTC (0 min)resolved
their latest update (Oct 30, 2026, 4:48 PM UTC): 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 sli…
Elevated connection errors in us-east-1Minor incident
Oct 25, 2026, 9:24 PM UTC to Oct 26, 2026, 11:45 AM UTC (14h 21m)resolved
their latest update (Oct 26, 2026, 11:45 AM UTC): 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 pub…
issue with rewind=1 and persist-last in some situationsAll systems operational
Oct 20, 2026, 1:00 PM UTC to Oct 20, 2026, 1:00 PM UTC (0 min)resolved
their latest update (Oct 20, 2026, 1:00 PM UTC): 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 s…
MongoDB ingress rule issuesAll systems operational
Oct 16, 2026, 1:00 PM UTC to Oct 16, 2026, 1:00 PM UTC (0 min)resolved
their latest update (Oct 16, 2026, 1:00 PM UTC): 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.
Elevated API ErrorsPartial outage
Oct 1, 2026, 3:36 PM UTC to Oct 1, 2026, 4:03 PM UTC (27 min)postmortem published
their latest update (Oct 1, 2026, 5:20 PM UTC): 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 capaci…
Sep 7, 2026, 11:25 AM UTC to Sep 7, 2026, 11:32 AM UTC (7 min)resolved
their latest update (Sep 7, 2026, 11:32 AM UTC): This incident has been resolved.
Elevated API Errors - LiveObjectsMinor incident
Aug 28, 2026, 12:08 PM UTC to Aug 28, 2026, 1:33 PM UTC (1h 24m)resolved
their latest update (Aug 28, 2026, 1:33 PM UTC): This incident has been resolved.
Elevated Errors in ap-southeast-1Minor incident
Aug 20, 2026, 7:29 PM UTC to Aug 20, 2026, 8:24 PM UTC (55 min)resolved
their latest update (Aug 20, 2026, 8:24 PM UTC): This incident has been resolved.
Elevated Error Rate in ap-southeast-1Partial outage
Aug 20, 2026, 7:07 PM UTC to Aug 20, 2026, 7:10 PM UTC (3 min)resolved
their latest update (Aug 20, 2026, 7:10 PM UTC): This incident has been resolved.
Showing the 10 most recent of 51 incidents Ably has declared in the history we hold.
These entries are Ably's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Ably's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.