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
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.
We are currently investigating degraded performance on zkSync Era Testnet, with timeouts and 503 errors. We will provide updates as more information becomes available.
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.
A fix has been implemented and services have returned to normal. We are monitoring closely to ensure stability.
investigating
We are currently investigating degraded performance on Moca Testnet, with elevated latency and 503 errors. We will provide updates as more information becomes available.
Stacks Mainnet Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
Mainnet — REST APIMainnet — Websockets API
monitoring
A fix has been implemented and services have returned to normal. We are monitoring closely to ensure stability.
investigating
We are currently investigating degraded performance on Stacks Mainnet, with elevated latency and 503 errors. We will provide updates as more information becomes available.
The Foundation has confirmed that the chain was halted as a precautionary measure following the identification of a security issue affecting a common dependency. A patch is currently being prepared, and the chain will remain halted until it is deployed. We are closely monitoring the situation and will provide further updates as they become available.
We have investigated degradation and identified the cause on archive nodes related to an upstream issue.
Arbitrum Mainnet - Elevated 503 Errors
minorSource not attested
Last archived state: resolved
View archived record details
Mainnet Classic — JSON-RPC APIMainnet Classic — WebSocket API
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are investigating the degradation of Arbitrum Mainnet archive requests. Users may experience elevated latenc, 503 responses, and API errors during this time.
BNB Smart Chain Mainnet - Elevated API Errors (eth_getLogs)
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.
The degraded performance and 503 responses for Polygon Amoy have been resolved. We are monitoring for stability.
identified
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.
investigating
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.
Performance on archive RPC methods has improved significantly. We are continuing to monitor the situation.
investigating
BNB Smart Chain 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.
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.
Hyperliquid EVM Testnet, Service Disruption
minorSource not attested
Last archived state: resolved
View archived record details
HyperEVM-Testnet - JSON-RPC API
investigating
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.
