Compute North
Crypto data center capex is only cheap if BTC and hashprice stay high. Compute North built through 2022 and never recovered.
Compute North was a Crypto / Data Center Hosting startup founded in 2017 in USA. It raised $385M before collapsing in 2022 — 5 years of runway burned. IdeaProof's AI Failure Score: 62/100, driven by debt-financed data center build tripped when btc crashed and compute north's own customers defaulted. The shutdown affected employees, investors, and the broader Crypto / Data Center Hosting ecosystem. This case study breaks down the timeline, root causes, competitors that won, and replicable lessons for founders validating similar ideas today.
Why did Compute North fail?
Compute North failed in 2022 after 5 years of operation, losing $385M in raised capital. The root cause was debt-financed data center build tripped when btc crashed and compute north's own customers defaulted. Key lesson: Crypto data center capex is only cheap if BTC and hashprice stay high. Compute North built through 2022 and never recovered.
2017 → 2022
$385M
Crypto / Data Center Hosting
USA
IdeaProof AI Failure Score
What Happened: The Timeline
2017
Founded in Minneapolis-St. Paul
2022-02
Raises $385M debt+equity for TX/NE build-out
2022-06
BTC crash begins hitting customer payments
2022-09-22
Files Chapter 11 in Southern District Texas
Root Causes
Compute North raised $385M in debt and equity across 2021-22 to build large-scale hosted crypto mining and HPC data centers in Texas and Nebraska. When BTC crashed 65% and multiple mining customers went insolvent, Compute North filed Chapter 11 on September 22, 2022, one of the first major hosting-side crypto bankruptcies. Assets were sold in a court-supervised process during 2023, with parts acquired by Generate Capital and other investors.
Causal Chain
This is our reading of the causal chain — separated from the verifiable facts above. Timeline dates, funding numbers and filings are facts (see methodology); root / proximate / terminal attribution is judgement based on public evidence.
Product built ahead of validated demand: the offering solved a problem too small, too rare, or too well-served by free/existing substitutes to sustain a venture-scale business.
- Debt-heavy capex program timed to peak BTC
- Mining customers defaulted on hosting fees
- Energy costs rose alongside revenue drops
- Insufficient liquidity for a full crypto winter
2022-06: BTC crash begins hitting customer payments
2022-09-22: Files Chapter 11 in Southern District Texas
Base rates
A single failure is an anecdote. These base rates give you the denominator — how common this outcome is across all startups matching Compute North's profile. Sources are third-party; we do not restate them as our own claims.
of crypto/Web3 projects launched in the 2021 cycle were inactive or delisted within 24 months of peak market cap.
CoinGecko + Nansen dataset analysis (2023)of startups ultimately fail — including ~10% that fail in the first year and the rest across the following decade.
Startup Genome / CB Insights aggregate (2024)of new US employer businesses survive past their 10th year (Bureau of Labor Statistics BED series).
US Bureau of Labor Statistics — BED (2024)of Series A rounds ever graduate to Series B; the rest run out of runway or pivot without a follow-on.
CB Insights Venture Capital Funnel (2023)Key Lessons Learned
1. Hosting economics = customer credit quality
Compute North's hosting revenue was only as good as its miner customers. When they defaulted, the leverage tore the balance sheet apart.
2. Timing infra capex to a commodity peak is fatal
$385M raised at peak BTC funded a build-out that met a crashed market — a pattern shared with dozens of 2022 crypto casualties.
Frequently Asked Questions
Sources & Confidence
Every data point is tagged with its source type and our confidence in it. How we grade sources.
Could This Failure Have Been Prevented?
IdeaProof's AI validates market demand, competitive positioning, and business model viability in minutes — catching the exact issues that sank Compute North.
Spotted a factual error?
Approved corrections are published in the public changelog with attribution.