Alchemy had 139 outages in the last 2 years totaling 77h 17m of downtime — averaging 5.7 incidents per month.
There were 139 Alchemy outages since March 4, 2026 totaling 77h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.
A subset of eth_sendRawTransaction requests on Hyperliquid Mainnet routed through our Asia Pacific region are seeing increased delays and elevated error rates.
We are continuing to investigate this issue.
This incident has been resolved.
A subset of eth_getLogs requests on Monad Mainnet routed through our EU Central region are seeing increased delays.
This incident has been resolved.
We are investigating degraded performance affecting requests on Sui Mainnet.
We are continuing to investigate this issue.
This incident has been resolved.
Between 22:35 and 22:55 UTC on July 30, a subset of requests on Robinhood Mainnet experienced elevated latency. This incident has been resolved.
A subset of eth_sendRawTransaction requests on Hyperliquid Mainnet are seeing increased delays for requests routed through our EU Central region.
This incident has been resolved.
We are investigating a network-wide stall affecting safe and finalized blocks on Base Mainnet.
This is a network-wide issue on Base Mainnet, not specific to Alchemy. The Safe head is delayed because data batching to Ethereum L1 is lagging. New block production on Base Mainnet is progressing normally, and requests against the latest block are unaffected. Only queries and workflows that depend on the safe or finalized block tag will see staleness. Refer to the Base status page for the latest updates: https://status.base.org/incidents/j6y12tshwkcg
This is resolved. Base Mainnet's Safe head has caught up and data batching to Ethereum L1 is back to normal. Block production was unaffected throughout. See the Base status page for their full update: https://status.base.org/incidents/j6y12tshwkcg
A subset of requests on Stable Mainnet are experiencing degraded
Nodes were unable to progress, team carried out a restart of the nodes and are seeing recovery and improved performance on requests. Actively monitoring.
Nodes have recovered and services are healthy again.
A subset of requests on Cronos Mainnet are experiencing availability issues.
We are continuing to investigate this issue.
A part of our Cronos nodes were down due to a binary issue.
Nodes have been rescyned with stable binary and services are back to healthy.
A subset of requests on Robinhood Mainnet routed through our Asia Pacific region may be experiencing increased latency.
This incident has been resolved.
We are investigating a network-wide stall affecting Zora, Ronin, BOB, Katana, Mode, Metal, and Superseed networks.
We are investigating a network-wide stall affecting Zora, Ronin, BOB, Codex, Mode, and Superseed networks.
Update: Zora has recovered. Mode mainnet has recovered; Mode Sepolia (testnet) is still degraded. Ronin, BOB, Codex, and Superseed remain impacted. We are continuing to monitor.
Update: All impacted networks have recovered except Mode Sepolia (testnet), which is still degraded. We are continuing to monitor Mode Sepolia.
Resolved: All impacted networks, including Mode Sepolia (testnet), have fully recovered and caught up. This incident is now resolved.
We are investigating elevated latency affecting a subset of requests in our US West region.
We identified the root cause and the affected service has been failed over. We are monitoring for full recovery!
Traffic has been fully restored to the US West region. This incident is now resolved!
We are investigating elevated error rates and increased latency on BNB Smart Chain Mainnet. Some requests may fail or respond slower than usual. Our team is actively working on a fix and we will post updates here as we learn more.
We experienced node-level failure on BNB Mainnet which caused a subset of our nodes to become unavailable. As a result, increased load was placed on our remaining infrastructure, further contributing to degraded response times. A node binary fix was deployed and we are seeing recovery.
We have confirmed full recovery across our BNB Smart Chain Mainnet infrastructure. All nodes are healthy and serving traffic normally, with response times and error rates back to baseline. This incident is now resolved. Thank you for your patience!
We are currently investigating an issue impacting transaction propagation on Soneium Mainnet.
This incident has been 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.
We are currently investigating an issue affecting Zora Sepolia nodes, resulting in failed requests and errors on this network. Our team is actively working to restore service and is coordinating with the Zora team on a resolution. We will provide an update as soon as we have more information.
This incident has been resolved.
We are investigating a network-wide stall affecting safe and finalized blocks on Abstract Mainnet.
This incident has been resolved.
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.
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.
We have applied a fix for all of the impacted chains and are monitoring the results.
This incident has been resolved.
We are currently investigating an issue resulting in increased errors and latency on Solana mainnet.
The issue has been identified and we've rolled out a fix.
This incident has been resolved.
We're seeing increased latency and higher block times on Tempo Testnet. This is caused by a planned stress test run by the Tempo network team, not by Alchemy infrastructure. The test window is expected to last up to 2 hours starting 2PM UTC on July 15. Performance should recover once the test concludes. No action is required on your end.
We are continuing to investigate this issue.
This incident has been resolved.
We're currently investigating an issue impacting performance on Cronos Mainnet.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are actively investigating an issue affecting Robinhood Mainnet where there are delayed user operation inclusion times.
We are currently seeing recovery.
We are investigating degraded performance affecting our Data APIs on BNB Smart Chain. A subset of requests may experience errors or increased latency.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
This incident has been resolved.
This incident has been resolved.
We are investigating degraded performance affecting Optimism Mainnet Data APIs.
This incident has been resolved.