57 lines
4.4 KiB
Markdown
57 lines
4.4 KiB
Markdown
---
|
||
type: source
|
||
title: "SpaceX FCC Filing for 1 Million Orbital Data Center Satellites — Amazon Critique, Industry Skepticism"
|
||
author: "The Register / FCC / Amazon (@theregister)"
|
||
url: https://www.theregister.com/2026/02/05/spacex_1m_satellite_datacenter/
|
||
date: 2026-02-05
|
||
domain: space-development
|
||
secondary_domains: []
|
||
format: article
|
||
status: processed
|
||
processed_by: astra
|
||
processed_date: 2026-04-14
|
||
priority: high
|
||
tags: [orbital-data-centers, SpaceX, FCC, regulatory, Amazon, feasibility, launch-cadence, 1-million-satellites]
|
||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||
---
|
||
|
||
## Content
|
||
|
||
SpaceX filed FCC application January 30, 2026 for authority to launch up to 1 million satellites for an orbital data center constellation (500-2,000 km altitude). FCC accepted for filing February 4, 2026. Public comment period closed March 6, 2026. Nearly 1,500 comments submitted.
|
||
|
||
**SpaceX's claims:**
|
||
- "With Starship's ability to deliver unprecedented tonnage to orbit for AI compute, the capacity for intelligence processing in space could surpass the electricity consumption of the entire U.S. economy"
|
||
- 100 kW of power per metric ton allocated to computing
|
||
- High-bandwidth optical links for inter-satellite communication
|
||
- Solar-powered
|
||
|
||
**Amazon's FCC petition to block:**
|
||
- 1M sats × 5-year lifespan = 200,000 satellite replacements per year
|
||
- Global satellite launch output in 2025: <4,600 satellites
|
||
- Required launch cadence: **44x current global capacity**
|
||
- "Sustaining a one-million-satellite constellation would require a launch rate that has never been achieved in the history of spaceflight"
|
||
|
||
**Technical expert skepticism:**
|
||
- Expert: "I think it's unclear at this stage whether it's feasible or not" — "a lot in this proposal riding on assumptions and technology that doesn't appear to actually exist yet"
|
||
- Refrigeration in space: standard cooling systems rely on gravity for fluid management; in microgravity, compressor lubricating oil can clog systems; heat cannot rise via natural convection
|
||
- DarkSky International: 1M satellites would permanently alter the night sky, devastate astronomical observation
|
||
|
||
**Industry reaction:** Multiple industry leaders called it "insane." Dataconomy headline: "Industry Leaders Slam SpaceX's 'insane' Orbital Data Center Plan."
|
||
|
||
## Agent Notes
|
||
**Why this matters:** The Amazon critique is methodologically rigorous. 200,000 replacements/year vs. 4,600 global launches in 2025 is a 44x gap. This is not a cost problem — it's a physical production/launch capacity problem. Even if Starship achieves 1,000 flights/year with 300 sats/flight = 300,000 sats/year, and if ALL of them went to this one constellation, it's barely possible. But Starship isn't flying 1,000 times/year.
|
||
|
||
**What surprised me:** The filing may be less an engineering plan and more an orbital spectrum/shell reservation play — similar to how SpaceX filed for 42,000 Starlink satellites to lock in frequency coordination rights. 1M satellites = claim the orbital neighborhood, negotiate later.
|
||
|
||
**What I expected but didn't find:** Any technical specification in the FCC filing about radiation hardening, thermal management design, or compute architecture. The filing is at the level of "we want to launch satellites to do compute" — no engineering substance.
|
||
|
||
**KB connections:** orbital debris is a classic commons tragedy — 1M satellites dramatically increases Kessler syndrome risk. MIT TR notes LEO capacity may be limited to ~240,000 satellites across all shells. SpaceX is filing for 4x physical capacity.
|
||
|
||
**Extraction hints:**
|
||
- CLAIM CANDIDATE (DIVERGENCE): SpaceX's 1M satellite ODC filing may be a spectrum-reservation strategy (filing > engineering plan) rather than an engineering commitment — consistent with SpaceX's Starlink mega-constellation filing history. Diverges with literal interpretation as a deployment plan.
|
||
- Note: This filing is filed under SpaceX's regulatory authority, not an engineering review.
|
||
|
||
## Curator Notes
|
||
PRIMARY CONNECTION: SpaceX vertical integration across launch broadband and manufacturing — this is SpaceX potentially vertically integrating into compute (via Starlink network + xAI + ODC constellation).
|
||
WHY ARCHIVED: The authoritative statement of the anti-ODC case at mass scale. Amazon's 44x launch capacity math is the clearest single data point against SpaceX's constellation claims.
|
||
EXTRACTION HINT: Focus on the launch cadence math (44x gap) as the binding physical constraint, not just the cost or technology constraints.
|