The Pieces of the Backbone
| Piece | Job | Real-World Example | Home Impact |
|---|---|---|---|
| Tier-1 backbone networks | Carry traffic across continents; peer with each other for free | Lumen (CenturyLink), Cogent, NTT, AT&T IP backbone | Speed between countries depends on Tier-1 capacity and peering |
| Transoceanic fiber routes | Physically connect continents with submarine cables | MAREA (US–Spain), FASTER (US–Japan) | Intercontinental latency floor: ~70ms US–Europe, ~120ms US–Asia |
| Core routers | Forward millions of packets per second across backbone links | Cisco CRS, Juniper PTX | Path changes appear as hop latency changes in traceroute |
| Autonomous systems (AS) | Independently numbered networks that exchange routing information | Your ISP is one AS; Google is another (AS15169) | Every internet path crosses multiple ASes |
| BGP | Border Gateway Protocol — the routing protocol that glues ASes together | Runs on every router at network boundaries | BGP misconfiguration can briefly reroute global traffic |
| Internet Exchange Points (IXPs) | Neutral facilities where networks peer directly instead of using transit | DE-CIX (Frankfurt), AMS-IX (Amsterdam), NYIIX (New York) | Local IXP peering reduces latency to CDN edges and streaming servers |
| CDN edge nodes | Cache popular content at hundreds of locations close to users | Cloudflare, Akamai, Netflix Open Connect | Netflix video may come from a server inside your ISP, not Netflix HQ |
How a Packet Moves from Your Screen to a Server
The journey of a single request to load a web page:
- Device to router: packet leaves your laptop via Wi-Fi or Ethernet to your home router (microseconds)
- Router to modem: the router forwards it to your cable modem or ONT (microseconds)
- Last mile: your ISP's network carries it from the neighborhood node to their aggregation point (1–5ms typical for cable or fiber)
- ISP core: the aggregation point forwards it into your ISP's regional and national backbone network
- Peering or transit decision: BGP determines whether the destination is reachable via a peering link (free, often local) or a transit provider (paid, goes further)
- IXP or private peering: if the destination network peers at a local IXP, traffic crosses the exchange switch — potentially ending the backbone journey here
- CDN edge: if the content is cached at a CDN node near you, the packet never reaches the origin server
- Origin server: for uncached or dynamic content, the packet continues through one or more additional backbone networks to reach the data center
Submarine Cables: The Physical Backbone Across Oceans
Transoceanic internet traffic physically travels through optical fiber cables lying on the ocean floor. Key facts:
- There are over 400 submarine cable systems worldwide carrying nearly all intercontinental internet traffic
- A single modern cable can carry 200+ Tbps using dense wavelength division multiplexing (DWDM)
- Light travels through fiber at roughly 2/3 the speed of light in vacuum — the physics of this sets the minimum latency floor between continents
- US–UK minimum latency is about 70ms round-trip; US–Japan is about 120ms — no amount of upgrading can beat physics
- Cable cuts (from anchors, earthquakes, or fishing trawlers) do happen; traffic reroutes through other cables via BGP, usually within minutes
Why CDNs Changed the Backbone
Before CDNs, every video stream from Netflix headquarters had to cross multiple backbones to reach every viewer. Netflix now operates Open Connect, a CDN that places servers inside ISP networks worldwide. The same video file is delivered from inside your ISP rather than from California — the backbone never sees that traffic.
This pattern — caching content close to users — now handles the majority of consumer internet traffic. YouTube, Netflix, Facebook, and Cloudflare collectively serve traffic that previously would have crossed backbone links many times over. When one of these CDNs has a problem, it looks like "the internet is slow" to affected users.
How Backbone Problems Show Up at Home
Home users see backbone issues as symptoms that don't match local explanations:
| Symptom | Likely Backbone Cause | How to Confirm |
|---|---|---|
| One service slow, others fine | Congested peering link between ISP and that service's CDN | Test the same service via VPN — if it's faster, the ISP's peering is the issue |
| International sites slow, domestic fine | Submarine cable congestion or routing detour | Run traceroute; look for high-latency hops at transoceanic entry point |
| Everything slow at same time daily | Transit or backbone link congestion during peak hours | Compare morning vs evening speed tests; if evening is consistently slower, it's capacity |
| Sudden latency spike to one game server | BGP reroute changed the path — more hops or longer route | Run pathping or MTR to the game server; look for where latency jumps |
| Complete loss of one country or service | BGP misconfiguration, DDoS, or cable cut | Check downdetector.com; test via mobile data on a different carrier |
Peering vs Transit: Why It Matters for Your Speed
When your ISP sends your traffic to another network, it either peers (free exchange, usually through an IXP) or buys transit (pays a backbone provider to carry the traffic). The implications:
- Well-peered ISPs deliver video, gaming, and CDN traffic over short, fast paths with lower latency
- Poorly-peered ISPs route traffic through transit providers — adding latency, extra hops, and potential congestion points they do not control
- When your ISP and Netflix peer at a local IXP, Netflix traffic may arrive with 5ms latency; via transit, it might be 40–60ms
- This is why two ISPs in the same city offering the same Mbps can have very different real-world streaming and gaming experience
Frequently Asked Questions
Is there one internet backbone?
No. The backbone is a collection of many independently operated networks connected through peering and transit agreements. No single company owns or controls the global backbone. Tier-1 networks like Lumen, Cogent, NTT, and AT&T form a voluntary mesh of mutual peering that makes all of them reachable to all others without payment to any third party.
Does my home internet traffic always cross the backbone?
Not always. Traffic to a CDN node inside your ISP's network never leaves the ISP. Traffic to a service that peers at a local IXP only crosses the exchange switch — a few microseconds of travel. Long-haul backbone links are only needed for truly distant or poorly-peered destinations, which is increasingly uncommon for popular consumer services.
Who controls the internet backbone?
No single organization. Different pieces are controlled by different parties: telecom carriers own the fiber routes; IXPs are often neutral nonprofits (like AMS-IX) or commercial operators (like Equinix); cloud providers like AWS, Google, and Microsoft own their own private backbone networks; CDN operators run distributed edge infrastructure. ICANN coordinates DNS and IP address allocation, but does not control traffic or routing.
Can backbone problems be fixed by upgrading my internet plan?
No. Backbone congestion, poor peering between your ISP and a service, or a submarine cable cut are outside your home network entirely. Upgrading from 200 Mbps to 1 Gbps does not help when the bottleneck is a congested peering link between your ISP and Netflix. The correct response to backbone problems is either switching ISPs (if one ISP has better peering with the affected service) or using a VPN that exits at a location with better routing to the destination.