Pool Uptime Monitor
Independent monitoring of Bitcoin mining pool availability. Stratum, website, and dashboard endpoints checked every 5 minutes from a single location (Contabo VPS, Germany).
| Pool | Status | Stratum | Web | 90-Day History | ||
|---|---|---|---|---|---|---|
Operational | 100.00% | 540 ms | ||||
Operational | 100.00% | 300 ms | ||||
Operational | 100.00% | 260 ms | ||||
Operational | 100.00% | 323 ms | ||||
Operational | 100.00% | 455 ms | ||||
Operational | 100.00% | 681 ms | ||||
Operational | 100.00% | 680 ms | ||||
Operational | 100.00% | 946 ms | ||||
Operational | 100.00% | 961 ms | ||||
Operational | 100.00% | 784 ms | ||||
Operational | 100.00% | 828 ms | ||||
Operational | 100.00% | 1029 ms | ||||
Operational | 100.00% | 666 ms | ||||
Operational | 99.80% | 1245 ms | ||||
Operational | 99.79% | 1560 ms | ||||
Operational | 99.18% | 2145 ms | ||||
Operational | 98.78% | 551 ms | ||||
Operational | 97.45% | 897 ms | ||||
Down | 48.33% | — |
Recent Incidents
Why Pool Uptime Matters
When a mining pool goes down, your ASIC hardware continues consuming electricity but earns nothing. Even brief outages can cost miners significant revenue, especially at scale. Independent uptime monitoring helps you identify the most reliable pools and avoid those with recurring availability issues.
How We Monitor
HashRadar checks each pool's Stratum endpoint every 5 minutes using a full mining protocol handshake: we send mining.subscribe followed by mining.authorize, just like a real miner connecting to the pool. This proves the pool is not only reachable but actively serving mining work. We also monitor HTTP endpoints (websites and dashboards) for web availability.
Incident Detection
Our incident state machine requires 3 consecutive failed checks (15 minutes) before declaring a pool down, preventing false alarms from transient network issues. Recovery requires 2 consecutive successful checks. This approach balances sensitivity with reliability, giving you accurate uptime percentages you can trust.