Skip to main content

2026-05-19

  1. The policy for the block query range available for each plan has been changed.

  2. The default range for querying by date and blockNumber in the Web3 Data API has been changed.

  3. The policy for Batch Call has been changed.

Major Updates​

Block Range and Batch Call Policy Updates per Pricing Plan​

Certain methods such as eth_getLogs can overload shared infrastructure resources when handling large-scale query requests, potentially affecting service stability.
To prevent this and deliver a more stable service, the block range and Batch Call policies for specific methods have been updated per plan.

1. Block Range Limit Changes by Plan​

  • Affected methods

    • eth_getLogs
    • eth_newFilter
    • eth_getFilterLogs
    • trace_filter

  • Changes

    • Starter Plan: Up to 10 Blocks
    • Starter Plus Plan and above: Up to 1,000 Blocks

2. Web3 Data API Query Range Changes​

  • Affected methods

    • All Web3 Data APIs that support fromDate, toDate, fromBlock, or toBlock as parameters

  • Changes

    • As-Is
      • Queryable range: All
      • Default query range: All
    • To-Be
      • Queryable range: All
      • Default query range: Last 30 days

3. Batch Call Policy Updates​

  1. A maximum of 300 items per batch is allowed. However, for reliable calls, we recommend setting 50 items or fewer per batch.
  2. Requests within a batch are treated as individual requests. If the combined CU of requests within a batch exceeds the plan's Throughput (CU/s), requests may be rate-limited.
  3. If a batch size limit, throughput limit, or response size limit (maximum 100MB) is exceeded, the entire Batch Call will fail. Violations of per-method limits will only cause that individual request to fail.