QuickNode had 246 outages in the last 2 years totaling 521h 6m of downtime — averaging 10 incidents per month.
There were 246 QuickNode outages since March 6, 2026 totaling 521h 6m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
We are investigating an elevated rate of 503 errors affecting eth_getLogs requests on BNB Smart Chain Mainnet. We will update this page as we acquire new information.
This incident has been resolved.
The Polygon Foundation is running a stress test on the Amoy network at 15:00 UTC. Users may experience elevated latencies and degraded performance during the duration of the stress test. We will keep this page updated as the test progresses.
The Polygon Foundation is currently running a stress test on the Amoy network. Users may experience elevated latencies, 503 responses and degraded performance during the duration of the stress test. Our team is working to resolve the degradation and we will follow up on this page with further updates.
The degraded performance and 503 responses for Polygon Amoy have been resolved. We are monitoring for stability.
This incident has been resolved.
BSC Mainnet is experiencing degraded performance on archive RPC methods. Some requests for historical data (trace, debug, and historical state lookups) may see increased latency or intermittent 503 errors. We are monitoring the situation and working on a resolution.
Performance on archive RPC methods has improved significantly. We are continuing to monitor the situation.
This incident has been resolved. Archive RPC methods are operating normally across all regions. We will continue to monitor for any recurrence.
The Quicknode team is investigating degraded performance of Base Sepolia in FRA region. We will follow up once we have more updates.
A fix has been implemented and we are monitoring the results.
The Quicknode team is investigating degraded performance of Base Sepolia. Users may observe 503 responses from their requests. We will follow up once we have more updates.
Customers may experience higher error rates, including 503 responses. We are in active communication with the Foundation and waiting for a new release to mitigate this. Further updates will be provided as the situation develops.
The Quicknode team is investigating the degraded performance of Base Sepolia - we will update this page as we acquire new information.
Our team is actively listening to updates from the Base team regarding Base Sepolia degradation. A fix has been identified and is being implemented by the Base team for the Base node client. We will update this page as we receive further updates.
The issue has been resolved and Base Sepolia services are operating normally.
We identified an issue causing elevated error rates for Monad RPC requests. Our team has deployed a fix, and error rates have returned to normal. We are continuing to monitor the service to ensure stability.
This incident has been resolved.
We've identified an outage affecting Hyperliquid EVM Testnet. The root cause is an upstream stall on Hyperliquid's testnet network infrastructure, unrelated to QuickNode services. Users may experience failed or timed-out RPC requests until the upstream network resumes. We will continue monitoring and provide updates as they become available.
This incident has been resolved. Block production on Hyperliquid's testnet network has resumed and service is back to normal.
We are currently investigating a degradation affecting Stacks mainnet. Users may experience elevated response times and intermittent 503 errors. Our team is actively investigating and will provide updates as more information becomes available.
We identified what appears to have been an upstream issue on the Stacks network side that caused a temporary halt in block production. Block production has since resumed, and we are no longer observing degradation at this time. We will continue investigating and will share more information as it becomes available.
This incident has been resolved. Block production and network performance have returned to normal levels across all services.