QuickNode Status

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.

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.

Resolved: The issue affecting Stellar Mainnet and Testnet during the v29 upgrade has been resolved. All systems are operating normally.

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

Resolved: This incident has been resolved.

Investigating: Zora Mainnet appears to have stalled at block 51,972,862. The Quicknode team is investigating and will update with more information once it is available.

Resolved: This incident has been resolved.

Monitoring: Block progression has resumed on Near Testnet. We are keeping a close eye on the network.

Investigating: Near Testnet appears to have stalled at block 270,420,304 - 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: The Quicknode team is investigating elevated 503 errors on World Chain Mainnet. Users may experience failed or degraded requests. 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.

Investigating: The Quicknode team is investigating the degraded performance of Fuel 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.

Investigating: Celestia Mocha Testnet appears to have stalled at block 1,082,619. The Quicknode team is investigating and will update with more information once it is available.

Resolved: This incident has been resolved.

Monitoring: The Polygon Amoy Testnet stress test has concluded. We are monitoring the network for stability and will continue to update this page as needed.

Investigating: We're experiencing an elevated level of API errors on Polygon Amoy Testnet due to an ongoing stress test by the foundation. We will update this page with further details once they become available.

Resolved: This incident has been resolved.

Monitoring: Cosmos Mainnet full nodes are fully operational and serving the latest blocks. Our team is continuing to restore archive availability and we are monitoring our Cosmos nodes for stability. We will provide further updates as they become available.

Identified: Cosmos Mainnet has resumed block production following the network-wide halt. Our infrastructure is completing synchronization before resuming full service. We do not have an ETA at this time and will update this page as soon as we have more information.

Identified: We have identified the cause of the Cosmos Mainnet network stall at block 33,086,740. This is a chain-wide halt resulting from a network governance attack, as reported by the Cosmos Foundation. We are actively monitoring the situation and will provide further updates as more information becomes available.

Investigating: Cosmos Mainnet appears to have stalled at block 33,086,740. This appears to be a chain-wide issue. The Quicknode team is investigating and will update this page as more information becomes available.