Incidents

Quoted from each provider's status page.

OngoingAll clear
Where, Apr 7, 2025 – Jan 16, 2026Places named on the status page: cloud regions, cities, countries, data centres. An incident naming only a broad area (Europe, APAC) is counted under the map, not pinned.
7 places · 3 not pinned
Sydney (ap-southeast-2): 2 incidents · AblyCalifornia: 1 incident · AblyFrankfurt: 1 incident · AblyIreland: 1 incident · AblyOhio: 1 incident · AblySingapore: 1 incident · AblyVirginia: 1 incident · Ably
Last 90 daysOne square per UTC day, coloured by the worst incident that day. Ongoing incidents count today.
0 Sev 1 days · 82 clean
AugSepOctMonWedFri
CleanSev 3–4Sev 2Sev 1

Thu, Dec 111 incident

18:36SEV 2Ably · Push delivery errors for messages published in ap-southeast-2 · source24m

Fri, Dec 51 incident

08:59SEV 3Ably · Ably website, customer dashboard & Control API issuesAbly Website · source19m

Tue, Nov 251 incident

11:38SEV 2Ably · High pusher, pubnub and mqtt adaptor error rateAbly Pub/Sub Channels - Asia-Pacific (Singapore), Ably Pub/Sub Channels - Asia Pacific (Sydney), Ably Pub/Sub Channels - Europe (Ireland) +4 · source33m

Wed, Oct 291 incident

08:57SEV 2Ably · Webhook delivery failuresIntegrations, Integration Rules · postmortem · source45m

Thu, Oct 91 incident

14:10SEV 3Ably · Ably website, customer dashboard & Control API issuesAbly Website · source0m