QuickNode Status

Monitoring: Service has been restored for X Layer Testnet, and requests are being served at the current chain head. Our engineers continue to work on the affected nodes and monitor stability.

Identified: We have identified the cause of the X Layer Testnet network stall at block 42837767. Our engineers are currently upgrading our nodes to restore service. We will provide further updates as progress is made.

Investigating: X Layer Testnet appears to have stalled at block 42837767 - The Quicknode team is investigating and will update with more information once it is available.

Identified: The World Chain team has confirmed the root cause of the intermittent 503 errors and is preparing a new node client release with a fix. We'll deploy it across our World Chain Mainnet nodes as soon as it's available. In the meantime, we're continuing to monitor closely, and some requests may still intermittently return 503 errors.

Investigating: World Chain Mainnet requests may intermittently return 503 errors. We've identified the cause as an issue in the node client affecting some of our backend nodes, and we're working with the World Chain team to resolve it. We're monitoring closely and will share updates as they become available.

Resolved: Since September 23, many nodes that don't forward traffic have joined TON's public overlay, the peer network our nodes use to receive blocks and pass on transactions. Because our nodes were connected to some of these peers, block sync slowed and some transactions were not delivered.

For more detail, see the TON Foundation's announcement: https://t.me/tonstatus/244

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

Identified: We are continuing to work on a fix for this issue.

Identified: The issue has been identified and working with the Ton Foundation to implement fixes.

Investigating: The Quicknode team is investigating degraded performance of TON Mainnet - we will update this page as we acquire new information.

Resolved: This incident has been resolved.

Monitoring: We're working with the foundation to recover our nodes. A fix has been applied, and our nodes are now syncing back up. We're continuing to monitor closely to ensure stability.

Investigating: We're investigating an issue affecting Vana Moksha testnet endpoints. Our nodes have stopped syncing at block 9,268,235, so requests may return stale data. Our team is looking into the cause and we'll share an update as soon as we have more information.

Resolved: This incident has been resolved.

Investigating: Blast Sepolia appears to have stalled at block 43,081,817. The Quicknode team is investigating and will update with more information once it is available.

Resolved: This incident has been resolved.

Identified: We have identified the root cause of the degraded performance affecting Injective Mainnet. We will continue to monitor and provide updates as the situation improves.

Investigating: The Quicknode team is investigating the degraded performance of Injective Mainnet - 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 degraded performance on Solana Mainnet. Customers may experience increased latency and 503 errors. Streams and Webhooks are also affected and may see delayed deliveries.