Is Ably Down?
Reachable from all 8 checked regions
Average response time: 1193ms
Last checked · checks run every 6 hours
Official status page: https://status.ably.com
Ably uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 54 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
54-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
What Ably does
Ably provides realtime messaging infrastructure, handling pub/sub channels, presence, push notifications and message queues over persistent connections. Applications use it for live chat, collaborative editing, live scores and location tracking, where the value is in delivery within a second. It is embedded inside other products, so its failures appear as a customer's own app going quiet.
What an outage looks like
Clients disconnect and reconnect repeatedly, or connect and then receive nothing. Live features stop updating while the rest of the application keeps working, so the page looks healthy but frozen. Presence lists show users who have left or omit users who are there. Push notifications stop arriving on devices while in-app messages still flow, or the reverse.
What to do about it
status.ably.com reports 18 components across three groups, Pub/Sub, Push Notifications and Queues, each broken down by region including Northern Virginia, Ohio, Northern California, Ireland, Frankfurt, Singapore and Sydney. Ably Platform, the Control API and Integrations report separately from the message path, so provisioning can fail while existing channels are fine. Client libraries reconnect on their own, so avoid forcing reconnection loops that add load to a recovering region.
Is it down for everyone, or just you?
If this page says Ably is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Ably outage FAQ
My app loads but live updates have stopped. Is that an Ably outage?
Are messages published during an outage delivered later?
Is the problem my region or the whole platform?
Why did presence show the wrong users?
Should my client retry harder during an outage?
How we measure this
- We request Ably's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Ably publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when Ably goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring