Near Mainnet: Degraded Performance on archive requests

All data forward from block 158817115 is fully accessible. Current block information served from tip is operating normally.

We have increased network capacity to reduce load and improve response times. Tip block data remains fully available, as before.

Archive data is available from block 158817115 onward. Requests for blocks prior to this will return HTTP 422 errors with the message “UNKNOWN_BLOCK”, affecting historical queries before August 8th at 23:59 UTC.

We will provide another update within 2 days

All blocks from 158817115 onward are fully available. Current block requests, recent historical queries, and streams operating at or near tip continue to function normally.
Archive requests for blocks prior to 158817115 will return HTTP 422 errors with the message “UNKNOWN_BLOCK”, impacting all historical data queries for any blocks before August 8th at 23:59 UTC.
Our team is continuing work on restoring full archive availability in collaboration with the NEAR Protocol core team. We will provide another update within 12 hours.

There is no change to the current impact. Our engineers are still investigating. We will provide another update within 2 hours.

The NEAR Archive API remains degraded due to missing historical blocks, which may result in UNKNOWN_BLOCK errors, timeouts or incomplete responses. Our team is working with the NEAR Protocol core team on a solution and will provide another update by 22:00 UTC.

The NEAR Archive API continues to experience degraded performance due to missing blocks. Some requests for historical data may return timeouts or incomplete responses. All other QuickNode NEAR products remain unaffected.

The NEAR Archive API is missing specific historical blocks, resulting in UNKNOWN_BLOCK errors when requesting this data. This is not an intermittent issue and affected blocks cannot be retrieved through retries.

Our engineering team continues working with the NEAR Protocol core team on a solution. We will provide another update by 20:00 UTC or sooner if new information becomes available.

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

Some of the archive nodes are starting to serve requests. Our engineering team is continuing to monitor.

Full nodes are fully synced and serving tip-level requests. Archive nodes remain partially degraded. Our engineers are actively re-sharding the archive nodes and working with the foundation team to speed up the fix.

Work toward full resolution is ongoing. Archive nodes are still degraded as engineers continue re-sharding.
We will provide another update within 2 hours.

Full nodes remain fully synced and serving tip-level requests. Archive nodes are still partially degraded as engineers continue re-sharding. Work toward full resolution is ongoing.
We will provide another update within 2 hours.

Full nodes are fully synced and serving tip-level requests.
Archive nodes remain partially degraded. Our engineers are currently re-sharding the archive nodes to include Shards 10 and 11.

Full nodes are fully synced and serving tip-level requests. Archive nodes remain partially degraded; we are actively implementing recovery procedures to restore complete archive query performance.

Our full nodes are back at the tip and have started serving requests. We are actively working on recovering the archive nodes.

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

We are currently investigating this issue.