QuickNode had 248 outages in the last 2 years totaling 736h 56m of downtime — averaging 10 incidents per month.
There were 248 QuickNode outages since March 6, 2026 totaling 736h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.
Flow Testnet EVM (JSON-RPC API) nodes stalled at block height 118,361,371. Our team is actively investigating and will provide an update once more information becomes available.
This incident has been resolved.
The Quicknode team is investigating the degraded performance of Ethereum Hoodi Testnet. Some users may experience 503 errors at this time. We will update this page as we acquire new information.
The Quicknode team has identified the root cause of the recent degradation affecting the Ethereum Hoodi nodes. Currently, the historical blob data for Ethereum Hoodi nodes is limited to slots >= 3,375,000. Requests for blob data prior to this slot may be temporarily unavailable. We are working on restoring complete historical blob coverage and will keep this page updated as the work progresses.
Historical blob data for Ethereum Hoodi nodes prior to slot 3,375,000 is now being served correctly, resolving the previous limitation. Full historical blob coverage has been restored. A fix has been implemented and we are monitoring the results to confirm full stability.
This incident has been resolved.
We are investigating an issue with Hedera Testnet resulting in elevated 503 errors. Users may experience failed or interrupted requests. Our team is actively investigating and will provide updates as more information becomes available.
We have identified the root cause of the elevated 503 errors on Hedera Testnet. The issue was caused by rate limiting (429s) on an upstream node. The affected node has been addressed and service has been restored. We are monitoring for continued stability.
This incident has been resolved.
Base Mainnet is experiencing a chain-wide stall. The Quicknode team is investigating and will update this page as more information becomes available. For reference, please see the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4
Nodes have been restarted and the chain stall has been resolved. 503 errors are no longer observed. We are monitoring the service for continued stability as backfill requests normalize.
This incident has been resolved.
We are currently performing maintenance and an upgrade on HyperEVM and Hypercore gRPC. Users may experience disruptions during this time. We will provide updates as the work progresses.
The HyperEVM and Hypercore maintenance / upgrade has been completed. All systems are operating normally.
B3 Mainnet appears to have stalled at block 60028954 due to a chain-wide stall on Base Mainnet, which B3 depends on. The QuickNode team is investigating and will update this page as more information becomes available. For Base Mainnet status, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4
B3 Mainnet block production has resumed and the network stall at block 60028954 has been resolved. This incident was related to a chain-wide stall on Base Mainnet. All systems are now operating normally.
Base Mainnet block production is currently unhealthy during the activation of the Beryl Upgrade. For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4
The Base Team has identified the issue with a problematic block interfering with subsequent block building. Their team is working on several threads to remediate. We will provide further updates as the situation develops. For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4
The Base team is continuing to debug and have isolated a consensus problem that caused an invalid block to be sequenced. This prevented new blocks from being created following block 47806542. The Base team is working on a fix to resume block propagation to the network while further isolating the root cause of the problematic block. For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The Quicknode team is investigating the degraded performance of Ethereum mainnet archived nodes. Customers may experience increased error rates, including 503 responses, when querying archive data. We will update this page as we acquire new information.
The underlying issue has been identified, and a mitigation is in place. Some nodes have recovered, and 503s have been mitigated. Quicknode teams are continuing to work to recover full capacity and monitor performance to ensure stability.
This incident has been resolved.
The Quicknode team is investigating degraded performance on XRP Ledger Mainnet. Some users may be experiencing 503 errors. We will update this page as we acquire new information.
The issue has been identified and a fix is being implemented.
The 503 errors have now been resolved. We are monitoring for stability.
This incident has been resolved.
We are investigating an outage affecting the Quicknode Dashboard. We will update this page as we acquire new information.
The QuickNode Dashboard is back online and our services have recovered. We are monitoring the situation.
The QuickNode Dashboard has been restored and is operating normally.
The Foundation has intentionally halted Solana Devnet starting at approximately 16:00 UTC. We will update this page once the network resumes.
The Solana Devnet restart has completed successfully. We are monitoring the network for stability and will provide further updates as needed.
This incident has been resolved.
HyperEVM Testnet block production is currently halted. The Hyperliquid foundation has confirmed the testnet network is offline for testing. Quicknode infrastructure is healthy and fully operational - all backends remain reachable and will resume serving new blocks once the network restarts. No action is required on your end.
The upstream network maintenance affecting HyperEVM Testnet has concluded. Block production has resumed and the network is operating normally.
We are currently investigating this issue.
Our engineers are closely listening to updates from the foundation. https://statuspage.incident.io/uniswap-status/incidents/01KVC95SYQFYPWXZW6QPM3WD99
A fix has been implemented by the foundation and we are monitoring the results. https://statuspage.incident.io/uniswap-status/incidents/01KVC95SYQFYPWXZW6QPM3WD99
This incident has been resolved.
The QuickNode team is investigating the degraded performance of Monad Mainnet in the LAX region - we will update this page as we acquire new information.
Additional Capacity was added to mitigate the degraded performance of the affected nodes in the region. Performance should now be stable and we are monitoring as we fully resolve the issue.
This incident has been resolved.
The Quicknode team is investigating degraded performance of Ethereum Hoodi. Users may experience 503 errors at this time. We will update this page as we acquire new information.
Our nodes have recovered. We are actively monitoring the results.
This incident has been resolved.
The QuickNode team is investigating degraded performance affecting multiple chains in the Singapore region. We will update this page as we acquire new information.
The degraded performance affecting multiple chains in the Singapore region have resolved and we are monitoring for stability.
This incident has been resolved.
Billing metrics in the Quicknode dashboard are currently experiencing a delay and may display usage behind current levels. Actual billing is not affected. We are investigating and will provide updates as more information becomes available.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The QuickNode team is investigating degraded performance of Aleo Mainnet — some nodes are currently reporting block heights behind the network tip. Users may experience stale block height responses. We will update this page as we acquire new information.
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.
Ault Testnet appears to have stalled at block 18,581,300. The QuickNode team is investigating the network wide stall.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cyber Mainnet appears to have stalled at block 33,825,690 - The QuickNode team is investigating and will update with more information once it is available.
Pods are recovering and the issue appears to be resolved. We are monitoring Cyber Mainnet to confirm full stability.
The issue with Cyber Mainnet has been resolved. Pods have fully recovered and the network is operating normally. We appreciate your patience during this time.
We are currently investigating an issue affecting the 0g Galileo Testnet in which the block height has stalled at 37,983,645. Further updates will be provided as the situation develops.
This incident has been resolved.
We are currently investigating an issue affecting Ault Mainnet in which the block height has stalled at 9,763,957. We are in active communication with the Foundation and are working toward restoring normal block progression. Further updates will be provided as the situation develops.
The block height stall on Ault Mainnet has been resolved. All nodes are now up to tip and operating normally.
The QuickNode team is investigating degraded performance of HyperEVM Testnet - we will update this page as we acquire new information.
We are monitoring HyperEVM Testnet for continued stability and will provide further updates as needed.
The issue affecting HyperEVM Testnet has been resolved. 503 errors have cleared and all systems are operating normally. We will continue to monitor for any recurrence.
We are investigating an issue with Injective Mainnet Tendermint JSON-RPC/REST API returning 503 errors. Our team is actively working to resolve this and will provide updates as more information becomes available.
We have temporarily added nearby region to mitigate the 503 issue. Some users may experience elevated latency at this time. Our team is actively working to resolve this and will provide updates as more information becomes available.
We are continuing to investigate this issue.
We have added additional regions to mitigate the 503 errors affecting Injective Mainnet. We are monitoring the service for stability and will provide further updates as needed.
The 503 errors affecting Injective Mainnet have been resolved. Additional regions were added to mitigate the issue and affected nodes have been brought back online. All systems are operating normally.
We are currently investigating a block height stall affecting HyperEVM Testnet endpoints. We will provide updates as the investigation progresses.
The network has recovered and we are monitoring the results.
This incident has been resolved.