- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-east-1
What to do
Check whether you use Alchemy in us, us-east-1. 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-07-18 09:02 UTC and 2026-07-17 20:00 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
Between approximately 23:20 UTC on July 17 and 03:30 UTC on July 18, some Polygon Mainnet requests experienced slower than normal response times, mainly for log queries. The issue was limited to the us-east-1 region. The cause was an unusually heavy request load that put pressure on part of our infrastructure in the region. We added extra capacity and rebalanced traffic, after which performance returned to normal. The issue is fully resolved. We apologize for the disruption.
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-97955ce5f2
Is Alchemy still down?
No, this incident was resolved 2026-07-17 20:00 UTC. For Alchemy's live state, see https://down.guide/alchemy.
How long did it last?
0m, from 2026-07-18 09:02 UTC to 2026-07-17 20:00 UTC, by the times Alchemy posted.
What was affected?
Alchemy named in us, us-east-1.
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.