QuickNode had 197 outages in the last 2 years totaling 164h 28m of downtime — averaging 8.1 incidents per month.
There were 197 QuickNode outages since March 6, 2026 totaling 164h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue. Users requesting data beyond this block will experience 503s. The Quicknode team is investigating and will update with more information once it is available.
This incident has been resolved.
Polygon Amoy archive nodes are currently stalled at block 36,805,071. Requests for historical data following this block will result in 503s. Users querying tip data are not affected. Our team is actively investigating the cause with priority and we'll provide updates as new information becomes available.
This incident has been resolved.
The Base Sepolia Network appears to have stalled at block 40297498 - This is not limited to Quicknode and is a network wide stall. The Quicknode team is investigating and will update with more information once it is available. You can follow the official Base Status Page for further information: https://status.base.org/incidents/l6d3mnl0c9hs
This incident has been resolved.
We are currently experiencing service disruptions affecting multiple Quicknode platform services. Affected services include Dashboard, Streams, Webhooks, and KV REST APIs. Customers may be unable to access these services. Quicknode RPC endpoints remain fully operational. Only platform management services are affected. Our engineering team is actively investigating and working to restore these services. We will provide the next update by 2PM UTC or sooner.
Update: The issue affecting Dashboard, Streams, Webhooks, and KV REST APIs appears to be resolved. Services have been restored and are operational. Our DevEx team is actively monitoring to ensure full service stability. We will provide a final update once monitoring is complete.
The service disruption affecting Dashboard, Streams, Webhooks, and KV REST APIs has been resolved. All platform services are fully operational. We apologize for any inconvenience this may have caused and thank you for your patience.
Solana Devnet is currently stalled at block 455,406,479. This has been confirmed as a network-wide issue and is expected, according to the foundation team. QuickNode is awaiting further guidance and will provide updates as more information becomes available.
The QuickNode team is currently following the foundation team's guidance to recover the nodes and will provide further updates as more information becomes available.
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.
We are currently investigating an issue intermittently affecting the QuickNode Dashboard, Streams, and KV Store REST API. Some customers may experience degraded performance or errors. Our team is actively working to identify the root cause. We will provide updates as more information becomes available.
The issue intermittently affecting the QuickNode Dashboard, Streams, and KV Store REST API has been resolved. Services have recovered and are operating normally. Our team will continue to monitor the situation closely to ensure stability is maintained. We apologize for any inconvenience this may have caused.
This incident has been resolved.
The QuickNode team is investigating the degraded performance of Polygon Amoy archive and debug requests - we will update this page as we acquire new information. Users may experience 503s during this time for archive and debug RPC calls.
The Quicknode team has identified the cause of the degraded performance of Polygon Amoy archive and debug requests and our engineers are applying a fix. Users may still experience 503s during this time for archive and debug RPC calls.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Fuel Sepolia network appears to have stalled at block 59,643,457. The QuickNode team is investigating and will update with more information once it is available.
This incident has been resolved.
We are currently experiencing a service disruption on Morph Mainnet. Block production has halted due to an issue with the sequencer. This incident has been acknowledged by the Morph Foundation, who are actively investigating. We will provide updates as the situation develops.
Block production on Morph Mainnet has resumed and nodes are currently catching up and syncing. The Morph Foundation has acknowledged an issue with the sequencer as the root cause of the halt. We are continuing to monitor until full sync is confirmed.
Block production on Morph Mainnet has fully resumed and nodes are synced. The issue was caused by a sequencer problem acknowledged by the Morph Foundation, who have since resolved it on their end. We will continue to monitor to confirm stability.
We are currently investigating this issue.
This is a chain-level incident. As our engineers are actively monitoring updates from the Morph Foundation, please find the next update by 8 AM UTC.
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 Hedera Mainnet - we will update this page as we acquire new information. Users may experience API errors and 503 responses during this time.
This incident has been resolved.
The HyperCore events WebSocket stream experienced intermittent interruptions due to unusually large hourly funding rate blocks, which caused the stream to stall for some consumers. Engineering deployed a fix to handle these large blocks more safely, and the stream is now stable.
B3 Sepolia is experiencing a network-wide stall at block height 61,001,532. This is not isolated to Quicknode. We will provide the next update as soon as new information becomes available. Explorer: https://sepolia.explorer.b3.fun/
This incident has been resolved.
Sui Testnet is experiencing a network-wide stall at block height 321,596,099. This is not isolated to Quicknode. We will provide the next update as soon as new information becomes available. Explorer: https://testnet.suivision.xyz/
Our engineers are closely listening to updates from the Sui foundation.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The 0G Galileo testnet network appears to have stalled at block 25181554 - The stall is network wide and is not isolated to Quicknode. Our team has reached out to the foundation for further information. This page will be updated as we receive further information.
The 0G Galileo testnet network stall has been resolved, and the chain is progressing normally again. The issue was network wide and not isolated to QuickNode. We will continue monitoring for stability.
On Cosmos, customers may experience degraded performance for both HTTP and WebSocket traffic, including increased error rates (ex, 503 responses), elevated latency, and intermittent request failures. To resolve this, we are performing an upgrade and working to restore normal service as quickly as possible. We will share the next update as soon as we confirm the cause and mitigation steps, and we’ll continue to provide updates as more information becomes available.
We have implemented a fix, and service is recovering. We are actively monitoring the situation and will share additional updates as we confirm continued stability
This incident has been resolved.
We are aware of a block height stall affecting Fluent Testnet. Requests may return stale or inconsistent data during this time. We are coordinating closely with the Fluent chain team to identify and resolve the underlying cause. Our engineering team is actively working to restore normal service. Recommended action: No action is required on your end. Requests to Fluent Testnet may return outdated block data until the issue is resolved. We will provide a further update within the next 60 minutes.
The block height stall on Fluent Testnet has been addressed and all nodes are now synced and producing blocks normally. We are monitoring to ensure stability. We will provide a final update shortly to confirm full resolution.
This incident has been resolved.
We are currently experiencing service disruptions on Ink Sepolia testnet due to backend node degradation. Multiple backend nodes are failing health checks and not providing block data within expected timeframes. Ink Sepolia testnet RPC endpoints are currently affected. Customers may experience request failures, timeouts, or inconsistent block data until our backend nodes are restored. Our engineering team is actively investigating and working to resolve the backend pool issues. We will provide the next update by 2:30pm or sooner.
The issue affecting Ink Sepolia testnet has been resolved. Backend nodes have returned to normal operation and are now passing health checks. All Ink Sepolia testnet RPC endpoints are now fully operational. If you continue to experience any issues, please contact our support team.
We are investigating an issue impacting Gnosis (GNO) Mainnet Archive RPC where some requests are returning elevated HTTP 503 errors and may experience degraded availability. The team is actively working to identify the cause and restore normal service. We will follow up with an update by 20:00 UTC.
Our team has identified the issue with the affected nodes and are currently working on recovery. We will follow up with an update by 20:30 UTC.
A fix has been implemented and we are monitoring the results. We will follow up with an update by 21:00 UTC.
This incident has been resolved.
We are currently investigating a block production stall on the Bitcoin Cash (BCH) mainnet. The network appears to have stopped producing new blocks, which is also confirmed by public explorers showing the same block height. We are monitoring the situation closely and will provide updates as they become available.
Bitcoin Cash (BCH) mainnet block production has resumed and the network is producing new blocks again. We will continue monitoring for stability.
BCH Testnet is experiencing slow block production. We are investigating and will update with more information once it is available.
This incident has been resolved.
We are currently experiencing service disruptions on Sonic mainnet due to an upstream network-wide block stall. The network is stalled at block 66,026,794. This is a network-wide issue and is not isolated to Quicknode. The Sonic Foundation has been notified. All Sonic mainnet RPC endpoints are currently affected by the upstream network stall. New blocks are not being produced until the network resumes. We will provide the next update by 11:30am or sooner as information becomes available.
We are currently experiencing service disruptions on Sonic mainnet RPC endpoints due to validator syncing issues. The Sonic team has clarified this is NOT a network stall. The Sonic network remains fully operational, continues to produce blocks, and transactions are processing as expected. The Sonic team has identified the issue and provided a fix requiring client upgrades to v2.1.6 and database resyncing. Our engineering team is actively applying this update to restore service. Sonic mainnet RPC endpoints are currently affected. Customers may experience request failures or timeouts until our nodes complete the upgrade and resync process. The native Sonic explorer remains operational: https://explorer.soniclabs.com/blocks For official updates from Sonic: https://x.com/SonicLabs/status/2036763965041021347 We will provide the next update by 3PM or sooner.
Our engineering team is actively applying the Sonic client upgrades to v2.1.6 and database resyncing to restore service. Sonic Mainnet RPC endpoints are currently affected. Customers may experience request failures or timeouts until our nodes complete the upgrade and resync process. The native Sonic explorer remains operational: https://explorer.soniclabs.com/blocks For official updates from Sonic: https://x.com/SonicLabs/status/2036763965041021347
The issue affecting Sonic mainnet RPC endpoints has been resolved. Our engineering team successfully completed the Sonic client upgrades to v2.1.6 and database resyncing at 00:00 UTC on 27 March. All Sonic mainnet RPC endpoints are now fully operational. If you continue to experience any issues, please contact our support team. https://portal.usepylon.com/quicknode/forms/submit-a-support-ticket
The Quicknode team is investigating the degraded performance of Tron Mainnet - we will update this page as we acquire new information. Users may experience 503 errors during this time.
We are continuing to investigate degraded performance on Tron Mainnet. At this time, we are seeing elevated 503 errors primarily in the EU region. Traffic is being shifted away from impacted capacity while we work to restore full service. We will share another update by 18:10 UTC (or sooner if there is a significant change).
Our team has deployed a fix to mitigate the 503 errors. Users should now see successful responses when making requests. We are monitoring for stability.
This incident has been resolved.
We are investigating intermittent 503 errors affecting the Avalanche Fuji Testnet. Some customers may experience temporary request failures or degraded performance. Our team is actively working to mitigate the issue and restore full service stability. We will provide an update as more information becomes available.
We have identified this as an upstream network-wide issue affecting Avalanche Fuji Testnet infrastructure. The C-chain (EVM) is currently affected and blocks have stopped being produced. This is a network-wide issue and is not isolated to Quicknode. The Avalanche team has been notified and is investigating. All Avalanche Fuji Testnet RPC endpoints are currently affected. Customers may experience 503 errors, request failures, or timeouts until the network stabilizes. We will provide the next update by 11am or sooner as information becomes available.
The upstream network issue has stabilized and blocks are now being produced. Our team is actively monitoring to ensure full service restoration. Customers should see improved performance, though some intermittent issues may still occur until all nodes are fully synchronized.
This incident has been resolved.
We have detected an issue on the BSC-Testnet Archive, due to which you would be seeing 503 errors. Our team is currently looking into it and will fix the situation as soon as possible.
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.