---
# System prepended metadata

title: Configure failover beacon nodes

---

# Configure failover beacon nodes

When running a [separate validator client](https://docs.teku.consensys.net/Reference/CLI/Subcommands/Validator-Client), Teku provides the capability to configure one or more beacon nodes, which would achieve redundancy.

## Usage

[beacon-node-api-endpoint](http://127.0.0.1:5051) option allows one or more comma-separated values:

1. `teku validator-client -beacon-node-api-endpoint=http://127.0.0.1:5051`
2. `teku validator-client -beacon-node-api-endpoint=http://127.0.0.1:5051,http://192.168.1.1:5051`

In the first example, the validator client will attempt to contact http://127.0.0.1:5051 to perform duties. If that node is offline, not synced or the request fails, then the validator client may fail to perform duties.

In the second example, if a request using http://127.0.0.1:5051 fails, then the same request will be attempted using http://192.168.1.1:5051. This allows the validator client to continue to perform its duties if at least one of the configured beacon nodes is available.

The ordering of the configured beacon nodes matters. The first one will be considered a primary and others as failovers. Typically, requests will be attempted using the primary beacon node first. If the validator client detects that the primary beacon node is offline or not synced, It will prefer a failover if one is available. When the primary beacon node is available again, requests will start using it first again.

## Advanced configuration

Teku provides couple of hidden options, which allow modifying the default behaviour when using failover beacon nodes. These should be used with caution and only by advanced users who understand the implications of the changed behaviour.


 - `--Xfailovers-send-subnet-subscriptions-enabled`

By default this option is set to `true` which means Teku sends subnet subscriptions to all configured beacon nodes to ensure that if a failover has to be used, it is ready.

 - `--Xfailovers-publish-signed-duties-enabled`

By default this option is set to `true` which means Teku sends signed duties (blocks, attestations, aggregations, etc) to all configured beacon nodes in order to propagate messages across the network faster. 

