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
Polygon Amoy Testnet - Scheduled Network Stress Test
A network stress test is scheduled by the foundation at 18 UTC, and customers may experience degraded performance and elevated API errors during this time. We will update this page as we acquire new information.
Our nodes have recovered and are back at the chain tip. We are continuing to monitor the situation and will provide further updates as needed.
identified
The underlying issue has been identified. We are working with the Foundation to restore normal block progression. Further updates will be provided as the situation develops.
investigating
Cosmos Mainnet appears to have stalled at block 32,878,318 - The Quicknode team is investigating and will update with more information once it is available.
Solana Testnet appears to have stalled at block 440004508 — This is a chain wide stall. We are following up with the Foundation channel and working toward restoring normal block progression. Further updates will be provided as the situation develops.
The underlying issue has been identified. We are working with the Foundation to restore normal block progression. Further updates will be provided as the situation develops.
investigating
Gravity Mainnet appears to have stalled at block 41,384,106. The Quicknode team is investigating and will update with more information once it is available.
The upstream feed connection issues have stabilized and we are monitoring for stability.
identified
Users may continue to experience degraded performance and issues with transaction landing on Robinhood Mainnet. We are currently investigating connection issues regarding the sequencer feed and are closely listening to updates from the foundation.
investigating
The RobinHood foundation team has confirmed everything has returned back to normality. Our engineering team is actively monitoring performance.
investigating
The RobinHood foundation team has been notified and is actively investigating, this appears to be unrelated to Quicknode. We will provide further updates as more information becomes available.
investigating
We are investigating increased latency on RobinHood Mainnet. The Quicknode team has notified the foundation and will update this page as we acquire new information.
Our nodes are starting to recover following the patch deployment. We'll post another update once the system is fully operational.
identified
We have identified a possible root cause for the Injective Mainnet block height stall. A high priority patch is being deployed, and a network-wide upgrade may be in progress. We will continue to monitor and provide updates as more information becomes available.
investigating
Injective Mainnet appears to have stalled chain wide at block 181,027,000. The team is investigating and will update with more information once it is available.
This continues to be an upstream issue on the Gravity network, not related to our infrastructure. Block production has partially resumed, with some nodes still catching up. We'll keep watching closely and update as the situation develops.
identified
The underlying issue has been identified. We are working with the Foundation to restore normal block progression. Further updates will be provided as the situation develops.
investigating
Gravity Mainnet appears to have stalled at block 39,007,386 - The Quicknode team is investigating and will update with more information once it is available.
We are continuing to investigate a network-wide stall at block height 8,335,793. As this is affecting the entire network, we're currently waiting on guidance from the foundation before proceeding. We'll provide updates as soon as more information becomes available.
investigating
We are currently investigating a network wide stall at block height 8,335,793.
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.
