Ably: Push delivery errors for messages published in ap-southeast-2

What to do

Check whether you use Ably in ap-southeast-2. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 24m it lasted.
Anything that failed between 2025-12-11 18:36 UTC and 2025-12-11 18:59 UTC may need a replay.
Subscribe to Ably's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=ably works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

investigatingDec 11, 2025, 6:36 PM UTC
Increased level of push delivery errors for messages published in ap-southeast-2 only since 15:28 UTC, we're remediating
provider
identifiedDec 11, 2025, 6:36 PM UTC
The issue has been identified and a fix is being implemented.
provider
resolvedDec 11, 2025, 6:59 PM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Ably still down?

No, this incident was resolved 2025-12-11 18:59 UTC. For Ably's live state, see https://down.guide/ably.

How long did it last?

24m, from 2025-12-11 18:36 UTC to 2025-12-11 18:59 UTC, by the times Ably posted.

What was affected?

Ably named in ap-southeast-2.

What caused it?

Ably hasn't published a root cause. If it does, it shows here.

Where does this come from?

Ably's official status page, https://status.ably.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.