Identified - Degraded eth_getProof responses on Base Mainnet

What to do

• Check whether you use Alchemy Base. 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 6d 3h it lasted.

  Anything that failed between 2026-06-16 07:25 UTC and 2026-06-22 10:35 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

1. identifiedJun 16, 2026, 7:25 AM UTC

   We're aware of an issue affecting eth_getProof requests on Base Mainnet for blocks beyond the most recent ~1,000 blocks. Affected requests may return an error indicating the requested block is outside the available proof window. Recent blocks near the chain tip are unaffected. Our team has identified the cause and is actively working on a fix to restore historical proof coverage. We'll post an update as soon as service is fully restored.

   provider

2. identifiedJun 17, 2026, 11:09 AM UTC

   A fix is in place and eth_getProof data on Base is steadily catching up to the chain tip. We're monitoring as it converges. Other Base methods remain unaffected. We will continue to share updates.

   provider

3. resolvedJun 22, 2026, 10:35 AM 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.