QuickNode Status

Resolved: This incident has been resolved.

Investigating: Solana Mainnet is currently undergoing a regenesis as part of the Alpenglow upgrade. We are monitoring the process 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.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.

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.

Resolved: Block production on Arbitrum Nova has resumed, and our nodes are syncing normally. Thanks for your patience.

Investigating: We're investigating an issue on Arbitrum Nova where no new blocks have been produced since block 85283638. We're in contact with the Arbitrum team to understand 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 this issue.

Resolved: This incident has been resolved.

Monitoring: Service has stabilized and we are monitoring for stability.

Investigating: We are currently investigating the elevated API errors being served on Near Mainnet. We will post updates as we receive further information.

Resolved: This incident has been resolved.

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: This incident has been resolved.

Investigating: The Aptos Foundation is beginning a scheduled state reset on Aptos Testnet at 17 UTC today, per AIP-147.

The reset returns Testnet to a fresh genesis and clears all prior on-chain state. The Aptos Foundation expects the process to take a few hours, with up to 48 hours possible if complications arise.

What this means for you: Once resync completes, previously deployed contracts, test accounts, and balances on Aptos Testnet no longer exist. You'll need to redeploy contracts and recreate test state against the new genesis.

Resolved: Injective Mainnet has remained stable since block production resumed, and our nodes are fully synced and serving current data. This incident is now resolved. Thank you for your patience.

Monitoring: Injective Mainnet has resumed block production and our nodes are advancing past block 186,223,485 again. Requests are returning current data and the block height stall is no longer occurring. We will continue to monitor the network to confirm stability.

Identified: The Injective Foundation has confirmed the issue and will be publishing an upgrade guide shortly. Injective Mainnet remains stalled at block 186,223,485. We will apply the upgrade to our nodes as soon as it is available and share another update once the rollout is underway.

Investigating: We are currently investigating a block height stall on Injective Mainnet. Nodes stopped advancing at block 186,223,485, and requests may return stale data until block production resumes. Our team is actively working on this and we will provide an update as soon as we have more information.

Resolved: This incident has been resolved.

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.