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.
May 2026
Billing Dashboard Metrics Delayed
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are investigating an issue causing billing metrics on the dashboard to appear delayed. We will provide updates as more information becomes available.
Stacks Testnet Network Stalled at Block 3,990,595
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 issue has been identified and a fix is being implemented.
investigating
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.
Injective Testnet Network Stalled at Block 126627399
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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.
Arbitrum Mainnet - Elevated 503 and API Errors
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are investigating an elevated rate of 503 and API 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.
Polygon Amoy Testnet - Elevated 503 Errors During Load Testing
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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.
Hedera Mainnet Network Stalled
minorSource not attested
Last archived state: resolved
View archived record details
identified
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
investigating
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/t9d33l15ygv0
Quicknode Dashboard - Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating the degraded performance of the Quicknode dashboard. Users may have issues accessing the Dashboard page at this time. We will update this page as we acquire more information.
HyperLiquid HyperEVM Testnet — 503 Errors
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on addressing the 503 errors affecting HyperLiquid HyperEVM Testnet. Nodes appeared to recover briefly but the issue had resumed. This issue originally began following a Hyperliquid Testnet hardfork at height 570610500. We will update this page as we acquire new information.
investigating
We are continuing to investigate 503 errors affecting HyperLiquid HyperEVM Testnet. Nodes appeared to recover briefly but the issue has resumed. Our team is actively investigating.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are investigating an issue with HyperLiquid HyperEVM Testnet where users may be experiencing 503 errors. Our team is actively working to resolve the issue and will provide updates as more information becomes available.
A fix has been implemented and we are monitoring the results.
investigating
We are investigating an issue affecting Polygon Amoy archive nodes. Users may experience 503 errors when making archive requests. Our team is actively working to restore full service and will provide updates as more information becomes available.
Elevated API Errors - 429 Rate Limit Responses
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We're experiencing an elevated level of API errors and are currently investigating the issue. We will update this page as more information becomes available.
