Define routing strategies for RPC endpoints.

Ironforge offers two routing methods: Sequential and Parallel. Each method has its own advantages and considerations.

Screenshot of RPC Routing


The Sequential routing method follows a sequential order when sending requests to RPC endpoints. When a request is made, Ironforge forwards it to the first available RPC endpoint in the configured list. If the first endpoint responds successfully, Ironforge uses that response. However, if the first endpoint encounters an error or is unavailable, Ironforge automatically moves to the next available endpoint in the sequence. This process continues until a successful response is obtained or all endpoints have been attempted.


The Parallel routing method is designed for maximizing performance and responsiveness. When a request is received, Ironforge simultaneously sends it to all available RPC endpoints. Ironforge then uses the response from the first endpoint that responds successfully, discarding the responses from the remaining endpoints. This approach leverages parallel processing to reduce response times. However, it's important to note that the Parallel method may incur higher costs due to the increased utilization.