Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
History
The Host That Learned a Small Routing Table: How IPv6 Ranked First Hops
IPv6 did not make every host a routing speaker. It let a router disclose a few expiring choices, then left the host to combine longest-prefix logic, observed reachability and local policy. The useful invention was as much the boundary as the route.
CASE FILE
The Filter That Crossed the Session but Not the Boundary: BGP ORF and the Authority to Ask for Less
Consider an illustrative customer changing its inbound prefix-list from a full table to a narrow feed. Its router immediately looks cleaner: unwanted routes disappear from the local RIB. Yet the provider may still be generating and transmitting every one of them, only to have the…
IETF
Linda Dunbar and the Directory That Must Not Invent a Neighbour
A virtual machine moves between racks, but an edge switch still holds yesterday's answer: the address is reachable through the old location. The reply can be perfectly formatted, delivered by an authenticated channel and still send traffic to the wrong place. Linda Dunbar's…
History
The Server That Counted Before It Answered: Why HTTP Needed 429
A request can be valid, authorized and still arrive after its allotted share has gone. HTTP 429 made that refusal legible while leaving the decisive questions—who is counted, across what scope and at whose cost—with the server that owns the capacity.
CASE FILE
The Session Was Established and Carried No Routes: RFC 8212 and the Authority of Explicit Policy
The following replacement-edge maintenance scenario is illustrative, not a reported incident. The new edge shows `Established`; KEEPALIVEs advance and the peer has been stable for twenty minutes, yet the IPv4 table is empty and nothing has been advertised. The transport is…
History
The Silence That Licensed an Address: What IPv6 DAD Could Prove
IPv6 DAD based an important decision on a negative observation: no rival appeared during a bounded local probe. The protocol had to say exactly how far that silence could reach.
Story
RIPE Atlas Closed a Probe-Assignment Incident Without a Measurement Ledger
A missing vantage point can describe the Internet, the probe or the scheduler. On 18 August, RIPE Atlas made the third possibility explicit: measurements using an area choice other than `worldwide` had trouble receiving probes. The backend was fixed; the public record still does…
CASE FILE
The Session Fell Silent but Left a Reason: BGP Shutdown Communication and the Authority to Explain a Closure
The peering drops at the scheduled minute. This time the receiver does not see only `Cease`. The terminal NOTIFICATION also carries a compact ticket reference, a reason and an expected maintenance interval. That text can remove hours of ambiguity. It can also be forged, exposed…
CASE FILE
Both Connections Reached OPEN; Only One Could Remain: BGP Collision Detection and the Authority of a Stable Identifier
Both routers dial at once. Two TCP connections complete between the same pair of addresses, and each carries a valid BGP OPEN. Neither transport is broken. Yet one configured peering cannot keep two competing finite-state machines and two versions of its session history. BGP…
History
The Write That Had to Name Its Past: Why HTTP Needed 428
A write request can be perfectly formed and still be too ignorant to trust. HTTP 428 gave an origin a precise way to demand the missing fact: which version of this resource did the writer actually see?
History
The Name That Chose a Service: How DNS SRV Found Servers
A domain once led clients toward one address and a remembered port. DNS SRV made service location an explicit, bounded choice among hosts.
CASE FILE
The Peer Kept Sending but Stopped Receiving: BGP SendHoldTimer and the Authority to End a One-Way Session
The neighbour is still sending KEEPALIVEs, so the BGP dashboard remains green. Yet its TCP receive window has collapsed to zero and none of the local withdrawals can leave the socket. The session is established, inbound liveness is real, and the route information held by the…
CASE FILE
The Route Was Accepted So Packets Would Die: BGP BLACKHOLE and the Authority to Destroy Reachability
A blackhole announcement is a rare routing message whose success is measured by non-delivery. That inversion can save a network during a DDoS attack, but only if the right to sacrifice one destination is narrower, more observable and more reversible than the emergency that…
CASE FILE
The Session Could Carry It; the Next One Could Not: BGP Extended Messages and the Authority of a Shared Size Budget
A BGP speaker accepts a 12-kilobyte UPDATE, selects the route and prepares to propagate it. The next neighbour accepts only the old 4,096-octet envelope. Nothing is malformed, the policy still prefers the path and the prefix is valid—yet the complete announcement cannot cross the…
IETF
Hannes Gredler and the OSPF Link That Had to Drain Both Ways
An operator makes one end of a circuit prohibitively expensive, watches routes leave, and calls the link drained. Yet packets can still enter from the neighbour because OSPF does not advertise one indivisible circuit: each router originates its own directional state. Hannes…
Story
LACNIC's ASO AC Result Became Official Without a Closure Receipt
At 18:00 UTC on 20 August, one public election table crossed a consequential boundary. The names and 144 votes did not change. The page's status did: the provisional result became the official result after two audit windows. What did not appear beside that new status was the…
History
The Request That Had to Wait for Proof: Why HTTP Needed 425
TLS 1.3 let returning clients send requests before a new handshake finished. HTTP 425 made replayable early data wait without changing the request itself.
CASE FILE
The Monitor Saw the Route, Not the Packet: BGP BMP and the Authority of a Control-Plane Witness
A monitoring feed can be accurate and still support a false conclusion. BGP Monitoring Protocol gives operators structured views of routes before policy, after policy, at export and after selection. Those views are not interchangeable. The first duty of a BMP system is therefore…
CASE FILE
The Metric Crossed the AS Boundary: BGP AIGP and the Authority to Define One Interior Cost
Two autonomous systems can belong to one operator and still speak different mathematical languages. If one calls a 10-millisecond link “10” and the other calls a high-capacity link “10,” adding their metrics produces a precise number with no coherent meaning. BGP AIGP can carry a…
History
The Alias That Could Not Move Authority: DNS DNAME
DNAME redirects descendant lookups by replacing one suffix. The owner, zone apex and NS delegation stay put even when many queries follow the new subtree.