The Borderless Table

How Fragile Trust Holds the Internet Together

The global internet is not a single unified network; it is a loose federation of roughly 75,000 independent physical networks known as Autonomous Systems (AS)—regional telecommunications carriers, national fiber backbones, university campuses, cloud data centers, and submarine cable operators—each identified by a unique Autonomous System Number (ASN). Physically, these networks bolt together inside windowless carrier-neutral colocation facilities called Internet Exchange Points, such as DE-CIX in Frankfurt or Equinix in Ashburn, Virginia, where yellow single-mode optical patch fibers link the border routers of one company directly to the border routers of another. Logically, however, the protocol that tells those 75,000 networks how to forward packets across the planet—the Border Gateway Protocol (BGP), originally sketched on three stained dining napkins by engineers Yakov Rekhter and Kirk Lougheed at an Internet Engineering Task Force meeting in January 1989—operates almost entirely on unverified word-of-mouth trust.

No single router on Earth holds a complete map of every physical wire and server on the internet. Instead, border routers exchange reachability announcements for blocks of Internet Protocol (IP) addresses written in Classless Inter-Domain Routing (CIDR) prefix notation. Under IPv4, every server address is a 32-bit binary number written as four octets (such as 208.65.153.238). A prefix written with a slash suffix /n specifies how many leading bits from left to right identify the network block, leaving the remaining $32 - n$ bits for individual host machines inside that block:

A /16 prefix locks the first 16 bits and covers $2^{16} = 65,536$ IP addresses; a /22 prefix covers $2^{10} = 1,024$ addresses; and a /24 prefix covers $2^{8} = 256$ addresses. Crucially, whenever a high-speed core router holds multiple valid BGP announcements in its forwarding table that match a destination IP address $D$, its silicon ternary content-addressable memory (TCAM) obeys an absolute, deterministic hierarchy before considering network distance or hop count: the longest-prefix match rule. Between two competing routes covering the same destination IP address, the router unconditionally selects whichever prefix $P_i$ has the greatest bit length $|P_i|$:

In a routing table, specificity trumps proximity, bandwidth, and ownership. If a network on the far side of the world announces a /24 block that falls inside another company's legitimate /22 block, every router on the internet that hears both announcements will immediately divert traffic toward the /24 announcer.

At 18:47 Coordinated Universal Time on Sunday, February 24, 2008, the government of Pakistan ordered domestic internet service providers to block access to YouTube after the video platform hosted clips the telecommunications ministry deemed blasphemous. Inside the network operations center of Pakistan Telecommunication Company Limited (PTCL, operating as AS17557) in Islamabad, engineers decided to block YouTube for Pakistani subscribers not by filtering domain names, but by injecting a local blackhole route into their domestic routers—a standard censorship technique that routes packets destined for a banned IP block into a null interface (null0), where they are silently discarded.

That evening, YouTube (AS36561) was legitimately advertising its main video servers from California to the global internet as the aggregate block 208.65.152.0/22 (1,024 addresses spanning 208.65.152.0 to 208.65.155.255). To intercept domestic requests to 208.65.153.238, PTCL engineers created a more specific 256-address sub-block—208.65.153.0/24—pointed to their internal blackhole. By operational mistake, PTCL failed to apply an outbound route filter on its international BGP peering session with its upstream transit carrier, PCCW Global (AS3491) in Hong Kong, and PCCW failed to check whether Pakistan Telecom had any legal right to announce YouTube's IP range.

Within 110 seconds of 18:47:45 UTC, PCCW propagated AS17557's /24 announcement to every Tier-1 backbone carrier in Asia, Europe, and North America. Because $|P| = 24$ is strictly longer than YouTube's $|P| = 22$, routers in Tokyo, London, Frankfurt, and New York—including routers inside neighboring California networks a few miles from YouTube's headquarters in San Bruno—instantly overwrote their forwarding tables. Global video requests from hundreds of millions of users were diverted off North American and European backbones, funneled down submarine fiber cables across the Mediterranean and Indian Ocean into Hong Kong and Karachi, and dumped into PTCL's null interface in Islamabad, saturating Pakistan's international bandwidth and taking YouTube dark worldwide.

At 20:07 UTC, YouTube's network engineers detected the hijack and fought back using the only weapon BGP recognized: prefix length. First, YouTube announced its own 208.65.153.0/24 route; with the prefix lengths tied at 24 bits, routers in North America and Europe fell back to the secondary tiebreaker (shortest AS hop count) and restored western traffic, though Asian networks closer to Hong Kong remained trapped. Thirteen minutes later, at 20:18 UTC, YouTube split its /24 block into two even more specific /25 prefixes (208.65.153.0/25 and 208.65.153.128/25, containing $2^{32-25} = 128$ addresses each). Because 25 bits beats 24 bits, global routers pivoted back to California, restoring service minutes before PCCW finally severed Pakistan Telecom's rogue announcement at 21:01 UTC.