Company
Corrections
How ComputeTape handles corrections and source issues.
Corrections need to be visible and disciplined because compute-market data can affect reader decisions.
ops@computetape.comInbox
Use for corrections, source issues, and broken page reports.
Visible changesPolicy
Material changes are noted when needed.
Editorial + dataScope
Corrections apply to written analysis and displayed market values.
Log
Recent corrections
1 correction issued. Each restated value keeps its superseded figure in the downloadable data.
- Aug 7, 2026 — ComputeTape H100 Index (CT-H100), Jul 29, 2026 to Aug 6, 2026: CT-H100 was published at $6.52 across 4 providers. The corrected value is $5.22 across 6 providers. A single 30-day editorial-review clock dropped Crusoe and Lambda from the eligible sample on 2026-07-29. Both rows were being re-scraped and confirmed unchanged every morning, and neither price moved during the affected window; only the review metadata had lapsed. Because review expiry sheds cheap long-tail neoclouds faster than vendor-fed hyperscalers, the surviving four-provider sample was biased upward.
Material corrections will appear here with date, page, and the change made.
What counts
Corrections this page will record
- A displayed market value, source link, observation timestamp, or confidence label was wrong.
- A story summary misstated the source-backed fact or blurred fact with ComputeTape interpretation.
- A methodology caveat was missing or unclear enough to change how a reader should use the data.
Process
Correction process
- Review the claim, source, timestamp, and affected page.
- Correct factual errors directly.
- Add a note when a market value, timestamp, or source changes materially.
- Keep editorial interpretation separate from raw-data corrections.