- Level
- confirmed
- Worst impact
- Degraded
- Components
- Sonic
What to do
Check whether you use Alchemy Sonic. 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 2d 2h it lasted.
Anything that failed between 2026-03-25 10:16 UTC and 2026-03-27 12:42 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 6
- investigating
We are currently investigating this issue.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
An accidental hard fork occurred on the Sonic mainnet due to a consensus-breaking change introduced in Sonic client v2.1.6, related to an upgraded Ethereum library containing CVE security patches. Nodes running older client versions fell out of consensus at block 66,026,364, while the network itself continued producing blocks normally. Our Sonic mainnet RPC nodes were affected. We have upgraded all nodes to v2.1.6 and initiated a full database resync from the latest snapshot. In the interim, traffic is being served through secondary infrastructure with updated binaries. Customers may experience intermittent errors or elevated latencies until primary nodes complete the resync process. The Sonic network remains fully operational -- blocks continue to be produced, transactions are processing, and funds are safe.
provider
- monitoring
Our Sonic mainnet RPC nodes are continuing to resync from the latest snapshot. During this process, all traffic is being routed through secondary infrastructure with updated binaries. Websocket connections are unavailable until the resync is complete, and customers may experience elevated latency or intermittent errors on RPC requests. We expect the resync to finish within the next several hours and will provide another update once primary nodes are back online and operating at full capacity.
provider
- monitoring
Several nodes in our primary fleet have successfully resynced and are now serving traffic. However, we are not yet back to full capacity; customers may experience elevated latency or an intermittent error rate. We will provide a final update once all nodes are fully back online
provider
- resolved
This incident has been resolved.
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-aa356de794
Is Alchemy still down?
No, this incident was resolved 2026-03-27 12:42 UTC. For Alchemy's live state, see https://down.guide/alchemy.
How long did it last?
2d 2h, from 2026-03-25 10:16 UTC to 2026-03-27 12:42 UTC, by the times Alchemy posted.
What was affected?
Alchemy named Sonic.
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.