- Level
- confirmed
- Worst impact
- Degraded
- Components
- Europe (Frankfurt), US East (Northern Virginia)
- Regions
- eu, eu-central-1, us, us-east-1
- Down Index
- 36of 100
What to do
Check whether you use Ably Europe (Frankfurt), US East (Northern Virginia) in eu, eu-central-1, 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 2024-08-22 22:57 UTC and 2024-08-22 22:57 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 22:43 and 22:50 UTC, us-east-1 and eu-central-1 datacenters experienced network issues communicating between each other. Seemingly no other pairs of regions were affected, only those two. Messages published in one of those two regions during that time may have experienced increased latency before being received by the other. (You can find out your local ably datacenter by querying rest.ably.io/metadata)
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-3b2f41cac8
Is Ably still down?
No, this incident was resolved 2024-08-22 22:57 UTC. For Ably's live state, see https://down.guide/ably.
How long did it last?
0m, from 2024-08-22 22:57 UTC to 2024-08-22 22:57 UTC, by the times Ably posted.
What was affected?
Ably named Europe (Frankfurt), US East (Northern Virginia) in eu, eu-central-1, 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.