Alchemy had 172 outages in the last 2 years totaling 147h 16m of downtime — averaging 7.1 incidents per month.
There were 172 Alchemy outages since March 4, 2026 totaling 147h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are investigating elevated latency affecting getSignaturesForAddress requests on Solana Mainnet in the US East region.
A routing change has been implemented, and we are observing latency returning to normal levels.
This incident has been resolved.
A subset of getSignaturesForAddress requests on Solana Mainnet experienced increased latency between 08:20 and 09:30 UTC and has since recovered.
A subset of requests on Robinhood Mainnet are experiencing increased latency in the APAC region.
This incident has been resolved.
We are investigating elevated latency and block lag affecting a subset of requests. Our team is actively working to restore normal performance and will provide an update soon.
We are investigating elevated latency and block lag affecting a subset of requests due to upstream feed relay instabilities. Our team is actively working to restore normal performance and will provide an update soon.
A fix has been implemented and we are monitoring the results.
The upstream feed relay instabilities have been resolved, and latency and block lag have returned to normal.
We are currently investigating this issue.
We are continuing to investigate this issue.
This is now fully recovered, nodes are caught up with the chain and error rates are back to baseline!
Investigating elevated API errors affecting requests across multiple networks. We are working to restore normal service and will provide updates as more information becomes available.
The issue has been identified and a fix is being implemented.
We are no longer seeing elevated errors in local testing and are monitoring the situation closely.
We are observing an increase in successful responses and are monitoring the situation closely.
The incident has been resolved. We are continuing to monitor the situation.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Monad Mainnet will undergo a planned network upgrade at 14:30 UTC today. No downtime or customer impact is expected. We will monitor the upgrade and provide updates if needed. Upgrade details:
Scheduled maintenance is currently in progress. We will provide updates as necessary.
We’re investigating elevated error rates and latency affecting some API requests across multiple regions. Our team is actively working to restore normal performance.
The issue has been identified and a fix is being implemented.
Robinhood Mainnet is seeing recovery. We're continuing to monitor.
Arbitrum Mainnet is seeing recovery. We're continuing to monitor.
All networks are seeing recovery. We're continuing to monitor. You might still see elevated latencies on Arbitrum, BSC and Robinhood. We expect them to come back to baseline shortly.
Arbitrum, BSC and Robinhood continue to exhibit slightly higher latencies than baseline. All other networks are back to baseline.
All networks latencies are back to baseline.
Network wide incident is affecting Cronos Mainnet and block production has been halted: https://x.com/CronosNetwork/status/2094072333434769703
Incident is resolved and blocks are being produced again - confirmed by Cronost team: https://x.com/CronosNetwork/status/2094417832394301499
A subset of requests on Ethereum Mainnet are experiencing elevated latency.
The issue has been identified and a fix is being implemented.
The elevated latencies affecting Ethereum Mainnet Data APIs have been resolved.
A subset of Data API requests on Robinhood Mainnet are experiencing increased latency and error rates.
This incident has been resolved.
WebSocket connections to X Layer Mainnet in our US East region are being established normally, but subscription events may be delayed or missing. HTTP requests are not affected.
A fix has been implemented, and we are monitoring the results.
This incident has been resolved! WebSocket subscription delivery for X Layer Mainnet in our US East region has returned to normal. HTTP requests were not affected at any point during this incident
We are currently investigating reports of elevated latency on API requests for Robinhood Mainnet, which may also affect aggregated endpoints such as Token API balance lookups. We will provide an update as more information becomes available!
This incident has been resolved. Between approximately 21:58 UTC and 22:12 UTC, some API requests on Robinhood Mainnet experienced elevated latency. All services are currently operating normally. We will continue to investigate the underlying cause to prevent recurrence!
We're observing a network wide chain stalled on Xdc Testnet - stopped at block: 85974607 See Xdc Testnet block explorer here: https://testnet.xdcscan.com/block/85974607
This incident has been resolved.
We're observing a network wide chain stalled on Zetachain mainnet - stopped at block: 18349554 See Zetachain block explorer here: https://zetascan.com/block/18349554
This incident has been resolved.
We are investigating reports of delayed safe and finalized block tag data on Unichain Mainnet for requests routed through our US East (use1) region. The latest block head and overall API serving are healthy and unaffected. Applications relying on safe/finalized tags (e.g. via eth_getBlockByNumber, eth_getLogs, eth_call) in this region may receive outdated block data. We are actively investigating and will provide updates as we have them!
A subset of nodes serving Unichain Mainnet in our US East (use1) region experienced stalled safe/finalized block tracking, causing delayed safe/finalized block data for requests routed through that region. The latest block head and overall API serving were unaffected throughout and no elevated error rates were observed. We performed a rolling restart of the affected nodes, which resolved the issue. Safe/finalized data is now current and within normal lag across the region. This incident is resolved!
A subset of eth_getLogs and debug_traceTransaction requests on BNB Smart Chain Mainnet are experiencing high latencies. We are actively investigating these issues and pursuing mitigation.
Resolved - Elevated latency on BNB Smart Chain Mainnet JSON-RPC requests has been fully mitigated. All methods are performing within normal latency ranges!
We are investigating elevated latency affecting Robinhood Mainnet requests. Our team is working to restore normal performance.
Our team is continuing to investigate elevated latency affecting Robinhood Mainnet requests.
Latency has returned to normal for Robinhood Mainnet. We will continue to monitor the service.
A subset of eth_getLogs requests on Polygon Mainnet are seeing increased delays.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating an issue causing Solana Streaming (WebSocket and gRPC) to be unavailable in Tokyo, Frankfurt, New York, and Salt Lake City. We will provide an update as more information becomes available.
The immediate issue has been mitigated, and we’re working on the final fix.
This incident has been resolved.
Some transactions submitted on Polygon Mainnet were taking longer than expected to propagate and land onchain. A fix has been applied and we are monitoring the results.
This incident has been resolved.
Following today's Polygon network hard fork, some trace methods on Polygon Mainnet are currently failing. This is a network-wide issue affecting all providers, as the Polygon team has not yet released a client binary with trace API support for the new fork. We expect the Polygon team to ship an updated binary restoring trace support, and we will roll it out as soon as it is available. We'll post updates here as we learn more.
This incident has been resolved.
We are investigating elevated latency affecting requests to Injective Mainnet in the US East region. Error rates remain within normal levels. We will provide an update as more information becomes available.
This incident has been resolved. Injective Mainnet performance has returned to normal.