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

Quicknode Outage History

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

Jul 3Sep 30

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

Incident History

August 2026
HyperLiquid Testnet - Degraded Performance
minor Observed active window 27m

View incident details and source

Started:

HyperEVM-Testnet - JSON-RPC API
investigating
We've identified an upstream issue causing timeouts and 503 errors on HyperLiquid Testnet. Updates to follow.
Stellar Mainnet JSON-RPC Degraded Performance
minor Observed active window 9h 51m

View incident details and source

Started:

Mainnet — JSON-RPC API
monitoring
A fix has been implemented and we are monitoring the results.
investigating
The Quicknode team is investigating the degraded performance of Stellar Mainnet JSON-RPC - 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.

August 2026
Sui Mainnet - Archive Degradation
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 a fix is being implemented.
investigating
Our team is investigating degradation on Sui Mainnet archive nodes.
Polygon Amoy Testnet , Elevated Network Load (Scheduled Stress Test)
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Our team is actively in discussion with the foundation to address the prolonged 503s on Polygon Amoy Testnet. You may continue to experience 503 errors and timeouts. We will provide updates as more information becomes available.
investigating
We're currently investigating prolonged 503s on Polygon Amoy Testnet following the conclusion of Polygon's scheduled stress test. You may continue to experience 503 errors and timeouts. We will provide updates as more information becomes available.
investigating
Polygon Labs is running load/stress testing on Amoy Testnet starting at 12:00 PM UTC today. You may experience higher-than-usual latency or elevated network load during this window. No action is needed on your end, we're monitoring and will update this page if anything requires attention.
Hyperliquid Testnet Network Stalled
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We've identified this as an upstream issue with Hyperliquid Testnet and are waiting on a fix from the Hyperliquid team. We'll update this page as soon as we have more information.
Zora Mainnet Network Stalled at Block 49527702
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Zora Mainnet is stalled at block 49,527,702. We are currently investigating and will update with more information once it is available.
NRT Region - Connectivity Issues Affecting Multiple Chains
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We are investigating connectivity issues affecting multiple chains in the NRT (Tokyo) region. Users in this region may experience elevated latency, timeouts, or failed requests. Traffic is being rerouted to alternate regions where possible. We will provide updates as more information becomes available.
Sui Mainnet - Archive Degraded Performance
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
The degraded performance has resolved and we are monitoring for stability.
investigating
The Quicknode team is investigating the degraded performance of Sui Mainnet archive nodes - we will update this page as we acquire new information.
July 2026
Sui Mainnet - Archive 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
The Quicknode team is investigating the degraded performance of Sui Mainnet archive nodes - we will update this page as we acquire new information.
BSC 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
The Quicknode team is investigating degraded performance on BSC Mainnet following a BSC archive snapshot release — we will update this page as we acquire new information.
World Chain Mainnet - Degraded Performance
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
The issue affecting World Chain Mainnet has been addressed and service has recovered. We are monitoring for continued stability and will provide further updates if needed.
investigating
The Quicknode team is investigating the degraded performance of World Chain Mainnet. We will update this page as we acquire new information. Users may experience 503s at this time.
Robinhood Testnet : Degraded Performance
minor Source not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.