- Level
- confirmed
- Worst impact
- Degraded
- Components
- Polygon
What to do
Check whether you use Alchemy Polygon. 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 49m it lasted.
Anything that failed between 2026-08-13 14:52 UTC and 2026-08-13 15:41 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
Following today's Polygon network hard fork, some trace methods on Polygon Mainnet are currently failing. This is a network-wide issue affecting all providers, as the Polygon team has not yet released a client binary with trace API support for the new fork. We expect the Polygon team to ship an updated binary restoring trace support, and we will roll it out as soon as it is available. We'll post updates here as we learn more.
provider
- resolved
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-3be08c4c88
Is Alchemy still down?
No, this incident was resolved 2026-08-13 15:41 UTC. For Alchemy's live state, see https://down.guide/alchemy.
How long did it last?
49m, from 2026-08-13 14:52 UTC to 2026-08-13 15:41 UTC, by the times Alchemy posted.
What was affected?
Alchemy named Polygon.
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.