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
We are investigating degraded performance affecting Moca Testnet. A short-notice network upgrade has caused our nodes to halt, resulting in 503 errors for endpoint requests. The Quicknode team is actively working to restore service. The chain itself is healthy and the public RPC is at tip. We will provide updates as more information becomes available.
Osmosis Mainnet – Network-Wide Stall at height 74,955,152
The Osmosis network stopped producing blocks at 22:57 UTC (block 74,955,152), affecting all providers, and Quicknode endpoints will resume serving new blocks as soon as the network restarts.
Polygon Amoy Testnet Network Stalled at Block 52,676,095
A fix has been applied and Quicknode Polygon Amoy Testnet endpoints are serving current block data again. We are monitoring to make sure the service stays stable.
identified
We have identified the cause of the issue affecting Polygon Amoy Testnet endpoints. Users may be experiencing stale block data and elevated 503 errors. The Amoy network itself is producing blocks normally. Our team is actively applying a fix and we will provide further updates as work progresses.
investigating
Polygon Amoy Testnet appears to have stalled at block 52,676,095 - The Quicknode team is investigating and will update with more information once it is available.
Injective Mainnet – Nodes Out of Sync Ahead of Scheduled Upgrade
A fix has been applied and Injective mainnet nodes are now catching up to the chain tip. Endpoints may still return slightly delayed data until they're fully synced. We're monitoring closely and will post an update once everything is back to normal.
investigating
Ahead of the scheduled Injective network upgrade (Nov 11, 12:00–14:00 UTC), our Injective mainnet nodes fell behind the chain tip and endpoints may return stale data. A fix is being applied and nodes will resync once it's in place. We'll post an update when service is fully restored.
Elysium Mainnet – Elevated Errors on eth_sendRawTransaction
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are investigating an issue affecting Elysium Mainnet where users are experiencing 429 and 403 errors on eth_sendRawTransaction requests. We will provide updates as we learn more.
We are investigating an issue affecting transaction and error log serving. Our engineers are actively working on a fix and will provide updates as more information becomes available.
Injective Mainnet – Scheduled Network Upgrade Test
Injective is conducting a scheduled mainnet upgrade test in coordination with its validators, as part of preparations for an upcoming network upgrade. During this window, block production on Injective mainnet may be paused or delayed, and requests to Injective endpoints may return stale data or errors.
This is a chain-wide event and is not related to Quicknode infrastructure. We are in contact with the Injective team and will post an update once normal network operations resume.
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are investigating elevated response times and timeouts affecting endpoints in the FRA region. Our team is actively investigating and will provide updates as more information becomes available.
Polygon Amoy Testnet - Degraded Performance During Network Stress Test
A network stress test is scheduled by the foundation at 19:00 UTC. Customers may experience degraded performance and elevated API errors on Polygon Amoy Testnet during this time. We will update this page as we acquire new information.
We have identified the root cause and are actively working on remediation across affected regions. Service restoration is underway and block height is progressing. We will continue to monitor and provide updates as the situation develops.
monitoring
Stacks Mainnet blocks are catching up. We are monitoring the network to confirm full recovery and stability.
identified
We have identified the root cause of the Stacks Mainnet stal Our engineers are actively working on restoring the connection and resuming block production. We will provide further updates as the situation progresses.
investigating
The Quicknode team is investigating an issue where Stacks Mainnet endpoints have stalled at block 9,395,980 since approximately 13:48 UTC. Users may be experiencing stale responses from Stacks Mainnet RPC endpoints. We will provide updates as more information becomes 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.
