QuickNode Status

Investigating: We are currently investigating an issue affecting Ault Mainnet in which the block height has stalled at 9,763,957. We are in active communication with the Foundation and are working toward restoring normal block progression. Further updates will be provided as the situation develops.

Resolved: This incident has been resolved.

Investigating: We are currently investigating an issue affecting the 0g Galileo Testnet in which the block height has stalled at 37,983,645. Further updates will be provided as the situation develops.

Resolved: The issue affecting HyperEVM Testnet has been resolved. 503 errors have cleared and all systems are operating normally. We will continue to monitor for any recurrence.

Monitoring: We are monitoring HyperEVM Testnet for continued stability and will provide further updates as needed.

Investigating: The QuickNode team is investigating degraded performance of HyperEVM Testnet - we will update this page as we acquire new information.

Resolved: The 503 errors affecting Injective Mainnet have been resolved. Additional regions were added to mitigate the issue and affected nodes have been brought back online. All systems are operating normally.

Monitoring: We have added additional regions to mitigate the 503 errors affecting Injective Mainnet. We are monitoring the service for stability and will provide further updates as needed.

Investigating: We are continuing to investigate this issue.

Investigating: We have temporarily added nearby region to mitigate the 503 issue. Some users may experience elevated latency at this time. Our team is actively working to resolve this and will provide updates as more information becomes available.

Investigating: We are investigating an issue with Injective Mainnet Tendermint JSON-RPC/REST API returning 503 errors. Our team is actively working to resolve this 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: The QuickNode team is investigating the degraded performance of Polygon Amoy Testnet. Users may experience intermittent 503 errors when making RPC requests. We will update this page as we acquire new information.

Resolved: This incident has been resolved.

Monitoring: The network has recovered and we are monitoring the results.

Investigating: We are currently investigating a block height stall affecting HyperEVM Testnet endpoints. We will provide updates as the investigation progresses.

Resolved: This incident has been resolved.

Monitoring: Our engineers identified and addressed an issue affecting block height on Polygon zkEVM Mainnet endpoints. All systems are operating normally and we will continue to monitor to ensure stability.

Investigating: We are currently investigating a block height stall affecting Polygon zkEVM Mainnet endpoints. We will provide updates as the investigation progresses.

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 our engineering team is applying a fix.

Investigating: The Quicknode team is investigating degraded performance on Polygon Amoy archive nodes — we will update this page as we acquire new information.

Resolved: This incident has been resolved.

Identified: We have identified the root cause of the degraded performance affecting Plasma Mainnet in the JFK region and node recovery is in progress.

As a temporary mitigation, traffic has been rerouted to nearby region while our engineers are working to recover the nodes. Some users may notice elevated latency at this time. We will continue to provide any new updates.

Identified: We have identified the root cause of the degraded performance affecting Plasma Mainnet in the JFK region. Our engineers are actively working to restore the affected nodes.

Investigating: The QuickNode team is investigating degraded performance of Plasma Mainnet nodes in the JFK region - we will update this page as we acquire new information.

Resolved: This incident has been resolved.

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.

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.

Affected components (:large_yellow_circle: Degraded performance) Mainnet Tendermint JSON-RPC/REST API • Mainnet Cosmos gRPC & REST API • Mainnet — Streams • Mainnet — Webhooks

Resolved: This incident has been resolved.

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.

Resolved: This incident has been resolved.

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.

Resolved: This incident has been resolved.

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.

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: We are currently investigating this issue.