- Level
- confirmed
- Worst impact
- Degraded
- Components
- US West (Northern California)
- Regions
- us, us-west-1
- Down Index
- 28of 100
What to do
Check whether you use Ably US West (Northern California) in us, us-west-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 2026-10-30 16:48 UTC and 2026-10-30 16:48 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 16:27-16:35 UTC, connection attempts to us-west-1 had an ~18% chance of being refused with an error due to a network load balancer issue. An Ably SDK will have been automatically retried to a fallback region, so an end user will have experienced no impact other than a slight increase in connection establishment latency.
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-231722983f
Is Ably still down?
No, this incident was resolved 2026-10-30 16:48 UTC. For Ably's live state, see https://down.guide/ably.
How long did it last?
0m, from 2026-10-30 16:48 UTC to 2026-10-30 16:48 UTC, by the times Ably posted.
What was affected?
Ably named US West (Northern California) in us, us-west-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.