QuickNode Status

Identified: We're currently experiencing an issue where historical archive data for blocks prior to 158817115 before August 8th, 2025 at 23:59 UTC are unavailable, returning HTTP 422 "UNKNOWN_BLOCK" errors.

Our engineering team is working with the Near foundation team on restoring of blocks prior to 158817115 with a snapshot. Expected duration minimum of five days, expect the next update on Sept 5th at 17:00 UTC as we progress toward a resolution.

Identified: We're currently experiencing an issue where historical archive data for blocks prior to 158817115 before August 8th, 2025 at 23:59 UTC are unavailable, returning HTTP 422 "UNKNOWN_BLOCK" errors.

Our engineering team is working with the Near foundation team on restoring of blocks prior to 158817115 with a snapshot. Expected duration minimum of five days, expect the next update on Aug 25 at 17:00 UTC as we progress toward a resolution.

Resolved: This incident has been resolved.

Monitoring: All Solana-Testnet nodes have recovered. We are monitoring performance to ensure stability and will provide an update upon confirmation or if further action is required within 10 minutes.

Identified: Our team is continuing to work on restoring service on our US-E Solana-Testnet nodes. No customer action is needed at this time. We will share another update regarding 503 mitigation efforts by 22:20 UTC.

Investigating: We have identified a recent error spike on one of our Solana Testnet node clusters. Some customers may be seeing elevated 503 responses from requests on the network. Our team is working to restore services fully and will share another update within 20 minutes.

Resolved: The Jupiter team has started the process of deprecating the Self-Hosted Swap API, and the binary is no longer being maintained. While the service remains stable at this time, future changes from external DEXs may result in issues that will not be fixed upstream.

Our team is working to identify any potentially viable solutions, but we currently recommend using the previously mentioned workarounds if you encounter errors related to Pump.fun’s API.

Identified: Jupiter Swap API for token swaps may continue to receive degraded quotes due to a breaking change introduced in Pump.fun's API. Jupiter is not updating its binary to address this issue so you will need to apply one of the following workarounds:

• Excluding Pump from your Jupiter API requests by adding: excludeDexes: 'Pump.fun Amm' when calling the quote endpoint if pump.fun is not needed.
• Using the /pump-fun/ paths of the Metis add-on if you need to handle Pump.fun swaps directly. See docs: https://www.quicknode.com/docs/solana/pump-fun-quote

Identified: Solana API customers using Metis - Jupiter Swap API for token swaps may receive degraded quotes due to a breaking change introduced in Pump.fun's API. Jupiter is not updating its binary to address this issue.

As a temporary workaround, we recommend excluding Pump from your requests by adding the parameter: excludeDexes: 'Pump.fun Amm' when calling the quote endpoint.

Our engineers are investigating alternative solutions and will provide another update by 19 UTC

Resolved: This incident has been resolved.

Monitoring: Nodes are progressing again from block: 1960612

Identified: Starknet will reorg beginning at block 1960612, removing about one hour of chain activity. Transactions included from this point forward will be dropped from the ledger and must be retransmitted.

A permanent fix to prevent this edge-case scenario is being developed and will be released by the foundation as soon as possible.

Identified: We are closely listening to updates from the foundation. As we progress toward a resolution, expect the next update on or before September 2, 08:00 UTC.

https://status.starknet.io/incidents/6p1hp8q4lykt

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Identified: At block height 18722274, the chain experienced a stall. Nodes are now moving forward again, and we will continue to monitor the network closely. If you require any further assistance, please contact support.

https://support.quicknode.com/

Investigating: We are investigating this issue. As we progress toward a resolution, expect the next update on or before September 2 at 04:00 UTC.

Resolved: This incident has been resolved.

Monitoring: Most of our nodes have caught up to the chain tip and are serving requests, so you should now see the latest data from your endpoint. Our team continues to monitor closely, and we will provide another update by 10:00 UTC or sooner.

Identified: Some nodes have caught up to the chain tip, and you should now see the latest data from your endpoint. Our team continues to monitor closely. We will provide another update by 08:00 UTC or sooner.

Investigating: The zkEVM mainnet nodes appear to have stalled at block 25,194,190. The QuickNode team is investigating and will update you with more information once it is available.

We will provide the next update by 05:00 UTC or sooner.

Resolved: This incident has been resolved.

Identified: Some of our nodes are starting and in the middle to catch up to the tip. You might see some 503s due to degraded performance. Our team is continuing to monitor closely.

We will update you again by 6:00 UTC or sooner.

Investigating: Customers using Race Mainnet and Sepolia APIs will not be able to retrieve data after block #18076526 and #18464043 respectively by network. Working with foundation team on resolution, expect provide additional updates when more information is available.