- Level
- confirmed
- Worst impact
- Degraded
- Components
- Stable
What to do
Check whether you use Alchemy Stable. 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 12m it lasted.
Anything that failed between 2026-07-27 03:39 UTC and 2026-07-27 06:51 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
A subset of requests on Stable Mainnet are experiencing degraded
provider
- identified
Nodes were unable to progress, team carried out a restart of the nodes and are seeing recovery and improved performance on requests. Actively monitoring.
provider
- resolved
Nodes have recovered and services are healthy again.
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-d33334a7fe
Is Alchemy still down?
No, this incident was resolved 2026-07-27 06:51 UTC. For Alchemy's live state, see https://down.guide/alchemy.
How long did it last?
3h 12m, from 2026-07-27 03:39 UTC to 2026-07-27 06:51 UTC, by the times Alchemy posted.
What was affected?
Alchemy named Stable.
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.