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
Incident History
September 2026
Vana Moksha Testnet nodes stalled at block height 9,268,235
We're investigating an issue affecting Vana Moksha testnet endpoints. Our nodes have stopped syncing at block 9,268,235, so requests may return stale data. Our team is looking into the cause and we'll share an update as soon as we have more information.
Zora Mainnet appears to have stalled at block 51,972,862. The Quicknode team is investigating and will update with more information once it is available.
We have identified a network-routing issue affecting connectivity to our JFK edge location from certain network ranges. Our edge infrastructure remains healthy, but some customers may experience connection timeouts, interrupted responses, or elevated latency. We are actively working to resolve this and will provide further updates as they become available.
investigating
We are currently investigating an issue causing elevated latency and timeouts in the JFK region. We will update this page as we acquire further information.
Near Testnet — Block Height Stalled at 270,420,304
Block progression has resumed on Near Testnet. We are keeping a close eye on the network.
investigating
Near Testnet appears to have stalled at block 270,420,304 - The Quicknode team is investigating and will update with more information once it is available.
A fix has been implemented and we are monitoring the results.
investigating
The Quicknode team is investigating elevated 503 errors on World Chain Mainnet. Users may experience failed or degraded requests. We will update this page as we acquire new information.
A fix has been implemented and we are monitoring the results.
investigating
Celestia Mocha Testnet appears to have stalled at block 1,082,619. The Quicknode team is investigating and will update with more information once it is available.
The Polygon Amoy Testnet stress test has concluded. We are monitoring the network for stability and will continue to update this page as needed.
investigating
We're experiencing an elevated level of API errors on Polygon Amoy Testnet due to an ongoing stress test by the foundation. We will update this page with further details once they become available.
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.
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.
July 2026
Degraded Performance - Multiple Chains
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The elevated 503 errors have been mitigated and our team is actively monitoring for stability.
investigating
The Quicknode team is investigating degraded performance affecting multiple regions. At the moment, users may experience 503s and elevated errors on Solana archive requests. 503s affecting other chains have been mitigated and our team is actively working to restore full service.
investigating
The Quicknode team is investigating degraded performance affecting multiple chains - we will update this page as we acquire new information.
Flare Mainnet Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The 503 errors on Flare Mainnet have been resolved. We are monitoring the service for continued stability and will provide further updates as needed.
investigating
The Quicknode team is investigating the degraded performance of Flare Mainnet - we will update this page as we acquire new information.
JOC Mainnet - Elevated 503 Errors
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 elevated 503 errors on JOC Mainnet - we will update this page as we acquire new information.
Celo Mainnet 503 Errors
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We’re currently investigating intermittent `503` errors impacting Celo Mainnet requests.
Our team has identified the issue and is working to restore normal service as quickly as possible. We’ll continue monitoring and provide updates as soon as more information is available.
Thank you for your patience.
Mantle Mainnet Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue affecting Mantle Mainnet nodes in the IAD region has been resolved and services have returned to normal. We are continuing to monitor to ensure full stability.
investigating
We are investigating an issue causing 503 errors and degraded performance for Mantle Mainnet in the IAD region. Some requests may fail or experience elevated latency during this time. We will share updates as we have more information.
Arbitrum Sepolia - Elevated 503 Errors
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The elevated 503 errors on Arbitrum Sepolia have been resolved. We are monitoring the service for stability and will provide further updates if the issue recurs.
investigating
We're experiencing an elevated level of 503 errors and our team is currently investigating. We will update this page as more information becomes available.
QuickNode's services remain fully operational. We've confirmed no impact to QuickNode-hosted infrastructure from the AWS US-WEST-2 issue. We'll continue monitoring and will update this page once AWS resolves the underlying issue.
investigating
We are aware of an ongoing issue with AWS US-WEST-2 that may be causing degraded performance or connectivity issues for customers on multiple chains in the US-WEST region. Our team is actively monitoring the situation.
For reference, please see the AWS Service Health Dashboard for upstream status: https://health.aws.amazon.com/health/status
We will continue to provide updates as more information becomes available.
Solana Testnet — Block Height Stalled
minorSource not attested
Last archived state: resolved
View archived record details
identified
This is a chain wide stalled. We are following up with the Foundation channel and working toward restoring normal block progression. Further updates will be provided as the situation develops.
investigating
Solana Testnet appears to have stalled at block 423,534,724 - The Quicknode team is investigating and will update with more information once it is available.
Tron-Mainnet: Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our team has deployed a fix to address the increase in 503s associated with our US-East cluster. Customers should now be seeing typical responses from their Tron endpoints.
We are working to fully deploy our fix across the cluster and will continue to monitor the network.
Our team will provide an update upon confirmation of stability or if further action is required within 15 minutes.
identified
The issue has been identified and a fix is being implemented.
investigating
Our team is investigating the degraded performance of Tron-Mainnet. Some users may experience 503 errors at this time. We will update this page as we acquire new information.
Robinhood Mainnet - 503 Errors on Archive Requests
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are investigating an issue with Robinhood Mainnet where archive requests are returning 503 errors. Our team is actively looking into the cause and will provide updates as more information becomes available.
