Skip to main content

[Maintenance] 2026-05-12

Posted: May 06, 2026

This update is scheduled on May 12, 2026.

Block Query Range and Batch Call Policy Updates by Pricing Plan​

To enhance the usability and stability of Shared Node Infra, the policy for methods that query large volumes of data will be updated.

  1. Block query range updates by pricing 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
  1. Web3 Data API policy update

  • Affected methods

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

  • Changes

    • As-Is
      • Queryable range: All
      • Default query range: All
    • To-Be
      • Queryable range: All
      • Default query range: Last 30 days
  1. Batch Call policy addition
  • A maximum of 300 requests can be included per batch. (In practice, including 50 or fewer requests per batch is recommended.)
  • Each request within a batch is counted as an individual request. As a result, requests may encounter throughput limit errors depending on usage.
  • If the response body size limit (maximum 100MB) is exceeded or the batch request format is invalid, the entire batch request may fail.

Team Account Permission Updates by Role​

As the number of projects and users within Team Account grows, the need for a new role to manage projects at the project level has emerged. The Admin role will be introduced in this update, and the permissions for the Editor and Viewer roles will also be adjusted accordingly.

  • Invitation permission changed
    • With the addition of a role dedicated to project management, the team invitation permission previously held by Editor and Viewer will be removed. Only Owner and Admin can invite members and assign appropriate permissions.
  • Viewer role API Key access removed
    • With the addition of new roles, the API Key access permission has been removed from Viewer so that Viewer can focus on its intended scope — viewing project information such as analytics. Members who need to access API Keys for development must be assigned the Editor role.