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.
June 2026
Scheduled: Injective Mainnet - Upgrade injectived to v1.20.0
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We will be upgrading our Injective Mainnet nodes to injectived v1.20.0 starting at 09:00 UTC on June 4, 2025.
This is a mandatory mainnet hard fork upgrade. During this maintenance window, you may experience temporary disruptions to Injective Mainnet services, including JSON-RPC, gRPC, Streams, and Webhooks.
We expect the process to be completed within 24 hours. We will update this page as the upgrade progresses and mark the maintenance as complete once everything has been confirmed stable....
Degraded Performance - Celo Mainnet Archived Nodes
minorSource not attested
Last archived state: resolved
View archived record details
investigating
The Quicknode team is investigating the degraded performance of Celo 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.
Polygon Amoy — Elevated Errors During Foundation Stress Test
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 aware of elevated API errors and 503 errors on Polygon Amoy. The Quicknode team is actively investigating. We will provide updates as this progresses.
monitoring
The Polygon Amoy nodes are recovering following the network stress test. We are monitoring for stability.
investigating
We are aware of elevated API errors and 503 errors on Polygon Amoy. The Polygon Foundation is currently conducting a network stress test which may be contributing to degraded performance. We will provide updates as this progresses.
Starknet Mainnet — Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been applied and we are monitoring the service for stability.
identified
We have identified the issue affecting Starknet Mainnet performance. Our team is working closely with the Starknet Foundation to resolve the issue. We will continue to provide updates as the situation progresses.
investigating
The QuickNode team is investigating the degraded performance of Starknet Mainnet - Users may experience elevated 503 errors and increased latency. We will update this page as we acquire new information.
HyperEVM Testnet - Network Stalled at Block 55,231,856
minorSource not attested
Last archived state: resolved
View archived record details
investigating
The HyperEVM Testnet (archive) appears to have stalled at block 55,231,856 - The QuickNode team is investigating and will update with more information once it is available.
Polygon mainnet : Degraded performance on archive calls
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 issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Berachain Bepolia Network Stalled at Block 20,782,375
minorSource not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix is being implemented.
investigating
The Berachain Bepolia network appears to have stalled at block 20,782,375. The QuickNode team is investigating and will update with more information once it is available.
Solana Testnet - Degraded Performance
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 issue has been identified and a fix is being implemented.
investigating
The QuickNode team is investigating instability on the Solana Testnet. We will update this page as we acquire new information.
Robinhood Testnet Network Stalled at Block 63,024,491
minorSource not attested
Last archived state: resolved
View archived record details
identified
Block height is progressing across the node infrastructure. We will notify you once the nodes are in sync with the broader network.
identified
The issue has been identified and a fix is being implemented.
investigating
Robinhood Testnet appears to have stalled at block 63,024,491 - Our team is investigating and we are working with the foundation to resolve the stall. We will update with more information once it is available.
Polygon zkEVM mainnet : Block height stalled
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
Our engineers are closely listening to updates from the foundation.
As we progress toward a resolution, please expect the next update on or before 10:00 UTC.
