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.
IETF
The Drop Rate Was Historical. The Control Boundary Still Matters: RFC 7872
RFC 7872 recorded substantial loss for several IPv6 extension-header probes in 2014–15. Its enduring value is not a percentage that can be carried into 2026; it is the disciplined separation between what a probe observed, where a path might have discarded it, who could change…
Story
The Route Was Absent. The Traffic Still Found It: APNIC 62’s BGP Neighbor Problem
A route-origin filter can leave an operator’s table clean while a downstream neighbor forwards toward the rejected destination. An APNIC 62 presentation made that uncomfortable distinction concrete. The useful response is to preserve separate evidence of received routes, local…
IETF
The Router Answered for the Exit. The Link Was Still Unproven
RFC 9703 lets MPLS Ping and Traceroute ask whether an EPE-SID reaches the peer association named by its Target FEC Stack. The reply can validate an egress role, and sometimes the observed incoming interface. It cannot make a skipped interface check, an unreconciled controller…
Story
ARIN’s Legal RPSL Still Produced a Partial Mirror Answer
A recursive query returned seven ASNs. The reference described in ARIN’s public suggestion contained far more. Nothing in that contrast required the routing policy to be invalid: the failure could sit in the journey from a logical set, through one very long physical line, into a…
Latin America and Caribbean Institutional
NIC.br’s IX.br: access options are not a recovery test
A network’s own exchange port and a shared connection describe different ways to reach IX.br. Neither description, on its own, establishes what remains usable during a failure. The operational question is which dependencies an alternative avoids—and who can put it to work.
IETF
The Reply Crossed Three Domains. The Proof Did Not
RFC 9716 gives an SR-MPLS echo reply a route home when ordinary IP reachability ends at a domain boundary. Its label stack can be supplied in advance or assembled border by border. That makes inter-domain diagnosis practical; it does not turn one returned echo into proof that the…
IETF
The Orbit Said the Link Was Ready. The Network Had Not Agreed
RFC 9717 turns orbital predictability into a routing advantage without confusing a forecast with an observation. Its proposed satellite architecture can prepare for scheduled change, but a schedule, a computed SID list and even a successful install receipt remain different claims…
IETF
The Clock Agreed. Did the Traffic? Auditing RFC 9722 Recovery
RFC 9722 gives recovering EVPN peers a common instant for rerunning Designated Forwarder election. That is a precise control-plane promise—not evidence that clocks, forwarding entries and customer packets all crossed the boundary together.
History
Anja Feldmann and the Traffic Matrix No Single Link Could Reveal
A red link on a network map looks like an answer: this is where the load is. For Anja Feldmann and her collaborators, it was only the start of the question. The counter could not say which demands had converged there, which routing decisions had brought them together, or where…
Story
AFRINIC’s Uganda Anycast Node Is Two Services, Not One
AFRINIC’s Uganda Anycast Node Is Two Services, Not One 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 Story…
History
Elise Gerich and the Public Record Behind Private Routes
Routers could tell one network what another network could reach. They could not explain what the other network meant to announce, what it was prepared to accept, or whether the two intentions were compatible. Elise Gerich’s work around the Routing Arbiter belongs to the history…
History
Stephen Wolff and the Boundary Between a Public Backbone and a Market
A packet could not explain whether it served scholarship or commerce. NSFNET nevertheless had to draw that distinction while it was becoming the principal American research backbone. Stephen Wolff’s most revealing contribution was to treat commercialization and privatization as…
Story
RIPE NCC Lets Operators Sign ASPAs Without Showing the Providers It Sees
RIPE NCC has made ASPA signing possible and tells operators to list every real upstream. Its public guide also says the Dashboard offers no BGP-derived hint about who those upstreams might be. The missing interface is not an automatic answer but an evidence receipt that helps a…
History
The Registry Issued the Address. RFC 2050 Refused to Promise the Route
In 1996, an organisation could receive globally unique address space, appear in the public registry and still lack the one thing a casual reader might assume came with both: a route across the Internet. RFC 2050 made that limit explicit because the registry was only one actor in…
Story
LACNIC Counts 2.223 Billion BGP Messages. Its Family Table Totals 853 Million Updates
Two sums on LACNIC’s noisy-BGP study close perfectly. A third opens a 1.37-billion-count question. That does not make the research wrong; “messages” and “updates” may describe different stages. It does make the missing bridge between raw RIS files and the published tables the…
Number Resource Society
AS211513: What the public record can—and cannot—establish about EBL
AS211513: What the public record can—and cannot—establish about EBL 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…
IETF
The Reply Came Back. It Did Not Prove the Path Was Measured: RFC 9779
RFC 9779 gives operators a standards-track way to measure loss and delay on SR-MPLS links and policies. Its most important operational lesson is less comfortable: a valid response can arrive by a route different from the traffic direction under examination. Protocol success, path…
Global Regional ISP
ROYA’s AS210837: The Evidence Chain Between Network Identity and Operation
ROYA’s AS210837: The Evidence Chain Between Network Identity and Operation 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…
North America Cloud Services
Motorola Cloud Services Networking is visible in the routing table—but who controls the service behind it?
Motorola Cloud Services Networking is visible in the routing table—but who controls the service behind it? intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…
Story
RIPE NCC’s AuthDNS Ledger Counts 43 Nodes but Not the Eyeball Coverage They Deliver
RIPE NCC has made the objective unusually clear: put AuthDNS where poorly served networks can actually reach it. Its public inventory can show that 43 hosted instances are operational. What it cannot yet show is whether each new map pin changed the anycast catchment that matters.