QuickNode Status

Resolved: This incident has been resolved.

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.

Resolved: The Injective Testnet network has resumed producing blocks. Our nodes have reconnected to peers and are advancing normally. This incident has been resolved.

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.

Resolved: This incident has been resolved.

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.

Resolved: The elevated 503 errors on Polygon Amoy Testnet observed during the scheduled load testing window (19:00–20:00 UTC) have subsided. The incident has been resolved and all systems are operating normally.

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.

Resolved: This incident has been resolved.

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

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

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.

Resolved: This incident has been resolved.

Identified: The Quicknode team is continuing to address the degraded performance of Lisk Mainnet and we are working with the foundation to resolve the issue. Customers may continue to experience stale data on block-dependent calls (e.g. eth_blockNumber) while archive nodes catch up to chain head. We will update this page as we acquire new information.

Investigating: The QuickNode team is investigating degraded performance of Lisk Mainnet - customers may experience stale data on block-dependent calls (e.g. eth_blockNumber) while archive nodes catch up to chain head. We will update this page as we acquire new information.

Resolved: The issue causing 503 errors on HyperLiquid HyperEVM Testnet has been resolved. All systems are operating normally.

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.

Resolved: This incident has been resolved.

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.

Resolved: Service has stabilized, and 503s are back down significantly.

We are still coordinating with the TON Foundation on an upstream release that provides a permanent fix, and we will roll it out once available. We will continue to monitor closely and will post a new update if impact returns or when the Foundation release is deployed.

Monitoring: Nodes have stabilized and 503s are down significantly. We're working with the foundation on a permanent fix.

Investigating: The QuickNode team is investigating the degraded performance of TON Mainnet. We will update this page as we acquire new information. Users may experience 503s at this time.

Resolved: This incident has been resolved.

Investigating: The QuickNode team is investigating degraded performance of Blast Mainnet in the SIN (Singapore) region - we will update this page as we acquire new information.