Daily provider-status observations and published incident history for Quicknode.
Component incident
Quicknode has an active component incident; no global outage is indicated. Verified .
Official provider source.
Looking for an update now? Check the current status, or follow Quicknode for future changes.
13.8%of 29 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
15.4%
26
22
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
September 2026
Polygon Amoy Testnet - Scheduled Network Stress Test
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.
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.
identified
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.
investigating
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.
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.
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.
investigating
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 upstream feed connection issues have stabilized and we are monitoring for stability.
identified
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.
investigating
The RobinHood foundation team has confirmed everything has returned back to normality. Our engineering team is actively monitoring performance.
investigating
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.
investigating
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.
Our nodes are starting to recover following the patch deployment. We'll post another update once the system is fully operational.
identified
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.
investigating
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.
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.
identified
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.
investigating
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.
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.
investigating
We are currently investigating a network wide stall at block height 8,335,793.
Legacy Incident Archive
182 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
June 2026
Ethereum Hoodi Testnet - Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
identified
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.
investigating
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.
Hedera Testnet - Elevated 503 Errors
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
investigating
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.
Base Mainnet Chain-Wide Stall
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
investigating
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
HyperEVM & Hypercore gRPC Maintenance / Upgrade
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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.
B3 Mainnet Network Stalled at Block 60028954
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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
Base Mainnet Block Production Disruption
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
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
identified
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
investigating
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 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.
investigating
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 503 errors have now been resolved. We are monitoring for stability.
identified
The issue has been identified and a fix is being implemented.
investigating
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.
Quicknode Dashboard Outage
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The QuickNode Dashboard is back online and our services have recovered. We are monitoring the situation.
investigating
We are investigating an outage affecting the Quicknode Dashboard. We will update this page as we acquire new information.
Solana Devnet Halt
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The Solana Devnet restart has completed successfully. We are monitoring the network for stability and will provide further updates as needed.
investigating
The Foundation has intentionally halted Solana Devnet starting at approximately 16:00 UTC. We will update this page once the network resumes.
