/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

How Google's networking infrastructure has evolved over ten years and five generations to deliver more than 1 petabit/sec of total bisection bandwidth

Amin Vahdat / Google Research Blog :

Google Research Blog Amin Vahdat

Context & Ripple Effects

Amin Vahdat's retrospective lands mid-arc in Google's decade-long buildout of its own plumbing: the same engineering culture that pushed in-cluster bisection bandwidth past a petabit per second went on to wire the planet around it, from the three new undersea cables and five cloud regions announced in early 2018 to the 250-terabit Dunant cable to France that came online in 2021.

The commercial payoff is visible in the related coverage too — once you own premium fiber everywhere, you can sell a cheaper Standard Tier that routes traffic over the public internet as a downgrade option, turning network ownership itself into a pricing lever against AWS and Azure.

First-order effects

  • Google's own services and Cloud Platform customers get lower latency and higher effective throughput inside its data centers, since the petabit-scale fabric removes inter-server bandwidth as the constraint on cluster-sized workloads.

Second-order effects

  • Rivals are pushed into matching capex: Google's cable-and-region expansion (Montreal, Netherlands, Los Angeles, Finland, Hong Kong) forces Amazon and Microsoft to keep buying or building equivalent subsea capacity rather than renting it.

Third-order effects

  • If the pattern holds, hyperscale cloud competition settles into an arms race over physical network assets — fiber, cables, regions — where the operator with the most owned bandwidth sets the price floor everyone else must subsidize against.

The trend: Cloud computing is consolidating around vertically integrated network owners, with each hyperscaler's private fiber and subsea footprint becoming the durable moat that software features alone can't replicate.