Alchemy Status

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.

The backfill has now finished, and the incident is fully resolved.

Between June 11 and June 12, Solana webhook delivery was disrupted. An internal service issue caused repeated disconnects from the Solana data stream over a ~24 hour window. During each disconnect, events were not recovered, resulting in missed webhook deliveries. This has been resolved. Webhooks are delivering normally for all new events as of June 12 19:30 UTC. If you have active Solana webhook subscriptions, you may notice two things: - Missed events - Some events from the incident window (June 11 19:43 UTC through June 12 19:30 UTC) may not have been delivered. We are working to backfill these. - Possible duplicate events - As part of the backfill, some events from the incident window may be delivered more than once. We recommend handling deduplication on your end using the transaction signature if you haven't already. - New events from June 12 19:30 UTC onwards are unaffected - deliveries are complete and accurate. We will update the status once the backfill is completed. We're sorry for the disruption.

This incident has been resolved.

We managed to fix underlying issue with eth_getLogs, Websockets remain to be affected.

HTTP requests are progressing again. Customers may still experience issues with eth_getLogs and WebSockets. We are actively investigating and will provide further updates shortly.

We are currently investigating Hyperliquid Mainnet stall at block 37597796.

A subset of eth_sendRawTransaction requests are not being propagated to land on chain.

We are investigating consistency issues affecting our EU Central region beginning around 06:58 UTC. Some customers may experience degraded or inconsistent API responses across multiple chains. Mitigation is in progress.