Elevated API Errors

What to do

• Check whether your product depends on Ably. 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 27m it lasted.

  Anything that failed between 2026-10-01 15:36 UTC and 2026-10-01 16:03 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.

Updates from Ably 3

1. investigatingOct 1, 2026, 3:36 PM UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

   provider

2. resolvedOct 1, 2026, 4:03 PM UTC

   Between 15:30 UTC to 15:36 UTC there were elevated errors affecting token requests in all regions resulting in 503 error responses.

   provider

3. postmortemOct 1, 2026, 5:20 PM UTC

   On October 1, a distributed denial-of-service \(DDoS\) attack caused elevated token-request errors across all Ably Realtime regions for approximately six minutes and intermittent unavailability of [ably.com](http://ably.com). We restored token-request service by increasing capacity and added targeted traffic-blocking and rate-limiting rules to mitigate the attack. We are strengthening endpoint protection and reviewing our firewall controls to reduce the risk of recurrence.

   provider

Corrections

None so far.

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