- Level
- confirmed
- Worst impact
- Degraded
- Components
- Robinhood
What to do
Check whether you use Alchemy Robinhood. 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 35m it lasted.
Anything that failed between 2026-09-04 12:56 UTC and 2026-09-04 13:32 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
We are currently investigating this issue.
provider
- investigating
We are continuing to investigate this issue. Team noticed that this is driven by an upstream issue on Robinhood Mainnet - a sharp increase in on-chain activity and block size, combined with brief instability on Robinhood's sequencer feed. This caused some of our nodes to briefly fall behind the chain tip and, during the worst of it, a short window of failed requests.
provider
- resolved
Service is now fully recovered, nodes are caught up with the chain and error rates are back to baseline! Instability upstream on Robinhood chain was concluded as a root cause.
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-6a1f23e567
Is Alchemy still down?
No, this incident was resolved 2026-09-04 13:32 UTC. For Alchemy's live state, see https://down.guide/alchemy.
How long did it last?
35m, from 2026-09-04 12:56 UTC to 2026-09-04 13:32 UTC, by the times Alchemy posted.
What was affected?
Alchemy named Robinhood.
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.