QuickNode had 229 outages in the last 2 years totaling 408h 50m of downtime — averaging 9.4 incidents per month.
There were 229 QuickNode outages since March 6, 2026 totaling 408h 50m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are investigating increased latency of Hyperliquid Mainnet - we will update this page as we acquire new information.
The elevated latency issue affecting Hyperliquid Mainnet has been resolved. All systems are operating normally. We will continue to monitor for any recurrence.
The Quicknode team is investigating the degraded performance of Base Mainnet - we will update this page as we acquire new information.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating intermittent packet loss in the NRT region. Users may experience 503s/ timeouts.
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 experiencing an elevated level of API errors and are currently looking into the issue.
This incident has been resolved.
The Quicknode team is investigating degraded performance of RobinHood Mainnet - we will update this page as we acquire new information.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The Quicknode team is investigating degraded performance on Solana Mainnet. Users may be experiencing elevated 503 errors at this time. 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.
A network stress test is scheduled by the foundation at 18 UTC, and customers may experience degraded performance and elevated API errors during this time. We will update this page as we acquire new information.
This incident has been resolved.
The Quicknode team is investigating degraded performance of BSC Mainnet in the FRA region. We will update this page as we acquire new information.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cosmos Mainnet appears to have stalled at block 32,878,318 - The Quicknode team is investigating and will update with more information once it is available.
The underlying issue has been identified. We are working with the Foundation to restore normal block progression. Further updates will be provided as the situation develops.
Our nodes have recovered and are back at the chain tip. We are continuing to monitor the situation and will provide further updates as needed.
This incident has been resolved with direct communication with Cosmos Labs. Please see the Cosmos Lab's post for additional information on their binary package used to resolve this incident: https://x.com/cosmoslabs_io/status/2097986609433960711
Solana Testnet appears to have stalled at block 440004508 — This is a chain wide stall. We are following up with the Foundation channel and working toward restoring normal block progression. Further updates will be provided as the situation develops.
This incident has been resolved.
Gravity Mainnet appears to have stalled at block 41,384,106. The Quicknode team is investigating and will update with more information once it is available.
The underlying issue has been identified. We are working with the Foundation to restore normal block progression. Further updates will be provided as the situation develops.
This incident has been resolved. Gravity Mainnet has resumed normal block progression past block 41,384,106.
We are investigating increased latency on RobinHood Mainnet. The Quicknode team has notified the foundation and will update this page as we acquire new information.
The RobinHood foundation team has been notified and is actively investigating, this appears to be unrelated to Quicknode. We will provide further updates as more information becomes available.
The RobinHood foundation team has confirmed everything has returned back to normality. Our engineering team is actively monitoring performance.
Users may continue to experience degraded performance and issues with transaction landing on Robinhood Mainnet. We are currently investigating connection issues regarding the sequencer feed and are closely listening to updates from the foundation.
The upstream feed connection issues have stabilized and we are monitoring for stability.
This incident has been resolved.
The Quicknode team is investigating degraded performance of Injective Mainnet — we will update this page as we acquire new information.
We are continuing to investigate this issue.
The issue causing elevated errors and 503 responses on Injective Mainnet has been resolved. All systems are operating normally. We are monitoring for stability
The elevated errors and degraded performance affecting Injective Mainnet have been resolved. All systems are operating normally.
Injective Mainnet appears to have stalled chain wide at block 181,027,000. The team is investigating and will update with more information once it is available.
We have identified a possible root cause for the Injective Mainnet block height stall. A high priority patch is being deployed, and a network-wide upgrade may be in progress. We will continue to monitor and provide updates as more information becomes available.
Our nodes are starting to recover following the patch deployment. We'll post another update once the system is fully operational.
This incident has been resolved.
Gravity Mainnet appears to have stalled at block 39,007,386 - The Quicknode team is investigating and will update with more information once it is available.
The underlying issue has been identified. We are working with the Foundation to restore normal block progression. Further updates will be provided as the situation develops.
This continues to be an upstream issue on the Gravity network, not related to our infrastructure. Block production has partially resumed, with some nodes still catching up. We'll keep watching closely and update as the situation develops.
This incident has been resolved.
We are currently investigating a network wide stall at block height 8,335,793.
We are continuing to investigate a network-wide stall at block height 8,335,793. As this is affecting the entire network, we're currently waiting on guidance from the foundation before proceeding. We'll provide updates as soon as more information becomes available.
This incident has been resolved.
We are currently investigating degraded performance on zkSync Era Testnet, with timeouts and 503 errors. We will provide updates as more information becomes available.
This incident has been resolved. zkSync Sepolia is operating normally.
We've identified an upstream issue causing timeouts and 503 errors on HyperLiquid Testnet. Updates to follow.
This incident has been resolved. HyperLiquid - HyperEVM-Testnet is operating normally.
The Quicknode team is investigating the degraded performance of Stellar Mainnet JSON-RPC - we will update this page as we acquire new information.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating degraded performance on Moca Testnet, with elevated latency and 503 errors. We will provide updates as more information becomes available.
A fix has been implemented and services have returned to normal. We are monitoring closely to ensure stability.
This incident has been resolved. Moca Testnet is operating normally.
We are currently investigating degraded performance on Stacks Mainnet, with elevated latency and 503 errors. We will provide updates as more information becomes available.
A fix has been implemented and services have returned to normal. We are monitoring closely to ensure stability.
This incident has been resolved. Stacks Mainnet is operating normally.
We are following up with the Foundation and working toward restoring normal block progression. Further updates will be provided as the situation develops.
This incident has been resolved.
We have investigated degradation and identified the cause on archive nodes related to an upstream issue.
This incident has been resolved.
We are investigating the degradation of Arbitrum Mainnet archive requests. Users may experience elevated latenc, 503 responses, and API errors during this time.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.