Candidate filtering
Routes retain enabled Endpoints that match the required chain, network, and protocol.
RPC failover
Move RPC failover out of your application code
Keep primary and backup Endpoints behind one Access Point. Retryable failures can move to another eligible target within the Route attempt bound.
Fail over with explicit routing rules
Priority routing follows the configured Endpoint order and advances when a target is filtered, rejected by its Circuit, or returns a retryable failure. Valid upstream JSON-RPC application errors remain final.
Bounded attempts
Route configuration sets the attempt limit, while the Gateway decides which operations can move after each failure.
Circuit recovery
Circuit states stop traffic to an unhealthy Endpoint and admit probes as recovery progresses.
Combine failover with multiple providers
Synchronize Endpoints from supported vendors, add matching targets to a Route, and choose ordered priority or weighted selection for the eligible candidate set.
Explore multi-provider RPCReview retry strategyUnderstand Circuit states
Next step
Add a backup to an existing Route
Place matching Endpoints in priority order, then choose the attempt bound that fits your application calls.