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.
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.
