Content Type
Analysis
Within the Content Type facet, Analysis intelligence gathers BTW.MEDIA articles that share the same editorial format, helping readers compare briefings, profiles, risk notes, market analysis, and event coverage without mixing different kinds of evidence. The page explains how this content type frames internet infrastructure events, company movements, governance decisions, operational signals, and public evidence across the site. Readers can compare which actors or infrastructure systems appear most often, how source quality changes interpretation, and whether the material is a durable profile, a time-sensitive event, a strategic market signal, or a governance development. The result is a useful search page for operators, investors, customers, analysts, and policy stakeholders who need to understand the consequence, timing, and evidence behind similar article formats.
History
The State Table Was Also a Kill Switch: RFC 2012
In RFC 2012, a manager could inspect a TCP connection in one moment and erase its host-side existence in the next. The same row that reported state also accepted `deleteTCB(12)`, turning a table of observations into a remote intervention surface whose consequences extended well…
Story
A Direct Route Fixed a 150ms Detour. It Has No Backup.
A route from Britain toward Denmark appeared to turn the Atlantic into a roundabout. The first explanation blamed the wrong control point. Operators then found a short European path, traced the detour to export and peering choices, and installed a direct route whose lack of…
Story
AFRINIC Crossed an ASN Block Boundary With 52 Earlier Numbers Absent From the Ledger
AFRINIC Crossed an ASN Block Boundary With 52 Earlier Numbers Absent From the Ledger intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
History
The IP MIB Passed Compliance. IPv6 Was Still Outside the Frame: RFC 2011
A green conformance result can be perfectly accurate and still answer the wrong operational question. RFC 2011 made the surviving MIB-II IP and ICMP entities orderly under SMIv2. Its own IESG Note also warned that the order stopped at a four-octet address. The document is a…
Story
APNIC's Governance Score Is 77%. Its Don't-Know Average Is 20%.
APNIC's new survey does not produce one verdict on governance. It produces a positive score among people able to judge eight claims, and a separate measure of how often members could not judge them. Any decision that carries the first number forward should carry the second one…
Story
RIPE NCC’s New IPv6 Exam Lasts 60 Minutes. Its Badge Will Last Three Years
A short private assessment is being asked to support a long public claim. Before RIPE NCC launches its IPv6 Advanced certificate, it should make the badge’s changing technical scope visible without exposing a single exam question.
History
The Root Server Became a Stack of Receipts: RFC 2010
RFC 2010 turned confidence in a capable root-server volunteer into inspectable duties—from checksums and clocks to capacity, contacts and outage notices—without deciding who deserved the role.
Story
One Recusal and One No Would Block AFRINIC GovCom Advice
AFRINIC’s five voting members do not approve formal advice through an ordinary supermajority. If one member recuses, a 3–1 vote clears the approval floor and still fails the separate dissent test.
History
The Packet Reached the Area. It Had Not Reached the Person: RFC 2009
RFC 2009 tried to fit a physical polygon inside a logical Internet address by routing approximately first and deciding precisely at the edge—a scaling bargain that made location, delivery and outcome separate facts.
Story
LACNIC Budgets a $390,000 Operating Gap. Financial Results Close All but $87,000 on Paper
A budget can show a small loss while concealing three different movements: the recurring cost of running the registry, the accounting result of a portfolio and the cash that actually entered or left the institution. LACNIC’s 2025 accounts show why its 2026 plan needs those…
Story
ARIN Put Three Candidate Pools on One Slate. Only Two Go to Members
ARIN's 2026 slate is a single page with three sets of candidates and two different decision makers. General Members choose the Board and Advisory Council. Trustees choose this year's NRO Number Council representative.
Story
AFRINIC’s Draft Says Slides Must Match the Proposal. A Mismatch Creates a Version That Cannot Count
A policy meeting can be perfectly public and still leave its decisive entity obscure. AFRINIC’s proposed working-group rules require presentation slides to match the submitted proposal; if they differ, an updated version must go to the mailing list even when its changes will not…
History
The Address Was Borrowed. The Route Was Never Included: RFC 2008
The Address Was Borrowed. The Route Was Never Included: RFC 2008 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
APNIC's Honeynet Logged 1.27 Million Events. That Is Not 1.27 Million Attacks
An APNIC 62 presentation turns one deliberately exposed server into a useful security instrument. Its headline, however, moves between attacks, attack events and events—three labels that cannot safely share one number.
Story
RIPE Atlas Counts Probe Farming by a BGP Prefix. The Cohort Can Move Without the Probe
A probe can stay on the same shelf, under the same account and on the same access line, yet acquire different neighbours for an admission rule. RIPE Atlas limits software probes partly by the IP prefix “as seen in BGP”. That is a defensible way to protect a shared measurement…
Creators
Ivan Pepelnjak and the discipline of testing network automation
Ivan Pepelnjak’s career runs from Slovenia’s early internet and exchange infrastructure to ipSpace.net and the open-source netlab project. His recurring argument is practical: automation becomes trustworthy only when intended state is modelled explicitly, vendor claims are…
History
One Router Drew the Path. No Router Needed the Whole Map: RFC 1992
Nimrod’s sharpest scaling decision was to abandon the comforting fiction of a single, complete map: knowledge could be partial, private and stale, provided that a chosen path did not depend on every router improvising from a different picture.
Story
LACNIC’s ASPA Explainer Cites a Moving Percentage Without a Snapshot
LACNIC’s ASPA Explainer Cites a Moving Percentage Without a Snapshot 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.…
Story
AFRINIC's IPv4 Summary Rose by Two. One Reserved Block Split into Three
AFRINIC's daily file gained two IPv4 records on 9 September. The tempting story is two new allocations. The rows tell a more useful one: a conserved block changed shape.
History
The Grant Was Automatic. The Boundary Was Not: RFC 1988
RFC 1988 removed the need to ask Hewlett-Packard for the same narrow permission implementation by implementation. It did not remove the perimeter around that permission—or the switch that could end it.