Alchemy incident
Identified - Degraded eth_getProof responses on Base Mainnet
Resolved after 6 days 3 hours, affecting Base, on June 16, 2026.
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.
Affected components
Update timeline
- identified Jun 16, 2026, 07: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 full historical proof coverage. We'll post an update as soon as service is fully restored.
- identified Jun 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.
- resolved Jun 22, 2026, 10:35 AM UTC
This incident has been resolved.
Your product runs on more than Alchemy
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services