- Level
- confirmed
- Worst impact
- Degraded
- Components
- Cronos
What to do
Check whether you use Alchemy Cronos. 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 3h 13m it lasted.
Anything that failed between 2026-07-24 09:36 UTC and 2026-07-24 12:49 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 4
- investigating
A subset of requests on Cronos Mainnet are experiencing availability issues.
provider
- investigating
We are continuing to investigate this issue.
provider
- identified
A part of our Cronos nodes were down due to a binary issue.
provider
- resolved
Nodes have been rescyned with stable binary and services are back to healthy.
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-5b4ff3a652
Is Alchemy still down?
No, this incident was resolved 2026-07-24 12:49 UTC. For Alchemy's live state, see https://down.guide/alchemy.
How long did it last?
3h 13m, from 2026-07-24 09:36 UTC to 2026-07-24 12:49 UTC, by the times Alchemy posted.
What was affected?
Alchemy named Cronos.
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.