Urgent.News

What's breaking now, across thousands of outlets.

Tech

Google launches first datacenter satellite and research that finds orbiting bit barns can work

If SpaceX can launch 1,800 Starships, and researchers nail gnarly networking, design and formation flying problems,

Google launches first datacenter satellite and research that finds orbiting bit barns can work

Google has successfully launched its first "Suncatcher" datacenter satellite into space, but questions remain about the feasibility of scaling this orbiting infrastructure. The Project Suncatcher aims to assess whether Google's tensor processing units (TPUs) can withstand launch and space conditions, potentially validating the cost-effectiveness of placing servers in orbit due to the abundant solar energy available.

In an announcement and accompanying peer-reviewed research, Google highlighted numerous challenges that must be overcome to make orbital datacenters viable.

The paper, titled "Toward a future space-based, highly scalable AI infrastructure system design," explains that SpaceX and other companies have suggested orbital datacenters could become practical when launch costs fall to $200 per kilogram. Google's researchers found that SpaceX has managed to cut launch costs by 20% with each doubling of cumulative mass launched.

If SpaceX maintains this trend, reaching 370,000 tons of additional cumulative mass (equivalent to approximately 1,800 successful Starship rocket launches) and reusing components 100 times, Google believes a $200/kilogram launch cost could be "plausible under reasonable assumptions."

While Google does not know the mass of its future datacenter satellites, they compared the cost of sending a satellite into space with the expense of powering servers on Earth. If launch costs reach approximately $200 per kilogram, the annualized cost per unit of power in space could become comparable to terrestrial spend. However, the paper notes that existing network technologies are likely insufficient for linking multiple satellites into functioning clusters.

To address this, Google's plans would require a highly integrated design, potentially incorporating next-generation architectures like computational substrates based on neural cellular automata.

Moreover, Google emphasized the need for robust optical satellite-ground communications, which will face challenges such as atmospheric turbulence, high-speed relative motion errors, and precision beam tracking. NASA's TeraByte Infrared Delivery (TBIRD) mission demonstrated 200 Gbps ground-low-earth-orbit communications and is cited as a promising approach.

Google concluded that achieving its space datacenter ambitions will require sustained research, iterative design refinement, and the accomplishment of several critical future milestones.

Written by urgent.news from The Register's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at theregister.com →

More in Tech

Structured Logging and Distributed Tracing: Moving Beyond console.log

We have all been there during an outage: staring at terminal logs searching for an error: [2026-09-25 02:14:12] Error processing request: object is None [2026-09-25 02:14:12] Failed to charge credit…

  • Structured JSON logging provides machine-readable, queryable format for complex systems
  • Correlation IDs enable tracing request lifecycle across multiple services
  • Middleware implementation facilitates attaching correlation ID to requests in frameworks

Understanding Prototypes in JavaScript: A Practical Guide for Developers

JavaScript uses prototypes to support inheritance, property lookup, and shared behavior between objects. Although modern syntax gives us classes and familiar object-oriented patterns, prototypes…

  • JavaScript uses prototypes for inheritance and shared behavior among objects
  • Every object has an internal prototype reference for property lookup
  • Prototype chain enables shared methods across instances and constructor functions

CVE-2026-92951: CVE-2026-92951: Sandbox Escape via External Package Allowlist Bypass in vm2

CVE-2026-92951: Sandbox Escape via External Package Allowlist Bypass in vm2 Vulnerability ID: CVE-2026-92951 CVSS Score: 9.9 Published: 2026-10-01 An incorrect authorization and directory traversal…

  • Remote attackers can bypass sandbox in vm2, execute arbitrary host code.
  • Incorrect authorization and directory traversal in external package allowlist.
  • Upgrade to vm2 version 3.11.7 or later to fix vulnerability.

More from Friday 2 October →