- 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 1h 23m it lasted.
Anything that failed between 2026-08-31 12:15 UTC and 2026-08-31 13:38 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 2
- investigating
Network wide incident is affecting Cronos Mainnet and block production has been halted: https://x.com/CronosNetwork/status/2094072333434769703
provider
- resolved
Incident is resolved and blocks are being produced again - confirmed by Cronost team: https://x.com/CronosNetwork/status/2094417832394301499
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-0fb7b4688a
Is Alchemy still down?
No, this incident was resolved 2026-08-31 13:38 UTC. For Alchemy's live state, see https://down.guide/alchemy.
How long did it last?
1h 23m, from 2026-08-31 12:15 UTC to 2026-08-31 13:38 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.