Topic
Peering and Transit
Within the Topic facet, Peering and Transit topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.
Europe and Middle East Regional ISP Trends
Trifle's pioneer story needs a current operator-control map
Trifle's pioneer story needs a current operator-control map intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The Europe…
Story
LACNIC's Four-Vendor BGP Claim Needs the Configuration Column
One malformed Prefix-SID attribute reportedly met three different actions as it crossed the Internet: discard, propagation and session reset. LACNIC's new routing-security article makes the divergence visible. To make it reproducible, the comparison now needs to name the release…
Europe and Middle East Cloud Services Trends
The regional boundary behind Genesis Cloud’s GPU capacity
Genesis Cloud’s accelerator inventory becomes useful capacity only when networking, data placement, images, security controls and recovery procedures can support the intended workload. Its documented regional boundaries therefore turn a catalogue question into an architectural…
Europe and Middle East Regional ISP Trends
VOLZ’s 120-hour node-power claim needs a failure-domain ledger
VOLZ has put an unusually concrete number beside network continuity: batteries at 14 large Kyiv communications nodes that the operator says can sustain power for 120 hours, backed by generators for emergencies. The number is valuable because it identifies a real control. It is…
APRICOT
The Conference Network Is APRICOT’s Strongest Constitution
APRICOT’s temporary production network is a more testable statement of institutional values than a conference slogan. Its designs, routes, client measurements and failures show what the summit attempts to operate—without proving universal compliance or regional adoption.
IETF
BGP Maintenance Needs Two Different Meanings of Graceful
Two change tickets can both say “graceful” while asking the network to do opposite things. One must move traffic away before a link or router stops forwarding. The other must keep forwarding on existing entries while the BGP control plane restarts. Treating those operations as…
Story
LACNIC’s 11 IXP Collectors Need a Vantage-Point Receipt
LACNIC has opened a useful window onto local routing: eleven BGP collector views, public MRT files and charts of prefixes, origin networks and paths. The problem begins only when a window is mistaken for the landscape. The portal does not bind each result to the peer cohort…
IETF
Clarence Filsfils and the Segment List That Learned to Share an Address
An SRv6 path can be perfectly explicit and still carry waste: the same locator block repeated across instruction after instruction, plus zero padding that moves through the network without adding a decision. RFC 9800 removes that repetition. Its deeper achievement is to specify…
Leaders
Aaron Wendel and What Two Failed ARIN Proposals Reveal About Operator Power
Fourteen years apart, two public tallies put Aaron Wendel on the losing side of consequential debates about Internet number resources. The defeats are more revealing than a conventional success story: they show how practical operating knowledge enters policy, how commercial…
IETF
The connection is larger than the path: Multipath TCP keeps one byte stream across several routes
A phone leaves an office with a live connection on Wi-Fi and reaches the street on cellular. Ordinary TCP ties that connection to one path. Multipath TCP can keep the application on one ordered byte stream while the endpoints add, retire and prioritise TCP subflows underneath it.…
IETF
The quiet hour is only a forecast: ALTO makes traffic timing a published promise
A bulk transfer can wait for two in the morning. The harder question is why two in the morning should be cheaper at all. ALTO Cost Calendars let a network publish that expectation to an application. The calendar is useful precisely because it is not the network itself: it is an…
Global Institutional Trends
At DE-CIX, the Route Server’s Default Is a Market Rule
One BGP session can replace hundreds of bilateral introductions. That efficiency is real, but so is the delegation hidden inside it: the route server’s defaults, filters and exceptions help decide who can reach whom, under which evidence, and at whose operational cost.
NPNOG
Who opens the room? What npNOG-10's welcome order can—and cannot—prove
The first twenty minutes of a conference can reveal institutional relationships. They cannot, without supporting records, tell us who held the decisive authority.
IETF
The packet was marked before it was lost: ECN’s long argument about congestion
The most important moment in congestion control is easy to miss: a router can warn an endpoint while the packet is still alive. Explicit Congestion Notification turned that possibility into a protocol, then spent two decades exposing how much cooperation is required to make two…
NPNOG
One week, two institutions—and two edition numbers
<!-- BTW:SLUG:one-week-two-institutions-two-edition-numbers-npnog-sanog-38 -->
History
When the Warning Reached the Wrong Server: The History of Path MTU Discovery
In 2015, Cloudflare found that a TCP flow and the ICMP warning meant to repair it could enter the same data centre and still reach different machines. The path had stated its limit. The server handling the connection never heard it. That incident exposed the institutional bargain…
Global Regional ISP Trends
IPv6 Extension Headers Are Becoming a Path-Compatibility Tax
The address answers. Ping works. Then the transport header moves 64 bytes deeper into an otherwise valid IPv6 packet, and the path goes quiet. Basic reachability survived; optional capability met the smallest parser on the route. It is a compact demonstration of how a protocol…
CASE FILE
A database governed by its entries: who gets a vote in PeeringDB?
A legal business entity can cross PeeringDB's membership threshold with two credentials: an active account and a representative or role subscribed to the governance list. The vote that follows is real. It is also only the first layer of authority over a database whose daily…
History
The Stability Rule That Punished Recovery: Route Flap Damping
A mechanism built to protect 1990s routers from repeated BGP updates learned to remember change without understanding its cause. The result was an unusual distribution of power: a prefix holder could repair a route, while distant networks continued to treat the recovery as…
IETF
Enke Chen and the Route That Outlived Its Session
A BGP session can disappear while the forwarding state learned through it still works. RFC 9494 permits some of that old state to remain far longer than ordinary graceful restart—but it does not call the state current. It marks the route, lowers its preference, limits where it…