Failover Pool
A Failover Pool is a backup mining pool configured in an ASIC miner that automatically takes over when the primary mining pool becomes unavailable. It allows miners to continue working if the main pool connection fails because of: server outage; network problems; maintenance; configuration errors; regional connectivity issues. A typical ASIC configuration includes: primary pool; secondary pool; tertiary pool.
Failover Pool Explained in Simple Terms
A failover pool works like a backup route.
Example:
Normal operation:
ASIC Miner → Primary Pool → Mining Continues
Problem:
Primary Pool Offline
Automatic switch:
ASIC Miner → Failover Pool → Mining Continues
The goal is to reduce the time when the miner has no valid mining connection.
How Failover Pool Works
The process usually follows these steps:
ASIC Connects to Primary Pool
The miner establishes a Stratum connection with the main pool.
Connection Failure Occurs
The miner detects:
timeout;
rejected connection;
server error;
network failure.
Failover Logic Activates
The ASIC switches to the next configured pool.
Backup Pool Provides Mining Jobs
The miner receives new work and continues submitting shares.
The process:
Primary Pool Failure → Detection → Pool Switch → Resume Mining
Example of Failover Pool in Practice
Example:
Priority | Pool |
1 | Primary Pool |
2 | Failover Pool |
3 | Backup Pool |
The miner attempts to use the highest-priority available pool.
Primary Pool vs Failover Pool
Feature | Primary Pool | Failover Pool |
Priority | First choice | Backup option |
Normal usage | Active | Usually inactive |
Purpose | Main mining connection | Maintain operation during failures |
Configuration | Required | Recommended |
The failover pool remains ready but is only used when necessary.
Why Failover Pools Are Used in ASIC Mining
Mining depends on continuous communication between ASIC miners and pools.
Without a backup:
Pool Failure → No Share Submission → Lost Mining Time
With failover:
Pool Failure → Automatic Switch → Continued Operation
Benefits include:
reduced downtime;
improved reliability;
protection from pool outages;
easier maintenance planning.
Failover Pool and Stratum Endpoint
Failover pools are configured using additional Stratum endpoints.
Example:
Primary:
stratum+tcp://pool-a.example.com:3333
Secondary:
stratum+tcp://pool-b.example.com:3333
The ASIC stores these endpoints and switches when required.
Failover Pool Configuration
ASIC miners usually allow several pool entries.
Example:
Setting | Value |
Pool 1 | |
Worker | farm01.worker01 |
Password | x |
Pool 2 | |
Pool 3 |
The order determines priority.
Failover Pool and ASIC Firmware
The switching behavior depends on ASIC firmware.
Firmware determines:
failure detection time;
retry intervals;
switching logic;
pool priority handling.
Different firmware versions may handle failover differently.
Failover Pool and Mining Downtime
A correctly configured failover pool reduces downtime caused by pool problems.
Example:
Without failover:
Event | Result |
Pool outage | Miner stops submitting shares |
Recovery | Requires manual action |
With failover:
Event | Result |
Pool outage | ASIC switches automatically |
Recovery | Mining continues |
The exact switching speed depends on miner configuration.
Failover Pool and Share Submission
When switching pools, the miner changes where shares are submitted.
Normal:
ASIC → Primary Pool → Shares
After failure:
ASIC → Failover Pool → Shares
The miner continues performing hashing, but accepted shares are credited according to the backup pool's rules.
Failover Pool and Mining Rewards
When a miner switches pools:
shares submitted to the backup pool contribute there;
reward calculation follows the backup pool's payment system;
payout settings may differ.
Operators should consider:
pool fees;
payout methods;
reliability;
reputation.
Failover Pool and Pool Selection Strategy
Mining operations may choose failover pools based on:
uptime history;
geographic location;
latency;
fees;
payout reliability;
operational stability.
The backup pool should be sufficiently reliable to support production mining.
Failover Pool and Latency
A backup pool may have different network characteristics.
Possible differences:
higher ping time;
different routing;
different server location.
Example:
Primary pool:
20 ms latency
Failover pool:
120 ms latency
The miner may still operate, but communication quality can differ.
Failover Pool and Packet Loss
Network problems can trigger failover behavior.
Examples:
packet loss;
connection resets;
unreachable servers.
However, temporary packet loss does not always mean immediate pool switching.
ASIC firmware determines failure thresholds.
Failover Pool and Network Monitoring
Mining operators monitor:
pool connection status;
switch events;
reconnect frequency;
rejected shares;
stale shares.
Unexpected frequent failovers may indicate:
network problems;
incorrect configuration;
unstable pool connections.
Failover Pool and Mining Farms
Large mining farms often configure backup pools across different providers.
Example:
Primary:
Pool Provider A
Backup:
Pool Provider B
Third:
Pool Provider C
This reduces dependence on one external service.
Failover Pool and Pool Maintenance
Mining pools sometimes perform scheduled maintenance.
A failover pool allows miners to continue working during:
software upgrades;
server migrations;
infrastructure maintenance.
The miner can return to the primary pool after service restoration.
Automatic Return to Primary Pool
Some ASIC firmware automatically returns to the primary pool when it becomes available.
Example:
Normal:
Pool A Active
Failure:
Pool B Active
Recovery:
Pool A Restored → Miner Switches Back
The behavior depends on firmware settings.
Failover Pool and Mining OS
Mining operating systems can manage failover settings across many ASIC devices.
Functions may include:
configuring backup pools;
changing priorities;
monitoring switching events;
applying fleet-wide settings.
This simplifies management of large deployments.
Failover Pool and Remote Management
Remote management platforms can update pool configurations without physical access.
Operators can:
add backup pools;
change priorities;
verify connections;
analyze failover events.
Failover Pool and Security
Pool credentials and configurations should be protected.
Security practices:
restrict access to management interfaces;
protect API credentials;
use secure remote access;
monitor configuration changes.
Unauthorized pool changes could redirect mining activity.
Failover Pool and Empty Mining Time
Without a failover pool:
Pool Failure → Miner Idle
With failover:
Pool Failure → Backup Connection → Mining Continues
This helps maximize operational availability.
Benefits of Failover Pools
Failover pools provide:
reduced mining interruptions;
automatic recovery from pool outages;
improved operational resilience;
easier maintenance handling;
protection from single pool failures.
Limitations of Failover Pools
Possible disadvantages:
backup pool may have higher fees;
different payout conditions;
higher latency;
configuration complexity;
switching delays.
A failover pool improves reliability but does not eliminate all downtime risks.
Failover Pool Best Practices
Recommended practices:
configure at least one backup pool;
choose reliable alternative providers;
test switching behavior;
monitor failover events;
verify worker credentials;
review payout conditions;
keep pool priorities documented.
Related Bitcoin Terms
Stratum Endpoint
Mining Pool
Pool Switching
ASIC Miner
Share Submission
Latency Monitoring
Uptime Monitoring
Remote Management