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% | 367 ms | ||||
Operational | 100.00% | 256 ms | ||||
Operational | 100.00% | 160 ms | ||||
Operational | 100.00% | 122 ms | ||||
Operational | 100.00% | 474 ms | ||||
Operational | 100.00% | 171 ms | ||||
Operational | 100.00% | 743 ms | ||||
Operational | 100.00% | 192 ms | ||||
Operational | 100.00% | 233 ms | ||||
Operational | 100.00% | 210 ms | ||||
Operational | 100.00% | 682 ms | ||||
Operational | 99.98% | 486 ms | ||||
Operational | 99.98% | 773 ms | ||||
Operational | 99.97% | 1439 ms | ||||
Operational | 99.94% | 499 ms | ||||
Operational | 99.87% | 98 ms | ||||
Operational | 99.49% | 254 ms | ||||
Operational | 99.18% | 224 ms | ||||
Degraded | 93.77% | — |
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.