Four data sources — and what each one shows
Hosted miners produce data through multiple independent channels. Each one shows something different, and none of them is complete on its own.
Hosting provider dashboard
- ·Facility-side miner status (online/offline as seen by the host)
- ·Power consumption readings (if the facility has per-rack metering)
- ·Basic temperature or environmental data (varies by provider)
- ·Repair and service status
Limitation: This is the host's view of your hardware — collected and reported by the same party whose service you're evaluating. It may not show hashrate quality, pool connectivity issues, or performance gaps that aren't visible from the facility side.
ASIC miner telemetry
- ·Per-chip hashrate and temperature
- ·Fan speed and thermal throttling
- ·Board-level fault conditions
- ·Local miner logs
Limitation: Direct access to the miner's own telemetry requires either local network access or a management interface provided by the hosting facility. Many hosted miners are behind the host's network, with remote access varying by provider.
Mining pool worker data
- ·Worker-level submitted hashrate (what the pool actually received)
- ·Accepted, rejected, and stale share counts
- ·Worker online/offline state as seen from the pool
- ·Per-worker earnings attribution
- ·Historical performance over any period the pool retains
This is independent of your host. It reflects what the pool received from your miners — not what the host reported about your miners. Pool data is the most direct available measure of whether your miner was actually hashing and earning.
Independent historical analysis
- ·Patterns of worker downtime over time
- ·Comparison of expected vs. observed performance
- ·Correlation between uptime patterns and billing periods
- ·Identification of intermittent or recurring underperformance
Limitation: Requires retaining pool data over time and analyzing it in context. This is what MineDocks is being built to provide — drawing on pool worker data that hosted miners already have, to produce analysis that's independent of the hosting provider.
What pool data can tell you about your hosted miners
Worker went offline
The pool stopped receiving submissions from that worker. The worker was not hashing during that period as seen from the pool.
Worker hashed below spec
Submitted hashrate was materially lower than the miner's rated capacity. This is visible in per-worker pool statistics where the pool tracks submitted work.
Downtime duration and pattern
Pool data shows exactly when a worker was last active and when it resumed. Patterns — such as repeated short outages, or specific time-of-day gaps — are visible in the historical record.
Whether earnings matched uptime
Pool-side earnings attribution tracks what each worker earned. If a worker was offline, it earned nothing during that period — this is traceable from the pool record independently of the host's billing.
The cause of downtime
Pool data records that a worker stopped submitting work. It does not tell you why — whether due to a power outage at the facility, a hardware failure, a network issue, curtailment, a scheduled maintenance event, or something else. Determining cause typically requires additional evidence: provider communications, facility event logs, or corroborating data.
Whether the host was at fault
Observed downtime does not by itself prove the host caused it. Hardware fails independently of host actions. Network issues may originate outside the facility. Pool data establishes what happened; not why or who is responsible.
Important distinction
MineDocks analysis is intended to show what was observed — worker stopped reporting, hashrate declined below expected — rather than attributing cause. The observed data is meaningful on its own. It tells you what the pool saw, independent of what the provider reported.
Limitations of each data source
None of these data sources is complete without the others. A thorough understanding of hosted-miner performance requires looking at all of them — and being clear about what each one can and cannot show.
| Source | Shows | Doesn't show |
|---|---|---|
| Provider dashboard | Facility-side miner status, operational events | Independent verification of delivered performance |
| ASIC telemetry | Chip/board-level detail, thermal state | Whether work was accepted by the pool |
| Pool worker data | Submitted hashrate, downtime as seen by pool, earnings | Cause of downtime, hardware diagnostics |
| Historical analysis | Patterns, expected vs. observed comparisons | Real-time status; requires data retention |
Read-only pool access: how MineDocks works
Many mining pools expose read-only API access to worker-level performance data. This allows external analysis without requiring custody of any assets or withdrawal access to the pool account.
MineDocks never requires:
- ✓Seed phrases or private keys
- ✓Withdrawal access or custody of BTC
- ✓Hosting provider login credentials
- ✓Write access of any kind to your pool account
Analysis is performed on pool worker performance data — hashrate, uptime patterns, and share statistics that describe what happened, not financial credentials or custody.
Not all mining pools expose identical API fields. The specific metrics available depend on what each pool publishes. MineDocks analysis is scoped to what pool APIs actually provide — not what would theoretically be useful.
What MineDocks is building toward
The current MineDocks beta is a Host Performance Report — an analysis of your mining pool worker data that shows observed uptime, hashrate patterns, and potential discrepancies between what your miners delivered and what the pool received.
Future MineDocks development is focused on making this independent pool-side analysis available systematically to hosted miners: tracking observed performance over time, building a history of what pool data shows across different providers and facilities, and eventually publishing that data in the Host Explorer as an independent layer alongside provider-stated claims.
That independent data layer does not currently exist for any provider in the MineDocks database. What exists today is the infrastructure to collect and analyze it, and the validation-stage beta report.
Already hosting miners?
The MineDocks beta report analyzes your pool worker data to identify potential downtime, underperformance, and discrepancies — independently of your hosting provider's dashboard.
Get a Free Host Performance Report