- Level
- confirmed
- Worst impact
- Degraded
- Components
- X-Layer
- Regions
- us
What to do
Check whether you use Alchemy X-Layer in us. 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 7h 22m it lasted.
Anything that failed between 2026-08-27 16:18 UTC and 2026-08-27 23:40 UTC may need a replay.Subscribe to Alchemy's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=alchemy works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Alchemy 3
- investigating
WebSocket connections to X Layer Mainnet in our US East region are being established normally, but subscription events may be delayed or missing. HTTP requests are not affected.
provider
- monitoring
A fix has been implemented, and we are monitoring the results.
provider
- resolved
This incident has been resolved! WebSocket subscription delivery for X Layer Mainnet in our US East region has returned to normal. HTTP requests were not affected at any point during this incident
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-82bff0e07d
Is Alchemy still down?
No, this incident was resolved 2026-08-27 23:40 UTC. For Alchemy's live state, see https://down.guide/alchemy.
How long did it last?
7h 22m, from 2026-08-27 16:18 UTC to 2026-08-27 23:40 UTC, by the times Alchemy posted.
What was affected?
Alchemy named X-Layer in us.
What caused it?
Alchemy hasn't published a root cause. If it does, it shows here.
Where does this come from?
Alchemy's official status page, https://status.alchemy.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.