Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£861.31
EST. MONTHLY
205
DAYS
EST. ROI
Mining downtime cost is the financial effect of unavailable productive hashrate during a defined period. A useful calculation starts with the net contribution the affected miners would probably have made, then adds direct recovery labour, contract effects and other event costs.
The calculation should not use gross revenue as the whole loss while ignoring electricity that was not consumed. It must also distinguish one failed machine from a site outage. This guide builds a clear hourly method that can support spare parts, monitoring and maintenance decisions.
Estimated reading time: 7 minutes
TL;DR
- Use affected accepted hashrate and a dated net contribution per unit of hashrate, not the whole site's gross revenue.
- Add diagnosis, repair, restart and contractual costs, but subtract costs genuinely avoided while equipment was off.
- Record the outage timeline and root cause so the figure can guide prevention instead of becoming a rough guess.
What This Means in Simple English
If a miner is off, it cannot earn pool credit, but it also stops using most of its electricity. The real hourly loss is therefore the profit contribution that disappeared, plus the extra cost of fixing and recovering the equipment.
Simple Example
Ten affected miners would normally contribute £18 per hour after electricity and pool fees. The outage lasts two hours. Recovery labour costs £25 and restart delay adds £9. The event cost is £70: £36 lost contribution, plus £25 labour, plus £9 restart loss.
Key Terms in Plain English
| Downtime: | A period when equipment cannot perform the intended productive work. |
|---|---|
| Net Contribution: | Revenue less the variable costs avoided when production stops. |
| Affected Hashrate: | The accepted mining capacity unavailable because of the event. |
| Recovery Time: | The period needed to restore stable accepted work after the fault is cleared. |
| Root Cause: | The underlying fault or condition that created the outage. |
Define the Outage Boundary
Write the start and end times before calculating money. The start may be the first pool alert or the first missing interval. The end should be stable accepted work, not merely power restored or a dashboard loaded.
List the exact miners, racks, circuits and supporting systems affected. A network outage may stop every miner while an individual fan fault affects one unit. Using total site hashrate for a partial event exaggerates the loss.
Use Accepted Hashrate Instead of Labels
Rated hashrate is useful for planning but may not match normal credited output. Use a representative accepted hashrate baseline from the same workers and operating mode. Exclude miners already offline before the event.
Pool estimates move over short windows because shares arrive randomly. Use a longer normal period and retain local logs as supporting evidence. Do not treat one five minute pool estimate as the exact missing output.
Calculate Lost Net Contribution
Estimate the revenue the affected accepted hashrate would have produced for the outage window. Subtract pool fees and variable electricity, cooling or service costs that were avoided while the equipment was off.
This gives lost net contribution rather than lost gross revenue. If hosting is charged as a fixed monthly amount regardless of operation, it may not be avoided. If the tariff charges each kilowatt hour, stopped miners reduce that part of the bill.
Add Diagnosis and Recovery Costs
Record staff time spent investigating, travelling, isolating equipment, replacing parts, testing and returning the miners to service. Use the actual labour basis rather than a made up flat percentage.
Add replacement parts, express delivery, contractor call out and temporary equipment where they arose because of the outage. Keep capital upgrades separate unless the event genuinely caused that purchase.
Include Restart and Stabilisation
A miner may power on before it returns to normal accepted work. Hashboards can tune, pools reconnect and cooling conditions settle. Count this recovery period when its output remains below the approved baseline.
Some faults cause repeated short restarts. Group them into one incident when they share a root cause and recovery action. Otherwise the report can hide a long degraded event as many tiny interruptions.
Check Contract and Customer Effects
A hosting contract may contain service credits, availability targets or exclusions. Apply only the wording that covers the actual event. Do not assume lost miner revenue and a customer credit are the same measure.
Customer communication and evidence gathering can add real labour. Reputation is important but should not be assigned an invented cash value. Record observable consequences and keep uncertain impacts separate.
Avoid Double Counting
Do not add gross revenue lost and then add electricity as another loss when the electricity was not consumed. Do not add repair labour twice through both a call out invoice and an internal hourly allocation.
Do not count the same restart period inside both outage duration and a separate recovery loss unless the formula clearly removes the overlap. Use a simple timeline and one owner for each cost line.
Turn the Figure into a Decision
Hourly mining downtime cost helps compare a spare power supply, better monitoring, redundant network equipment or planned maintenance. Compare the expected reduction in incident cost with the complete purchase and upkeep cost.
A single expensive outage does not prove every proposed control is worthwhile. Estimate incident frequency, detection time and how much the control can realistically prevent. Keep the assumptions visible.
Maintain Equipment Safely
Maintenance is non routine work and may expose people to electrical, moving or hot equipment. HSE guidance says work equipment should be maintained in an efficient state and maintenance should be planned so it can be carried out safely.
Use competent people and safe isolation. A lost mining hour is never a reason to bypass lock off, cooling, guarding or electrical checks. Schedule suitable work during planned downtime where practical.
Build a Repeatable Incident Record
Record alert time, confirmation time, isolation, diagnosis, repair, power restoration and stable accepted work. Add the affected assets, evidence source, root cause, action owner and calculation version.
Review similar incidents together. A falling mean time to repair or fewer repeated faults is stronger evidence than a dramatic claim from one case. Update the hourly value when difficulty, price, tariff or operating mode changes.
What the Current Data Can and Cannot Tell You
Mining revenue, network difficulty, fees and electricity tariffs change, so the hourly value needs a timestamp.
HSE guidance supports planned, competent and safely isolated maintenance; financial urgency does not remove those duties.
Pool hashrate is estimated from shares and should be compared across a representative baseline period.
Update mining downtime cost after a material tariff, difficulty, price or operating mode change.
Use mining downtime cost to compare controls only when every option uses the same incident boundary.
Keep mining downtime cost separate from uncertain reputation estimates that cannot be evidenced.
Decision Table
| Cost Line | Example |
|---|---|
| Lost net contribution | £18 per hour for two hours = £36 |
| Recovery labour | £25 |
| Restart loss | £9 |
| Avoided electricity | Already included in net contribution |
| Total incident cost | £70 |
The example explains the method only. Use affected accepted hashrate, actual tariffs, invoices and one non overlapping incident timeline for a real calculation.
Frequently Asked Questions
Should Mining Downtime Cost Use Gross Revenue?
Usually no. Use lost net contribution after variable costs that were genuinely avoided while the miners were off.
When Does a Mining Outage End?
End it when the affected equipment returns to stable accepted work, not simply when power or the dashboard returns.
Should I Use Rated or Accepted Hashrate?
Use a representative accepted hashrate baseline for the affected workers, supported by local records and the exact operating mode.
Can Mining Downtime Include Customer Credits?
Yes when the contract requires a credit for that event, but keep it separate from lost mining contribution and avoid overlap.
How Often Should the Hourly Cost Be Updated?
Update it whenever network difficulty, Bitcoin price, pool terms, electricity tariff or the normal operating profile changes materially.
Conclusion
Mining downtime cost is most useful when it follows one incident boundary from lost accepted work to safe recovery. Calculate lost net contribution, add direct event costs and remove every overlap. The resulting record can justify monitoring, spares and maintenance without turning a rough gross revenue number into a false loss claim.
Sources and Further Reading
- HSE Maintenance Of Work Equipment
- HSE Introduction To Electrical Safety
- Bitcoin Developer Guide: Mining
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.