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
Billing Dashboard Metrics Delayed
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 investigating an issue causing billing metrics on the dashboard to appear delayed. We will provide updates as more information becomes available.
Stacks Testnet Network Stalled at Block 3,990,595
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 issue has been identified and a fix is being implemented.
investigating
The Stacks Testnet appears to have stalled at block 3,990,595 - The QuickNode team is investigating and will update with more information once it is available.
Injective Testnet Network Stalled at Block 126627399
minorSource not attested
Last archived state: resolved
View archived record details
investigating
The Injective Testnet network appears to have stalled at block 126627399 following a network upgrade — The Quicknode team is investigating and will update with more information once it is available.
Arbitrum Mainnet - Elevated 503 and API Errors
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 investigating an elevated rate of 503 and API errors affecting Arbitrum Mainnet. Our team has identified an issue with backend connectivity and is actively working to restore full service. We will provide updates as more information becomes available.
Polygon Amoy Testnet - Elevated 503 Errors During Load Testing
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are aware of elevated 503 errors on the Polygon Amoy Testnet. This is related to scheduled load and stress testing being conducted by the Polygon team between 19:00 – 20:00 UTC. We will update this page as more information becomes available.
Hedera Mainnet Network Stalled
minorSource not attested
Last archived state: resolved
View archived record details
identified
Hedera Mainnet appears to have stalled at block 95,291,380. This is due to on-going maintenance by the foundation. You can find more details from the Foundation's Status Page here:
https://status.hedera.com/incidents/6558j95l840y
investigating
Hedera Mainnet appears to have stalled at block 95,291,380. This is due to on-going maintenance by the foundation. You can find more details from the Foundation's Status Page here:
https://status.hedera.com/incidents/t9d33l15ygv0
Quicknode Dashboard - Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating the degraded performance of the Quicknode dashboard. Users may have issues accessing the Dashboard page at this time. We will update this page as we acquire more information.
HyperLiquid HyperEVM Testnet — 503 Errors
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on addressing the 503 errors affecting HyperLiquid HyperEVM Testnet. Nodes appeared to recover briefly but the issue had resumed. This issue originally began following a Hyperliquid Testnet hardfork at height 570610500. We will update this page as we acquire new information.
investigating
We are continuing to investigate 503 errors affecting HyperLiquid HyperEVM Testnet. Nodes appeared to recover briefly but the issue has resumed. Our team is actively investigating.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are investigating an issue with HyperLiquid HyperEVM Testnet where users may be experiencing 503 errors. Our team is actively working to resolve the issue and will provide updates as more information becomes available.
A fix has been implemented and we are monitoring the results.
investigating
We are investigating an issue affecting Polygon Amoy archive nodes. Users may experience 503 errors when making archive requests. Our team is actively working to restore full service and will provide updates as more information becomes available.
Elevated API Errors - 429 Rate Limit Responses
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're experiencing an elevated level of API errors and are currently investigating the issue. We will update this page as more information becomes available.
