- Source: inbox/queue/2026-01-30-spacenews-spacex-fcc-million-satellite-orbital-datacenter.md - Domain: space-development - Claims: 2, Entities: 1 - Enrichments: 4 - Extracted by: pipeline ingest (OpenRouter anthropic/claude-sonnet-4.5) Pentagon-Agent: Astra <PIPELINE>
47 lines
No EOL
3.1 KiB
Markdown
47 lines
No EOL
3.1 KiB
Markdown
# SpaceX Orbital Data Center Constellation
|
||
|
||
**Type:** Satellite constellation (orbital compute infrastructure)
|
||
**Status:** FCC application filed, not authorized
|
||
**Operator:** SpaceX
|
||
**Purpose:** AI data processing using orbital solar power
|
||
**Scale:** Up to 1,000,000 satellites
|
||
**Altitude:** 500-2,000 km (above standard Starlink at ~550 km)
|
||
**Inclinations:** 30° and sun-synchronous
|
||
**Power per satellite:** 100 kilowatts (per Musk illustration)
|
||
**Relationship to Starlink:** Separate constellation, distinct FCC application
|
||
|
||
## Overview
|
||
|
||
SpaceX's orbital data center constellation is a proposed mega-constellation of up to 1 million satellites designed for AI data processing in orbit. Filed with the FCC on January 30, 2026, it represents the largest orbital infrastructure claim in history — 33x larger than all authorized Starlink satellites combined.
|
||
|
||
## Technical Architecture
|
||
|
||
Each satellite is designed to operate at 100 kilowatts of power for onboard AI processors, using "near-constant solar power" from sun-synchronous and 30° inclination orbits. The constellation operates at 500-2,000km altitude, above standard Starlink shells, to maximize solar irradiance exposure time.
|
||
|
||
## Regulatory Status
|
||
|
||
The FCC accepted the application for filing on February 4, 2026 (DA-26-113) and opened it for public comment on February 5, 2026. SpaceX requested a waiver of standard FCC deployment milestone requirements, which typically mandate half the constellation deployed within 6 years and the full system within 9 years. The waiver request signals that SpaceX acknowledges the deployment timeline is aspirational rather than near-term operational.
|
||
|
||
## Strategic Context
|
||
|
||
The filing was submitted 3 days before SpaceX's xAI acquisition announcement (February 2, 2026), suggesting coordinated strategy. Together with the Terafab announcement (March 21, 2026, with 80% of compute earmarked for orbital data center chips), the sequence reveals SpaceX's vertical integration strategy extending to orbital compute infrastructure.
|
||
|
||
## Scale and Implications
|
||
|
||
At 1 million satellites, the constellation would:
|
||
- Require approximately 2,500 Starship flights for launch (at 100 tonnes per launch, 250kg satellite mass)
|
||
- Represent 25 years of full Starship cadence at 100 flights/year
|
||
- Add 40x the current tracked orbital debris population
|
||
- Generate 100 GW of orbital solar power if fully deployed (100kW × 1M satellites)
|
||
|
||
## Debris and Governance Concerns
|
||
|
||
The constellation's scale and altitude range (500-2,000km, where debris persists for years to decades) create unprecedented orbital debris risk. At 1 million satellites, even perfect deorbit compliance would fundamentally alter collision probability for all orbital operators. The filing does not address debris management at this scale.
|
||
|
||
## Timeline
|
||
|
||
- **2026-01-30** — FCC application filed for up to 1M satellite orbital data center constellation
|
||
- **2026-02-04** — FCC accepted application for filing (DA-26-113)
|
||
- **2026-02-05** — FCC opened application for public comment
|
||
- **2026-02-02** — SpaceX announced xAI acquisition (3 days after filing)
|
||
- **2026-03-21** — Terafab announced with 80% compute for orbital data center chips |