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.
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.
