AI Weekly Malaysia

Alphabet plans to launch Google tensor processing units into orbit on a SpaceX Falcon 9 during the uncrewed Transporter-18 mission, scheduled for 11:15 am PT from Vandenberg Air Force Base, carrying Planet Labs satellites including a solar-powered prototype equipped with TPUs. It marks the first in-orbit test for Alphabet's Project Suncatcher, a moonshot initiative to develop reliable AI computing infrastructure in space. SpaceX has promoted supercomputers in orbit as a way to escape ground-based data-center constraints, and Alphabet holds a SpaceX stake worth more than $82 billion after SpaceX went public in June in a record IPO.

Why: Do not re-plan your AI stack around this yet: there is no announced capacity, pricing, API, latency, bandwidth, or Malaysia availability, so it does not change near-term cloud/TPU/GPU choices for local builders. Treat it as a science test to watch only if your long-term AI roadmap depends on escaping terrestrial data-center power and land limits.

Google flew a prototype orbital compute satellite on a SpaceX launch from California on October 1, 2026 — the first time it has sent an advanced chip to space. The satellite, built on a Planet Labs platform, will test whether a Google TPU can run in orbit, firing it in 15-minute bursts to stay within the satellite's power and thermal limits; a two-satellite demo with laser links is expected next year, and Google's stated end state is 81 satellites flying in close formation. Google's own estimate is that roughly 1,600 Starship launches would be needed before space data centers get off the ground.

Why: Nothing here changes what you build or buy today: the prototype runs a TPU in 15-minute bursts precisely because continuous kilowatt power and cooling in orbit are unsolved, and the 1,600-launch figure puts orbital compute well beyond any current planning horizon. Treat space data centers as a multi-year research bet, not a capacity option — if you are modelling GPU/TPU supply or energy costs for the next few years, terrestrial constraints are still the binding ones.