- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 20of 100
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 0m it lasted.
Anything that failed between 2024-07-09 10:36 UTC and 2023-03-21 16:00 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 1
- resolved
Between 15:40 and 17:40 UTC, customers using the REST API directly may have observed 502 error responses. Our SDKs automatically retry 5xx responses to fallback endpoints, so customers using SDKs should not have noticed anything except increased latency due to the retries. The proximate cause was a faulty router deploy, we are actively investigating the root cause, and will be improving our alerting system, which should have caught this sooner. We apologise for any disruption.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-4d7e14fa0f
Is Ably still down?
No, this incident was resolved 2023-03-21 16:00 UTC. For Ably's live state, see https://down.guide/ably.
How long did it last?
0m, from 2024-07-09 10:36 UTC to 2023-03-21 16:00 UTC, by the times Ably posted.
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.