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
Ethereum Hoodi Testnet - Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Historical blob data for Ethereum Hoodi nodes prior to slot 3,375,000 is now being served correctly, resolving the previous limitation. Full historical blob coverage has been restored. A fix has been implemented and we are monitoring the results to confirm full stability.
identified
The Quicknode team has identified the root cause of the recent degradation affecting the Ethereum Hoodi nodes.
Currently, the historical blob data for Ethereum Hoodi nodes is limited to slots >= 3,375,000. Requests for blob data prior to this slot may be temporarily unavailable.
We are working on restoring complete historical blob coverage and will keep this page updated as the work progresses.
investigating
The Quicknode team is investigating the degraded performance of Ethereum Hoodi Testnet. Some users may experience 503 errors at this time. We will update this page as we acquire new information.
Hedera Testnet - Elevated 503 Errors
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have identified the root cause of the elevated 503 errors on Hedera Testnet. The issue was caused by rate limiting (429s) on an upstream node. The affected node has been addressed and service has been restored. We are monitoring for continued stability.
investigating
We are investigating an issue with Hedera Testnet resulting in elevated 503 errors. Users may experience failed or interrupted requests. Our team is actively investigating and will provide updates as more information becomes available.
Base Mainnet Chain-Wide Stall
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Nodes have been restarted and the chain stall has been resolved. 503 errors are no longer observed. We are monitoring the service for continued stability as backfill requests normalize.
investigating
Base Mainnet is experiencing a chain-wide stall. The Quicknode team is investigating and will update this page as more information becomes available.
For reference, please see the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4
HyperEVM & Hypercore gRPC Maintenance / Upgrade
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently performing maintenance and an upgrade on HyperEVM and Hypercore gRPC. Users may experience disruptions during this time. We will provide updates as the work progresses.
B3 Mainnet Network Stalled at Block 60028954
minorSource not attested
Last archived state: resolved
View archived record details
investigating
B3 Mainnet appears to have stalled at block 60028954 due to a chain-wide stall on Base Mainnet, which B3 depends on. The Quicknode team is investigating and will update this page as more information becomes available.
For Base Mainnet status, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4
Base Mainnet Block Production Disruption
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 Base team is continuing to debug and have isolated a consensus problem that caused an invalid block to be sequenced. This prevented new blocks from being created following block 47806542. The Base team is working on a fix to resume block propagation to the network while further isolating the root cause of the problematic block.
For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4
identified
The Base Team has identified the issue with a problematic block interfering with subsequent block building. Their team is working on several threads to remediate. We will provide further updates as the situation develops.
For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4
investigating
Base Mainnet block production is currently unhealthy during the activation of the Beryl Upgrade.
For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4
The underlying issue has been identified, and a mitigation is in place.
Some nodes have recovered, and 503s have been mitigated.
Quicknode teams are continuing to work to recover full capacity and monitor performance to ensure stability.
investigating
The Quicknode team is investigating the degraded performance of Ethereum 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.
The 503 errors have now been resolved. We are monitoring for stability.
identified
The issue has been identified and a fix is being implemented.
investigating
The Quicknode team is investigating degraded performance on XRP Ledger Mainnet. Some users may be experiencing 503 errors. We will update this page as we acquire new information.
Quicknode Dashboard Outage
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The QuickNode Dashboard is back online and our services have recovered. We are monitoring the situation.
investigating
We are investigating an outage affecting the Quicknode Dashboard. We will update this page as we acquire new information.
Solana Devnet Halt
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The Solana Devnet restart has completed successfully. We are monitoring the network for stability and will provide further updates as needed.
investigating
The Foundation has intentionally halted Solana Devnet starting at approximately 16:00 UTC. We will update this page once the network resumes.
