Skip to main content
Ably logo

Is Ably Down?

No — Ably is up

Reachable from all 8 checked regions

Average response time: 1225ms

Last checked · checks run every 6 hours

Official status page: https://status.ably.com

Ably uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
1046ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 20 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

20-day clean streak
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: no data
Aug 16: no data
Aug 17: no data
Aug 18: no data
Aug 19: no data
Aug 20: no data
Aug 21: 100.00% uptime, 10 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Aug 24: 100.00% uptime, 32 checks
Aug 25: 100.00% uptime, 32 checks
Aug 26: 100.00% uptime, 32 checks
Aug 27: 100.00% uptime, 32 checks
Aug 28: 100.00% uptime, 32 checks
Aug 29: 100.00% uptime, 32 checks
Aug 30: 100.00% uptime, 32 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 100.00% uptime, 32 checks
Sep 2: 100.00% uptime, 32 checks
Sep 3: 100.00% uptime, 30 checks
Sep 4: 100.00% uptime, 28 checks
Sep 5: 100.00% uptime, 23 checks
Sep 6: 100.00% uptime, 24 checks
Sep 7: 100.00% uptime, 32 checks
Sep 8: 100.00% uptime, 30 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: no data
Aug 12 Today
No downtime Partial Downtime Not measurable No data

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

ams
880ms
DNS 21ms TCP 2ms TLS 9ms TTFB 798ms
arn
1001ms
DNS 51ms TCP 1ms TLS 8ms TTFB 992ms
bom
1708ms
DNS 7ms TCP 2ms TLS 7ms TTFB 1695ms
cdg
900ms
DNS 115ms TCP 1ms TLS 8ms TTFB 818ms
sin
2085ms
DNS 163ms TCP 1ms TLS 10ms TTFB 2075ms
sjc
635ms
DNS 14ms TCP 1ms TLS 7ms TTFB 626ms
syd
2118ms
DNS 220ms TCP 1ms TLS 10ms TTFB 2111ms
yyz
475ms
DNS 92ms TCP 1ms TLS 13ms TTFB 467ms

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 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Ably outage FAQ

My app loads but live updates have stopped. Is that an Ably outage?
It is the classic signature of one. Realtime delivery runs over a separate connection from the requests that load your page, so the application can render perfectly while nothing new arrives. Check the Pub/Sub component for your region. A frozen page with no errors is more consistent with a realtime failure than with an application fault.
Are messages published during an outage delivered later?
Depends on the feature. Ably keeps recent messages available for a limited window so clients that reconnect can recover what they missed, but a channel is not a durable queue. Anything that must survive an extended incident belongs in Ably Queues or in your own store, not in channel history alone.
Is the problem my region or the whole platform?
Ably reports each region separately within every group, so an incident in Ireland leaves Singapore unaffected. Client libraries can fall back to other endpoints, which means some users route around a regional problem while others do not. Read the row for the region your application is pinned to before concluding the platform is down.
Why did presence show the wrong users?
Presence state is derived from connection state, so during a period of repeated disconnections it lags reality. Users who dropped may still be listed until their connection times out, and users who reconnected may briefly appear twice. This corrects itself once connections stabilise and does not need intervention.
Should my client retry harder during an outage?
No. Ably's own libraries implement backoff and reconnection, and adding your own aggressive retry loop on top puts more load on a region that is already recovering. Leave the library to reconnect, and design the interface so a stale state is visible to the user rather than hidden behind a spinner that never resolves.

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 403 or 429 means 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 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required