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
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 17Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Solana Mainnet is currently undergoing a regenesis as part of the Alpenglow upgrade. We are monitoring the process and will provide updates as more information becomes available.
The Aptos Foundation is beginning a scheduled state reset on Aptos Testnet at 17 UTC today, per AIP-147.
The reset returns Testnet to a fresh genesis and clears all prior on-chain state. The Aptos Foundation expects the process to take a few hours, with up to 48 hours possible if complications arise.
What this means for you: Once resync completes, previously deployed contracts, test accounts, and balances on Aptos Testnet no longer exist. You'll need to redeploy contracts and recreate test state against the new genesis.
Injective Mainnet has resumed block production and our nodes are advancing past block 186,223,485 again. Requests are returning current data and the block height stall is no longer occurring. We will continue to monitor the network to confirm stability.
identified
The Injective Foundation has confirmed the issue and will be publishing an upgrade guide shortly. Injective Mainnet remains stalled at block 186,223,485. We will apply the upgrade to our nodes as soon as it is available and share another update once the rollout is underway.
investigating
We are currently investigating a block height stall on Injective Mainnet. Nodes stopped advancing at block 186,223,485, and requests may return stale data until block production resumes. Our team is actively working on this and we will provide an update as soon as we have more information.
X Layer Testnet – Network Stalled at Block 42837767
Service has been restored for X Layer Testnet, and requests are being served at the current chain head. Our engineers continue to work on the affected nodes and monitor stability.
identified
We have identified the cause of the X Layer Testnet network stall at block 42837767. Our engineers are currently upgrading our nodes to restore service. We will provide further updates as progress is made.
investigating
X Layer Testnet appears to have stalled at block 42837767 - The Quicknode team is investigating and will update with more information once it is available.
The World Chain team has confirmed the root cause of the intermittent 503 errors and is preparing a new node client release with a fix. We'll deploy it across our World Chain Mainnet nodes as soon as it's available. In the meantime, we're continuing to monitor closely, and some requests may still intermittently return 503 errors.
investigating
World Chain Mainnet requests may intermittently return 503 errors. We've identified the cause as an issue in the node client affecting some of our backend nodes, and we're working with the World Chain team to resolve it. We're monitoring closely and will share updates as they become available.
Blast Sepolia appears to have stalled at block 43,081,817. The Quicknode team is investigating and will update with more information once it is available.
We have identified the root cause of the degraded performance affecting Injective Mainnet. We will continue to monitor and provide updates as the situation improves.
investigating
The Quicknode team is investigating the degraded performance of Injective Mainnet - 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
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
Our team is investigating degradation on Sui Mainnet archive nodes.
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
minorSource 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
minorSource 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
minorSource 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
minorSource 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
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 Sui Mainnet archive nodes - we will update this page as we acquire new information.
BSC 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
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
minorSource 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
minorSource not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix is being implemented.
