Looking for an update now? Check the current status, or follow Quicknode for future changes.
17.2%of 58 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)
Aug 17Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
November 2026
Base Mainnet – Delayed transaction inclusion (upstream)
Base has implemented a fix for the delayed transaction inclusion and is monitoring the results. Inclusion times should be returning to normal. We'll keep monitoring and update this incident once Base confirms it's fully resolved.
investigating
We're aware of delayed transaction inclusion on Base Mainnet caused by an issue on the Base sequencer side. Transactions sent through Quicknode endpoints are being accepted and forwarded normally, but may take longer than usual to be included in a block.
Base is actively investigating: https://status.base.org/incidents/9jdt5jc1ylry
We'll update this incident as Base shares more information.
October 2026
XRPL EVM Mainnet Network Upgrade - Service Disruption
A fix has been deployed and XRPL EVM Mainnet endpoints are returning current blocks again as of 16:16 UTC. Between 13:59 and 16:16 UTC, requests may have returned stale block data following today's network upgrade.
investigating
We are investigating service disruptions affecting XRPL EVM Mainnet following a scheduled network upgrade. Users may experience intermittent errors and degraded performance. Our team is actively working to restore full service and will provide updates as more information becomes available.
Traffic has been restored and 503 errors are no longer observed. We will continue to monitor.
investigating
We are investigating an issue affecting Cosmos Mainnet endpoints. Users may be experiencing 503 errors when attempting to connect. Our team is actively working to restore service and will provide updates as more information becomes available.
Solana testnet has been halted by Anza as part of their planned stabilization process. Block production is paused network-wide until the cluster restarts. We're following Anza's restart process and will bring our nodes back online as soon as the network resumes. Solana mainnet and devnet are not affected.
Polkadot Asset Hub Mainnet Stuck at Block 22,295,913 in NRT Region.
Polkadot Asset Hub Mainnet appears to have stalled at block 22,295,913 in NRT region. The Quicknode team is investigating and will update with more information once it is available.
Robinhood Mainnet - Increased Latency on Select Methods
We have identified the root cause of the increased latency and timeouts affecting Robinhood Mainnet on select methods, including debug_traceBlockByNumber, eth_getBlockReceipts, eth_getLogs, and eth_getBlockByNumber. Our engineers have disabled the affected backends and are actively working to restore full service. Some stream-based services may continue to experience delays as they catch up. We will provide another update as the situation progresses.
investigating
The Quicknode team is investigating degraded performance of Robinhood Mainnet - we are seeing increased latency and timeouts on select RPC methods. We will update this page as we acquire new information.
Quicknode API Authentication Outage - Streams, KV Store, and Webhooks Affected
We are investigating an issue with our internal Quicknode API that is causing authentication failures for multiple accounts. Quicknode Streams, KV Store REST API, and Webhooks are currently affected. We will update this page as we acquire new information.
We're investigating an issue on Arbitrum Nova where no new blocks have been produced since block 85283638. We're in contact with the Arbitrum team to understand the cause, and we'll share an update as soon as we have more information.
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.
