Degraded eth_getLogs across multiple networks

What to do

• Check whether you use Alchemy Ethereum, Polygon, World Chain. 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 14m it lasted.

  Anything that failed between 2026-07-15 17:00 UTC and 2026-07-15 17:15 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 4

1. identifiedJul 15, 2026, 2:52 PM UTC

   We're investigating elevated error rates and latency on eth_getLogs across multiple networks. We've identified the cause and are actively working on mitigation. We'll share an update as recovery progresses.

   provider

2. identifiedJul 15, 2026, 5:00 PM UTC

   The fix that we have applied is working well for Ethereum and Polygon mainnets, and we see full recovery there. Our team continues to work on recovering Worldchain.

   provider

3. monitoringJul 15, 2026, 5:11 PM UTC

   We have applied a fix for all of the impacted chains and are monitoring the results.

   provider

4. resolvedJul 15, 2026, 5:15 PM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.