Posted on November 7, 2025

On November 5, 2025 at 05:35 KST (20:35 UTC), a client update introduced a validity check issue in the archive node for Polygon Amoy. This impacts the Web3 Data API service for the Amoy testnet, causing degraded/partial availability, and some recent data may be unavailable or incomplete.

This incident affects Polygon Amoy only. Other networks and services are not impacted.

We are investigating and implementing fixes; further updates will be provided as progress is made.

Thank you for your patience and understanding.

—
Nodit Team

[Breaking Changes] Upcoming Testnet Data Retention Policy Update

Posted on October 23, 2025

Nodit will apply a new Web3 Data API data retention policy for all Testnets starting Tuesday, November 25, 2025, after 05:00 UTC (14:00 KST).

This change introduces a 90-day data retention limit for all Testnets chains. After the update, only data from the most recent 90 days will be available through the Web3 Data API.

This policy does not apply to chains for which Nodit currently provides only a Testnet (without Mainnet support). For these networks, all data will remain accessible without the 90-day limit.

Affected Networks

The new 90-day retention policy applies to the following chains:

This policy will also apply to any future Testnets added to the Web3 Data API, except for those that do not have a corresponding Mainnet supported by Nodit.

What’s Changing

• All Testnet responses from the Web3 Data API will return data from the past 90 days only (excluding testnet-only chains).
• When requesting snapshot data (e.g., a block or transaction hash) older than 90 days, the following error message will be returned:

{
  "code": "RESOURCE_NOT_FOUND",
  "message": "Resource not found: { RESOURCE_NAME = RESOURCE_VALUE }. Testnet only retains data from the past 3 months. To access older data, please use a Node API."
}

• For state-based resources such as accounts, token holders, and smart contracts, accumulated states will continue to be returned as before.
• For multi-record queries, only data within the 90-day retention window will be included.
• When using fromDate or toDate parameters that extend beyond the 90-day range, the response will contain no data for those periods, without triggering an error.

APIs Directly Affected

The following APIs will be directly affected ⏤ will throw 404 Not Found error for hash or id before 90 days ⏤ by this policy change(for each networks):

• Get Block by Hash or Number
• Get Ledger by Hash or Index
• Get Transaction By Transaction ID
• Get Transaction By Version
• Get Transactions In Block
• Get Transactions In Ledger

Other Web3 Data APIs will also no longer return data older than 90 days after this change.

This adjustment is part of Nodit’s ongoing effort to optimize resources for less frequently accessed datasets, allowing us to enhance performance and expand support for additional chains and features.

We appreciate your understanding as we implement this change to deliver a more efficient and scalable service environment.

—

Nodit Team