New Multi-region uptime checks and custom-domain status pages

Quicknode Outage History

Daily provider-status observations and published incident history for Quicknode.

Operational

Quicknode is operational. Verified . Official provider source.

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

Aug 18Nov 15

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 17 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

November 2026
Moca Testnet Degraded Performance – Short-Notice Network Upgrade
minor Observed active window 1h 37m

View incident details and source

Started:

Moca - Testnet
investigating
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
minor Observed active window 17h 5m

View incident details and source

Started:

Osmosis - Mainnet
investigating
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
minor Observed active window 2h 40m

View incident details and source

Started:

Polygon - Amoy Testnet
monitoring
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
minor Observed active window 1h 44m

View incident details and source

Started:

Injective - Mainnet
monitoring
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
minor Observed active window 34m

View incident details and source

Started:

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 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.
RPC Logs - Service Disruption
minor Observed active window 50m

View incident details and source

Started:

RPC Logs
investigating
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
minor Observed active window 13h 2m

View incident details and source

Started:

Injective - Mainnet
investigating
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.
Elevated Response Times and Timeouts - FRA Region
minor Observed active window 3h 8m

View incident details and source

Started:

Base - Mainnet
monitoring
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
minor Observed active window 2h 16m

View incident details and source

Started:

Polygon - Amoy Testnet
investigating
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.
Stacks Mainnet Stuck at Block 9,395,980
minor Observed active window 6h 11m

View incident details and source

Started:

Stacks - Mainnet
monitoring
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.

May 2026
Billing Dashboard Metrics Delayed
minor Source 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 causing billing metrics on the dashboard to appear delayed. We will provide updates as more information becomes available.
Stacks Testnet Network Stalled at Block 3,990,595
minor Source 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 Stacks Testnet appears to have stalled at block 3,990,595 - The QuickNode team is investigating and will update with more information once it is available.
Injective Testnet Network Stalled at Block 126627399
minor Source not attested
Last archived state: resolved
View archived record details
investigating
The Injective Testnet network appears to have stalled at block 126627399 following a network upgrade — The Quicknode team is investigating and will update with more information once it is available.
Arbitrum Mainnet - Elevated 503 and API Errors
minor Source 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 elevated rate of 503 and API errors affecting Arbitrum Mainnet. Our team has identified an issue with backend connectivity and is actively working to restore full service. We will provide updates as more information becomes available.
Polygon Amoy Testnet - Elevated 503 Errors During Load Testing
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We are aware of elevated 503 errors on the Polygon Amoy Testnet. This is related to scheduled load and stress testing being conducted by the Polygon team between 19:00 – 20:00 UTC. We will update this page as more information becomes available.
Hedera Mainnet Network Stalled
minor Source not attested
Last archived state: resolved
View archived record details
identified
Hedera Mainnet appears to have stalled at block 95,291,380. This is due to on-going maintenance by the foundation. You can find more details from the Foundation's Status Page here: https://status.hedera.com/incidents/6558j95l840y
investigating
Hedera Mainnet appears to have stalled at block 95,291,380. This is due to on-going maintenance by the foundation. You can find more details from the Foundation's Status Page here: https://status.hedera.com/incidents/t9d33l15ygv0
Quicknode Dashboard - Degraded Performance
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We are investigating the degraded performance of the Quicknode dashboard. Users may have issues accessing the Dashboard page at this time. We will update this page as we acquire more information.
HyperLiquid HyperEVM Testnet — 503 Errors
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on addressing the 503 errors affecting HyperLiquid HyperEVM Testnet. Nodes appeared to recover briefly but the issue had resumed. This issue originally began following a Hyperliquid Testnet hardfork at height 570610500. We will update this page as we acquire new information.
investigating
We are continuing to investigate 503 errors affecting HyperLiquid HyperEVM Testnet. Nodes appeared to recover briefly but the issue has resumed. Our team is actively investigating.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are investigating an issue with HyperLiquid HyperEVM Testnet where users may be experiencing 503 errors. Our team is actively working to resolve the issue and will provide updates as more information becomes available.
Polygon Amoy — Archive Requests Returning 503 Errors
minor Source 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 affecting Polygon Amoy archive nodes. Users may experience 503 errors when making archive requests. Our team is actively working to restore full service and will provide updates as more information becomes available.
Elevated API Errors - 429 Rate Limit Responses
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We're experiencing an elevated level of API errors and are currently investigating the issue. We will update this page as more information becomes available.