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.
June 2026
0g Galileo Testnet — Block Height Stalled at 37,983,645
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating an issue affecting the 0g Galileo Testnet in which the block height has stalled at 37,983,645. Further updates will be provided as the situation develops.
Ault Mainnet — Block Height Stalled at 9,763,957
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating an issue affecting Ault Mainnet in which the block height has stalled at 9,763,957. We are in active communication with the Foundation and are working toward restoring normal block progression. Further updates will be provided as the situation develops.
HyperEVM Testnet Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are monitoring HyperEVM Testnet for continued stability and will provide further updates as needed.
investigating
The QuickNode team is investigating degraded performance of HyperEVM Testnet - we will update this page as we acquire new information.
Injective Mainnet Tendermint JSON-RPC/REST API – 503 Errors
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have added additional regions to mitigate the 503 errors affecting Injective Mainnet. We are monitoring the service for stability and will provide further updates as needed.
investigating
We are continuing to investigate this issue.
investigating
We have temporarily added nearby region to mitigate the 503 issue. Some users may experience elevated latency at this time. Our team is actively working to resolve this and will provide updates as more information becomes available.
investigating
We are investigating an issue with Injective Mainnet Tendermint JSON-RPC/REST API returning 503 errors. Our team is actively working to resolve this and will provide updates as more information becomes available.
HyperEVM Testnet — Block Height Stalled
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The network has recovered and we are monitoring the results.
investigating
We are currently investigating a block height stall affecting HyperEVM Testnet endpoints. We will provide updates as the investigation progresses.
Polygon Amoy Testnet — 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
The QuickNode team is investigating the degraded performance of Polygon Amoy Testnet. Users may experience intermittent 503 errors when making RPC requests. We will update this page as we acquire new information.
Polygon zkEVM Mainnet - Block Height Stalled
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our engineers identified and addressed an issue affecting block height on Polygon zkEVM Mainnet endpoints. All systems are operating normally and we will continue to monitor to ensure stability.
investigating
We are currently investigating a block height stall affecting Polygon zkEVM Mainnet endpoints. We will provide updates as the investigation progresses.
Polygon Amoy — Degraded Performance on Archive Nodes
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 our engineering team is applying a fix.
investigating
The Quicknode team is investigating degraded performance on Polygon Amoy archive nodes — we will update this page as we acquire new information.
Degraded Performance — Elevated Latency on Trace Methods
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
The Quicknode team is investigating degraded performance and elevated latency affecting debug_trace* and tracing requests across multiple networks in the FRA region. We will update this page as we acquire new information.
Plasma Mainnet Degraded Performance - JFK Region
minorSource not attested
Last archived state: resolved
View archived record details
identified
We have identified the root cause of the degraded performance affecting Plasma Mainnet in the JFK region and node recovery is in progress.
As a temporary mitigation, traffic has been rerouted to nearby region while our engineers are working to recover the nodes. Some users may notice elevated latency at this time. We will continue to provide any new updates.
identified
We have identified the root cause of the degraded performance affecting Plasma Mainnet in the JFK region. Our engineers are actively working to restore the affected nodes.
investigating
The QuickNode team is investigating degraded performance of Plasma Mainnet nodes in the JFK region - we will update this page as we acquire new information.
