Vendor Status Watch

← all vendors

Ably status history

Current state: operational — “All Systems Operational” per https://status.ably.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

4incidents, last 30 days
4incidents, last 90 days
13incidents on record
Incidents per week, last 12 weeks:

How long do Ably incidents last?

23 minmedian incident duration13 measured
84 min90th percentile1 in 10 ran longer
8 minmedian, major/critical only7 incidents

From 13 incidents with a vendor-posted start and resolve time. Longest on record: SMS based 2FA is currently unavailable — 101 min (2026-01-21 18:11 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (13)

StartedIncidentStatusImpactDuration
2026-09-07 11:25 UTCAbly documentation pages - ably.com/docsresolvedmajor7 min
2026-08-28 12:08 UTCElevated API Errors - LiveObjectsresolvedminor1 h 24 min
2026-08-20 19:29 UTCElevated Errors in ap-southeast-1resolvedminor55 min
2026-08-20 19:07 UTCElevated Error Rate in ap-southeast-1resolvedmajor2 min
2026-02-17 10:19 UTCElevated realtime publish error rate in ap-southeast-1resolvedminor12 min
2026-02-14 05:57 UTCElevated Attach Error Rate in eu-west-1resolvedmajor8 min
2026-01-21 18:11 UTCSMS based 2FA is currently unavailableresolvedminor1 h 41 min
2025-12-11 18:36 UTCPush delivery errors for messages published in ap-southeast-2resolvednone23 min
2025-12-05 08:59 UTCAbly website, customer dashboard & Control API issuesresolvedcritical19 min
2025-11-25 11:38 UTCHigh pusher, pubnub and mqtt adaptor error rateresolvedminor32 min
2025-10-29 08:57 UTCWebhook delivery failurespostmortemmajor44 min
2025-10-09 14:10 UTCAbly website, customer dashboard & Control API issuesresolvedmajor0 min
2025-08-13 12:47 UTCElevated Realtime errors in EU regionsresolvedmajor37 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Ably with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "ably"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}