QuickNode had 194 outages in the last 2 years totaling 180h 59m of downtime — averaging 8 incidents per month.
There were 194 QuickNode outages since March 6, 2026 totaling 180h 59m of downtime. Each is summarised below — incident details, duration, and resolution information.
The Quicknode team is investigating the degraded performance of Celo 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.
This incident has been resolved.
We are aware of elevated API errors and 503 errors on Polygon Amoy. The Polygon Foundation is currently conducting a network stress test which may be contributing to degraded performance. We will provide updates as this progresses.
The Polygon Amoy nodes are recovering following the network stress test. We are monitoring for stability.
We are aware of elevated API errors and 503 errors on Polygon Amoy. The Quicknode team is actively investigating. We will provide updates as this progresses.
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 Starknet Mainnet - Users may experience elevated 503 errors and increased latency. We will update this page as we acquire new information.
We have identified the issue affecting Starknet Mainnet performance. Our team is working closely with the Starknet Foundation to resolve the issue. We will continue to provide updates as the situation progresses.
A fix has been applied and we are monitoring the service for stability.
This incident has been resolved.
The HyperEVM Testnet (archive) appears to have stalled at block 55,231,856 - The QuickNode team is investigating and will update with more information once it is available.
The issue with the HyperEVM Testnet archive nodes stalling at block 55,231,856 has been resolved. A patch (nb-20260604) has been applied to the affected nodes and block height is advancing normally. We will continue to monitor for stability.
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.
The Berachain Bepolia network appears to have stalled at block 20,782,375. The QuickNode team is investigating and will update with more information once it is available.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
The QuickNode team is investigating instability on the Solana Testnet. 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.
The Robinhood Testnet appears to have stalled at block 63,024,491 - The QuickNode team is investigating and will update with more information once it is available.
The issue has been identified and a fix is being implemented.
Block height is progressing across the node infrastructure. We will notify you once the nodes are in sync with the broader network.
This incident has been resolved.
We are currently investigating this issue.
Our engineers are closely listening to updates from the foundation.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The Hemi Mainnet network appears to have stalled at block 4538215. This is a chain-wide issue and is not specific to QuickNode. Our team has raised this with the Hemi Foundation and will provide updates as more information becomes available.
The Hemi Foundation has identified a fix for the network stall at block 4538215. Our team is monitoring the situation as the fix is being applied. We will provide further updates as the network recovers.
The Hemi Mainnet network stall at block 4538215 has been resolved. The Hemi Foundation identified and deployed a fix, and the network is now advancing normally. All Hemi Mainnet services are fully operational.
Sui Mainnet stopped accepting user transactions due to an issue during the epoch change beginning at ~1:30PT. Validators are up and creating system transactions, but user transactions are not currently being accepted. This is a network-wide incident announced by the Sui Core Team. We are monitoring for any changes and our engineering team will promptly act on any updates.
Sui mainnet's network activity has resumed. https://x.com/SuiNetwork/status/2060549945594401126
This incident has been resolved.
The Sui Mainnet appears to have stalled at block 280,912,461 - The QuickNode team is investigating and will update with more information once it is available.
We are investigating 503 errors on Sui Mainnet following a network stall. The Sui Network team has issued an emergency release (mainnet-v1.72.4) and we are actively monitoring the situation. We will provide updates as more information becomes available.
The network stall has been addressed. We are monitoring Sui Mainnet for stability following the emergency release (mainnet-v1.72.4). We will continue to update this page as we confirm full recovery.
This incident has been resolved.
Flow Testnet is currently experiencing a network-wide stall at block height 112,873,473. We will provide updates as soon as they become available. Explorer: https://evm-testnet.flowscan.io/blocks
This incident has been resolved.
The Sui Mainnet network appears to have stalled at block 280,692,037. The QuickNode team is investigating and has raised the issue with the Sui Foundation. We will update this page as more information becomes available.
The Sui Foundation has acknowledged the issue and is actively working on a fix. We will continue to provide updates as more information becomes available.
Our engineers are updating nodes to the recent 1.72.3 release. Users may begin to see 503s mitigated and we will mark the incident as resolved once stability at tip has been confirmed.
This incident has been resolved.
We are investigating intermittent 503 errors affecting the Plasma Mainnet. 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 are continuing to investigate this issue.
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 Polygon Mainnet (Matic) archive nodes - we will update this page as we acquire new information.
We have brought additional nodes online and are monitoring the situation. Performance is improving, though we have not yet reached full capacity. We will continue to provide updates as the situation develops.
This incident has been resolved.
Unichain Sepolia archive and flashblocks endpoints are currently experiencing degraded performance. Users may experience 503s during this time. We are actively investigating the issue and will provide an update as soon as possible.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating intermittent 503 errors affecting the Abstract Testnet. Some customers may experience temporary request failures or degraded performance. Our team is actively working to mitigate the issue and will provide an update 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.
Blast Sepolia appears to have stalled. The Quicknode team is investigating and will update this page as more information becomes available.
This incident has been resolved.
We are investigating an issue causing billing metrics on the dashboard to appear delayed. We will provide updates as more information becomes available.
A fix has been implemented and we are monitoring the results.
The incident has been resolved. The Billing Dashboard Metrics are now operating normally. We will continue to monitor the situation and apologize for any inconvenience caused.
The Stacks Testnet appears to have stalled at block 3,990,595 - The QuickNode team is investigating and will update with more information once it is available.
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.
The Injective Testnet network appears to have stalled at block 126627399 following a network upgrade — The Quicknode team is investigating and will update with more information once it is available.
The Injective Testnet network has resumed producing blocks. Our nodes have reconnected to peers and are advancing normally. This incident has been resolved.
We are investigating an elevated rate of 503 errors affecting Arbitrum Mainnet. Our team has identified an issue with backend connectivity and is actively working to restore full service. We will provide updates as more information becomes available.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are aware of elevated 503 errors on the Polygon Amoy Testnet. This is related to scheduled load and stress testing being conducted by the Polygon team between 19:00 – 20:00 UTC. We will update this page as more information becomes available.
The elevated 503 errors on Polygon Amoy Testnet observed during the scheduled load testing window (19:00–20:00 UTC) have subsided. The incident has been resolved and all systems are operating normally.
The Hedera Mainnet appears to have stalled at block 95,291,380 - The QuickNode team is investigating and will update with more information once it is available.
Hedera Mainnet appears to have stalled at block 95,291,380. This is due to on-going maintenance by the foundation. You can find more details from the Foundation's Status Page here: https://status.hedera.com/incidents/6558j95l840y
This incident has been resolved.