152 recorded Quicknode incidents since June 2026, with official updates, affected components, duration and resolution information.
Solana testnet has been halted by Anza as part of their planned stabilization process. Block production is paused network-wide until the cluster restarts. We're following Anza's restart process and will bring our nodes back online as soon as the network resumes. Solana mainnet and devnet are not affected.
Polkadot Asset Hub Mainnet appears to have stalled at block 22,295,913 in NRT region. The Quicknode team is investigating and will update with more information once it is available.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
Our engineers have upgraded to GreatVoyage-Nile-v4.8.2.4-PQ1-build1, and we're monitoring the node infrastructure. https://github.com/tron-nile-testnet/nile-testnet/releases/tag/GreatVoyage-Nile-v4.8.2.4-PQ1-build1
This incident has been resolved.
The Quicknode team is investigating degraded performance of Robinhood Mainnet - we are seeing increased latency and timeouts on select RPC methods. We will update this page as we acquire new information.
We have identified the root cause of the increased latency and timeouts affecting Robinhood Mainnet on select methods, including debug_traceBlockByNumber, eth_getBlockReceipts, eth_getLogs, and eth_getBlockByNumber. Our engineers have disabled the affected backends and are actively working to restore full service. Some stream-based services may continue to experience delays as they catch up. We will provide another update as the situation progresses.
We have replaced the affected backend infrastructure. Latency and timeouts on select RPC methods on Robinhood Mainnet have returned to normal, and affected Streams have caught up. We are continuing to monitor.
This incident has been resolved.
We are investigating an issue with our internal Quicknode API that is causing authentication failures for multiple accounts. Quicknode Streams, KV Store REST API, and Webhooks are currently affected. We will update this page as we acquire new information.
The issue affecting our API authentication has been resolved. The incident was limited to a small number accounts. All services, including Quicknode Streams, KV Store, and Webhooks, are operating normally.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're investigating an issue on Arbitrum Nova where no new blocks have been produced since block 85283638. We're in contact with the Arbitrum team to understand the cause, and we'll share an update as soon as we have more information.
Block production on Arbitrum Nova has resumed, and our nodes are syncing normally. Thanks for your patience.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Solana Mainnet is currently undergoing a regenesis as part of the Alpenglow upgrade. We are monitoring the process and will provide updates as more information becomes available.
This incident has been resolved.
We are currently investigating the elevated API errors being served on Near Mainnet. We will post updates as we receive further information.
Service has stabilized and we are monitoring for stability.
This incident has been resolved.
The Aptos Foundation is beginning a scheduled state reset on Aptos Testnet at 17 UTC today, per AIP-147. The reset returns Testnet to a fresh genesis and clears all prior on-chain state. The Aptos Foundation expects the process to take a few hours, with up to 48 hours possible if complications arise. What this means for you: Once resync completes, previously deployed contracts, test accounts, and balances on Aptos Testnet no longer exist. You'll need to redeploy contracts and recreate test state against the new genesis.
This incident has been resolved.
We are currently investigating a block height stall on Injective Mainnet. Nodes stopped advancing at block 186,223,485, and requests may return stale data until block production resumes. Our team is actively working on this and we will provide an update as soon as we have more information.
The Injective Foundation has confirmed the issue and will be publishing an upgrade guide shortly. Injective Mainnet remains stalled at block 186,223,485. We will apply the upgrade to our nodes as soon as it is available and share another update once the rollout is underway.
Injective Mainnet has resumed block production and our nodes are advancing past block 186,223,485 again. Requests are returning current data and the block height stall is no longer occurring. We will continue to monitor the network to confirm stability.
Injective Mainnet has remained stable since block production resumed, and our nodes are fully synced and serving current data. This incident is now resolved. Thank you for your patience.
X Layer Testnet appears to have stalled at block 42837767 - The Quicknode team is investigating and will update with more information once it is available.
We have identified the cause of the X Layer Testnet network stall at block 42837767. Our engineers are currently upgrading our nodes to restore service. We will provide further updates as progress is made.
Service has been restored for X Layer Testnet, and requests are being served at the current chain head. Our engineers continue to work on the affected nodes and monitor stability.
This incident has been resolved.
World Chain Mainnet requests may intermittently return 503 errors. We've identified the cause as an issue in the node client affecting some of our backend nodes, and we're working with the World Chain team to resolve it. We're monitoring closely and will share updates as they become available.
The World Chain team has confirmed the root cause of the intermittent 503 errors and is preparing a new node client release with a fix. We'll deploy it across our World Chain Mainnet nodes as soon as it's available. In the meantime, we're continuing to monitor closely, and some requests may still intermittently return 503 errors.
This incident has been resolved.
Blast Sepolia appears to have stalled at block 43,081,817. The Quicknode team is investigating and will update with more information once it is available.
This incident has been resolved.
The Quicknode team is investigating degraded performance of TON Mainnet - we will update this page as we acquire new information.
The issue has been identified and working with the Ton Foundation to implement fixes.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
Since September 23, many nodes that don't forward traffic have joined TON's public overlay, the peer network our nodes use to receive blocks and pass on transactions. Because our nodes were connected to some of these peers, block sync slowed and some transactions were not delivered. For more detail, see the TON Foundation's announcement: https://t.me/tonstatus/244
The Quicknode team is investigating the degraded performance of Injective Mainnet - we will update this page as we acquire new information.
We have identified the root cause of the degraded performance affecting Injective Mainnet. We will continue to monitor and provide updates as the situation improves.
This incident has been resolved.
We are investigating an elevated level of 503 errors on Hyperliquid Mainnet. We will update this page as we acquire more information.
The 503 errors affecting Hyperliquid Mainnet have been resolved. All backends are healthy and operating normally. We will continue to monitor the situation.
We're investigating an issue affecting Vana Moksha testnet endpoints. Our nodes have stopped syncing at block 9,268,235, so requests may return stale data. Our team is looking into the cause and we'll share an update as soon as we have more information.
We're working with the foundation to recover our nodes. A fix has been applied, and our nodes are now syncing back up. We're continuing to monitor closely to ensure stability.
This incident has been resolved.
