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
A fix has been implemented and we are monitoring the results.
investigating
Vana Moksha appears to have stalled at block 9,170,953 — The Quicknode team is investigating and will update with more information once it is available.
Cosmos Mainnet full nodes are fully operational and serving the latest blocks. Our team is continuing to restore archive availability and we are monitoring our Cosmos nodes for stability. We will provide further updates as they become available.
identified
Cosmos Mainnet has resumed block production following the network-wide halt. Our infrastructure is completing synchronization before resuming full service. We do not have an ETA at this time and will update this page as soon as we have more information.
identified
We have identified the cause of the Cosmos Mainnet network stall at block 33,086,740. This is a chain-wide halt resulting from a network governance attack, as reported by the Cosmos Foundation. We are actively monitoring the situation and will provide further updates as more information becomes available.
investigating
Cosmos Mainnet appears to have stalled at block 33,086,740. This appears to be a chain-wide issue. The Quicknode team is investigating and will update this page as more information becomes available.
Arc Testnet - JSON RPC APIArc Testnet - Websocket API
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are continuing to investigate on the issue.
investigating
The Quicknode team is investigating the degraded performance of Arc Testnet. Users may experience 503 errors at this time. We will update this page as we acquire new information.
Cosmos Mainnet Network Stalled at Block 33,073,000
Cosmos Mainnet nodes have halted at block height 33,073,000 pending a required v28.2.0 upgrade. We have reached out to the Cosmos Foundation team for the release artifacts and are working to deploy the fix as soon as it is available. We will provide further updates as the situation develops.
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 Quicknode team is investigating degraded performance on Solana Mainnet. Users may be experiencing elevated 503 errors at this time. We will update this page as we acquire new information.
A fix has been implemented and we are monitoring the results.
investigating
The Quicknode team is investigating the degraded performance of Solana Mainnet. Users may experience 503s at this time. We will update this page as we acquire new 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
minorSource 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
minorSource 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.
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
minorSource 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
minorSource 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
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 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
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 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
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.