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.
June 2026
Ethereum Hoodi Testnet - Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Historical blob data for Ethereum Hoodi nodes prior to slot 3,375,000 is now being served correctly, resolving the previous limitation. Full historical blob coverage has been restored. A fix has been implemented and we are monitoring the results to confirm full stability.
identified
The Quicknode team has identified the root cause of the recent degradation affecting the Ethereum Hoodi nodes.
Currently, the historical blob data for Ethereum Hoodi nodes is limited to slots >= 3,375,000. Requests for blob data prior to this slot may be temporarily unavailable.
We are working on restoring complete historical blob coverage and will keep this page updated as the work progresses.
investigating
The Quicknode team is investigating the degraded performance of Ethereum Hoodi Testnet. Some users may experience 503 errors at this time. We will update this page as we acquire new information.
Hedera Testnet - Elevated 503 Errors
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have identified the root cause of the elevated 503 errors on Hedera Testnet. The issue was caused by rate limiting (429s) on an upstream node. The affected node has been addressed and service has been restored. We are monitoring for continued stability.
investigating
We are investigating an issue with Hedera Testnet resulting in elevated 503 errors. Users may experience failed or interrupted requests. Our team is actively investigating and will provide updates as more information becomes available.
Base Mainnet Chain-Wide Stall
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Nodes have been restarted and the chain stall has been resolved. 503 errors are no longer observed. We are monitoring the service for continued stability as backfill requests normalize.
investigating
Base Mainnet is experiencing a chain-wide stall. The Quicknode team is investigating and will update this page as more information becomes available.
For reference, please see the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4
HyperEVM & Hypercore gRPC Maintenance / Upgrade
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently performing maintenance and an upgrade on HyperEVM and Hypercore gRPC. Users may experience disruptions during this time. We will provide updates as the work progresses.
B3 Mainnet Network Stalled at Block 60028954
minorSource not attested
Last archived state: resolved
View archived record details
investigating
B3 Mainnet appears to have stalled at block 60028954 due to a chain-wide stall on Base Mainnet, which B3 depends on. The Quicknode team is investigating and will update this page as more information becomes available.
For Base Mainnet status, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4
Base Mainnet Block Production Disruption
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 Base team is continuing to debug and have isolated a consensus problem that caused an invalid block to be sequenced. This prevented new blocks from being created following block 47806542. The Base team is working on a fix to resume block propagation to the network while further isolating the root cause of the problematic block.
For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4
identified
The Base Team has identified the issue with a problematic block interfering with subsequent block building. Their team is working on several threads to remediate. We will provide further updates as the situation develops.
For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4
investigating
Base Mainnet block production is currently unhealthy during the activation of the Beryl Upgrade.
For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4
The underlying issue has been identified, and a mitigation is in place.
Some nodes have recovered, and 503s have been mitigated.
Quicknode teams are continuing to work to recover full capacity and monitor performance to ensure stability.
investigating
The Quicknode team is investigating the degraded performance of Ethereum mainnet archived nodes.
Customers may experience increased error rates, including 503 responses, when querying archive data.
We will update this page as we acquire new information.
The 503 errors have now been resolved. We are monitoring for stability.
identified
The issue has been identified and a fix is being implemented.
investigating
The Quicknode team is investigating degraded performance on XRP Ledger Mainnet. Some users may be experiencing 503 errors. We will update this page as we acquire new information.
Quicknode Dashboard Outage
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The QuickNode Dashboard is back online and our services have recovered. We are monitoring the situation.
investigating
We are investigating an outage affecting the Quicknode Dashboard. We will update this page as we acquire new information.
Solana Devnet Halt
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The Solana Devnet restart has completed successfully. We are monitoring the network for stability and will provide further updates as needed.
investigating
The Foundation has intentionally halted Solana Devnet starting at approximately 16:00 UTC. We will update this page once the network resumes.
