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.
A fix has been implemented and services have returned to normal. We are monitoring closely to ensure stability.
investigating
We are currently investigating degraded performance on Moca Testnet, with elevated latency and 503 errors. We will provide updates as more information becomes available.
Stacks Mainnet Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
Mainnet — REST APIMainnet — Websockets API
monitoring
A fix has been implemented and services have returned to normal. We are monitoring closely to ensure stability.
investigating
We are currently investigating degraded performance on Stacks Mainnet, with elevated latency and 503 errors. We will provide updates as more information becomes available.
The Foundation has confirmed that the chain was halted as a precautionary measure following the identification of a security issue affecting a common dependency. A patch is currently being prepared, and the chain will remain halted until it is deployed. We are closely monitoring the situation and will provide further updates as they become available.
We have investigated degradation and identified the cause on archive nodes related to an upstream issue.
Arbitrum Mainnet - Elevated 503 Errors
minorSource not attested
Last archived state: resolved
View archived record details
Mainnet Classic — JSON-RPC APIMainnet Classic — WebSocket API
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are investigating the degradation of Arbitrum Mainnet archive requests. Users may experience elevated latenc, 503 responses, and API errors during this time.
BNB Smart Chain Mainnet - Elevated API Errors (eth_getLogs)
We are investigating an elevated rate of 503 errors affecting eth_getLogs requests on BNB Smart Chain Mainnet. We will update this page as we acquire new information.
The degraded performance and 503 responses for Polygon Amoy have been resolved. We are monitoring for stability.
identified
The Polygon Foundation is currently running a stress test on the Amoy network. Users may experience elevated latencies, 503 responses and degraded performance during the duration of the stress test. Our team is working to resolve the degradation and we will follow up on this page with further updates.
investigating
The Polygon Foundation is running a stress test on the Amoy network at 15:00 UTC. Users may experience elevated latencies and degraded performance during the duration of the stress test. We will keep this page updated as the test progresses.
Performance on archive RPC methods has improved significantly. We are continuing to monitor the situation.
investigating
BNB Smart Chain mainnet is experiencing degraded performance on archive RPC methods. Some requests for historical data (trace, debug, and historical state lookups) may see increased latency or intermittent 503 errors. We are monitoring the situation and working on a resolution.
We identified an issue causing elevated error rates for Monad RPC requests. Our team has deployed a fix, and error rates have returned to normal.
We are continuing to monitor the service to ensure stability.
Hyperliquid EVM Testnet, Service Disruption
minorSource not attested
Last archived state: resolved
View archived record details
HyperEVM-Testnet - JSON-RPC API
investigating
We've identified an outage affecting Hyperliquid EVM Testnet. The root cause is an upstream stall on Hyperliquid's testnet network infrastructure, unrelated to QuickNode services. Users may experience failed or timed-out RPC requests until the upstream network resumes. We will continue monitoring and provide updates as they become available.
