New Multi-region uptime checks and custom-domain status pages

Quicknode Outage History

Daily provider-status observations and published incident history for Quicknode.

Operational

Quicknode is operational. Verified . Official provider source.

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

Aug 18Nov 15

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 17 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

November 2026
Base Mainnet – Delayed transaction inclusion (upstream)
minor Observed active window 4h 6m

View incident details and source

Started:

Base - Mainnet
monitoring
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
minor Observed active window 36m

View incident details and source

Started:

monitoring
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.
Cosmos Mainnet Outage - 503 Errors
minor Observed active window 3h 29m

View incident details and source

Started:

Cosmos - Mainnet
monitoring
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.
Aptos Testnet - Chain Stall at Block 16,617,441
minor Observed active window 6h 0m

View incident details and source

Started:

Aptos - Testnet
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
The Quicknode team is currently investigating a network-wide stall at block height 16,617,441.
Solana Testnet: Planned network halt
minor Observed active window 12h 22m

View incident details and source

Started:

Solana - Testnet
investigating
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.
minor Observed active window 32m

View incident details and source

Started:

investigating
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
minor Observed active window 6h 1m

View incident details and source

Started:

Robinhood - Mainnet
identified
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
critical Observed active window 51m

View incident details and source

Started:

Quicknode Streams Quicknode Webhooks
investigating
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.
Morph mainnet : Degraded performance in EU region
major Observed active window 13h 29m

View incident details and source

Started:

Morph - Mainnet
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
We are currently investigating this issue.
Arbitrum Nova – Block production halted
minor Observed active window 9m

View incident details and source

Started:

Arbitrum Nova - Mainnet
investigating
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.

May 2026
Degraded Performance - TON Mainnet
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
Nodes have stabilized and 503s are down significantly. We're working with the foundation on a permanent fix.
investigating
The QuickNode team is investigating the degraded performance of TON Mainnet. We will update this page as we acquire new information. Users may experience 503s at this time.
Billing Dashboard Data Delay
minor Source not attested
Last archived state: resolved
View archived record details
identified
We’re currently experiencing a delay in billing-related data appearing in the dashboard. Charges and usage may take longer than usual to reflect, but billing is still processing normally in the background. We’re working to restore normal update times and will post an update once data is fully caught up.
Quicknode dashboard : Investigating Dashboard Loading Issues
minor Source 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 currently investigating an issue where some users may experience longer load times on the dashboard, and KV API requests may return 503 errors.
Base Mainnet & Base Sepolia - Degrade Performance
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We are aware of a node peering stability issue affecting Base Mainnet and Testnet. The Base Foundation has published an incident report attributing this to upcoming changes to p2p peer discovery. Quicknode Base Infrastructure may be impacted and users could see intermittent 503 errors or request timeouts during this period. There is no action required on your end. Our team is monitoring the situation closely and will provide updates here as more information becomes available.
Base Sepolia: Degraded Performance
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating an issue affecting archive calls on Base Sepolia. We will provide updates as they become available.
Worldchain Mainnet: Degraded Performance
minor Source 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 currently investigating degraded performance on our Worldchain Mainnet nodes. Users may experience 503s and null responses. We will provide updates as they become available.
Quicknode Key-Value Store: Degraded Performance
minor Source 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 currently experiencing a service disruption affecting the Quicknode Key-Value Store API. Customers may be unable to access this service. Our team is actively looking into the issue and will provide updates as soon as possible.
Quicknode Streams: Degraded Performance
minor Source 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 currently investigating this issue.
Quicknode dashboard : Investigating Dashboard Loading Issues
minor Source 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 our engineers are actively working on a resolution. Please expect the next update by 11:00 AM UTC.
investigating
We are currently investigating this issue.
Quicknode streams API, Key Value storage API : Degraded performance
minor Source 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 our engineers are actively working on a resolution. Please expect the next update by 11:00 AM UTC.
investigating
We are currently investigating this issue.