- 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 0m it lasted.
Anything that failed between 2026-05-14 18:42 UTC and 2026-05-14 18: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 1
- resolved
A subset of our Cronos Mainnet nodes briefly stalled and stopped advancing during a short window between approximately 18:17 UTC and 18:28 UTC. The chain itself remained available to peers, and service has fully recovered. We are coordinating with the Cronos team to determine the root cause. 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-4a85dbeb0c
Is Alchemy still down?
No, this incident was resolved 2026-05-14 18:42 UTC. For Alchemy's live state, see https://down.guide/alchemy.
How long did it last?
0m, from 2026-05-14 18:42 UTC to 2026-05-14 18:42 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.