Node and connection limitations

The nodes deployed with Chainstack are not rate-limited or throttled down.

There are some default limitations, however.

HTTP

• 1000 requests per connection — The maximum number of requests per one HTTP connection is limited to 1000. After serving 1000 requests in one HTTP connection, the current connection is closed and a new one is opened.
• 60 seconds timeout — An idle connection is closed in 60 seconds.
• 1 MB — The size of the request body that you send to a node is limited to 1 MB by default.

WebSocket

• 500 connections — The maximum number of open connections over WebSocket is 500.
• 3600 seconds timeout — An idle connection is closed in 1 hour.
• Connection drops with the message 1006 — Because you are sharing the node connection gateway with other customers, your WebSocket connection may close with the message 1006 and ECONNRESET. The two options to deal with this is implement a reconnect in your code or get a dedicated node gateway as part of customization.

eth_getLogs / getPastEvents block range limitation

Block range limitations apply for the eth_getLogs method on the Harmony and Fantom nodes since their clients have the hard caps natively. The limitations are as follows:

Fantom — 100 blocks.

Harmony — 1,024 blocks.

There are no specific limitations to other EVM-compatible protocols, but we recommend to stay in the following block ranges per request when using the eth_getLogs method on elastic nodes:

Ethereum — 2,000 blocks.

Polygon — 2,000 blocks.

BNB Smart Chain — 2,000 blocks.

Avalanche — 100,000 blocks.

Under the hood, the web3.js getPastEvents method calls eth_getLogs.

We also offer Node and Connection customizations. Such as increasing timeouts, max connections, adding more namespaces, etc. See also Node customizations.