- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-east-1
- Down Index
- 28of 100
What to do
Check whether you use Ably in us, us-east-1. 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 2023-09-28 18:50 UTC and 2023-09-28 18:50 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
We're currently experiencing network timeouts for hosted reactor queues in the us-east-1 region, we are investigating. 28th Sep 09:01 PM Our team are continuing to investigate network timeouts for hosted reactor queues in the us-east-1 region. 28th Sep 10:03 PM We have deployed a change to work around ongoing networking issues affecting the queues service in us-east-1. As far as we can tell, this has been successful and service performance has returned to normal. We will continue to monitor the situation. 28th Sep 10:10 PM The service is performing normally.
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-a438044126
Is Ably still down?
No, this incident was resolved 2023-09-28 18:50 UTC. For Ably's live state, see https://down.guide/ably.
How long did it last?
0m, from 2023-09-28 18:50 UTC to 2023-09-28 18:50 UTC, by the times Ably posted.
What was affected?
Ably named in us, us-east-1.
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.