Compass Mining Hosting Cost & Downtime: How the Billing Model Works

The billing structure: flat monthly fee, prepaid

What this means in practice: your monthly hosting cost at Compass is determined by your miner's power draw (in kilowatts) and the facility rate — not by how many hours your miner actually ran during that month. You pay the contracted rate for the full month whether the miner hashed for all 720 hours or fewer.

The fee is prepaid in advance. This is the billing structure described in Compass's own FAQ documentation.

Hosting rates: why no single number is shown

Compass's hosting rates are not uniform across their network. Rates vary by facility, and current rates are not confirmed as a single provider-wide figure from MineDocks's primary source review.

Current hosting rates vary by facility and are not confirmed as a single provider-wide figure from current primary sources. Review current Compass facility listings for specific pricing.

MineDocks policy is to avoid publishing a universal rate when the primary source does not confirm one. This applies to Compass specifically because rates differ meaningfully by facility — and publishing one number would imply that it applies everywhere, which is not accurate.

The 95% uptime SLA: what it covers and how it's measured

The 95% facility uptime SLA is a claim about facility availability, measured by ping or online-status — not by delivered hashrate or pool-side mining output.

What this means: a miner can register as “up” under ping-based methodology while not hashing at full capacity, or while experiencing connection quality issues that affect pool submissions. The SLA measures whether the facility's network and power were available to the miner — not whether the miner was delivering expected mining performance.

This is not a criticism specific to Compass — ping-based uptime measurement is common across the industry. But it is a meaningful distinction when evaluating what an uptime guarantee actually covers.

Downtime remediation: Compass Credits

When eligible downtime occurs, Compass's documented policy provides for Compass Credits — credits applied against future hosting fees. This is the downtime remedy described in their support documentation.

This distinction matters for miners evaluating their total economic exposure to downtime. Under a fixed monthly billing model with ping-based SLA measurement and credit-based remediation, the cost of an extended outage is: (a) continued hosting fees during the downtime, partially offset by credits if eligible; (b) lost mining revenue, which credits do not cover.

Contract structure

Contract terms vary by product. The standard hosted product has historically required at least one year. Compass has also offered an “Easy Exit” monthly renewal product, which provides more flexibility but may have different pricing or availability. Check current Compass product listings for the specific terms applicable to any offer you're evaluating.

What MineDocks would measure differently

Compass's own dashboard shows facility-side miner status. The SLA is measured at the facility level by ping/online-status. These are the host's measurements, collected and reported by the same party providing the service.

MineDocks is being developed to analyze pool-side worker data — meaning what your mining pool actually received from your miners, independent of what the hosting dashboard shows. Pool data shows:

• ›When each worker was active and hashing as seen by the pool (not the facility)
• ›Submitted hashrate per worker — what the pool received, not what the miner reported locally
• ›Downtime duration as observed from the pool side
• ›Whether observed pool-side uptime aligns with what the provider reported

This is different from facility ping — and the difference matters. A miner can pass a ping test from the facility while not being connected to or hashing on the assigned pool. Pool-side data answers a different question: was this miner actually contributing hashrate, and when?