- Level
- confirmed
- Worst impact
- Degraded
- Components
- US East (Ohio)
- Regions
- us, us-east-2
- Down Index
- 34of 100
What to do
Check whether you use Ably US East (Ohio) in us, us-east-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 14m it lasted.
Anything that failed between 2025-02-17 02:56 UTC and 2025-02-17 03:11 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
- investigating
We're investigating elevated error rates for some applications in us-east-2. We will update with more information when we have it
provider
- investigating
Error rates are back to normal. We are continuing to investigate what the issue was.
provider
- resolved
Error rates have been back to normal since 0255 (UTC).
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-ba30afab86
Is Ably still down?
No, this incident was resolved 2025-02-17 03:11 UTC. For Ably's live state, see https://down.guide/ably.
How long did it last?
14m, from 2025-02-17 02:56 UTC to 2025-02-17 03:11 UTC, by the times Ably posted.
What was affected?
Ably named US East (Ohio) in us, us-east-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.