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.
Story
APNIC Will Put VRP History in REx. A Timeline Still Needs a Vantage Point
APNIC plans to show current and historical RPKI VRP information for an individual Internet number resource in REx. That could turn a specialist dataset into useful public memory. But a dated line is not self-explanatory: unless it names the observation, derivation and scope…
Story
RIPE NCC Is Running Four Security Programmes at Once. Their Handoffs Need a Public Map
RIPE NCC’s quarterly plan puts audit work, risk management, application security and monitoring on four adjacent lines, all marked “In progress”. That is useful disclosure, but not yet a view of how evidence moves between them. A small public handoff map would let members…
Story
AFRINIC's Bylaws Chair Is Also CEO Designate. The Review Needs a Role-Transition Record
Mike Silber will not take office as AFRINIC’s chief executive until 1 January 2027. But the constitutional review he was appointed to chair was still working one day after his designation was announced. That overlap is not proof of a conflict. It is a reason to publish the small…
Story
LACNIC's Election Recovery Defaults to ALL. One Email Search Reaches Vote, Nomination and Support Links
Convenience has a constitutional edge when the thing being recovered is not an account but a power. LACNIC’s newly published election code can use one email address to find three kinds of tokenised link. The missing record is not another log of clicks. It is a receipt showing why…
Story
ARIN's WhoWas Accepts an IPv6 Address. The History Still Needs a Capability Receipt
A request can be well formed, a report can have the right columns, and the archive behind both can still remain unproved. ARIN’s public record now makes all three propositions about IPv6 WhoWas look adjacent. What it does not provide is the small, dated receipt that would make…
Story
APNIC Has an ASN Endpoint and an Empty Changelog. They Do Not Prove the Same Release
APNIC Has an ASN Endpoint and an Empty Changelog. They Do Not Prove the Same Release intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
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…
Story
AFRINIC's 2026 Closure Data Spells Voluntary Two Ways
AFRINIC has done the useful thing by publishing reproducible statistics on closed memberships and returned number resources. But its current 2026 data place `VOLUNTARY` beside `VOLUNTART`, and the dashboard treats the two strings as different categories. That one-character split…
Story
LACNIC Asked for a Technical-Committee Charter. Its First Committee Ran the Registry.
LACNIC’s Board has found a sensible reason to create a technical committee and an equally sensible reason to fear one. Directors need a place to understand technologies that may reshape the registry. They do not need a second operations room. The distinction sounds obvious until…
History
RFC 2056 and the Fork in a Z39.50 URL
In 1996, RFC 2056 gave two URL schemes to Z39.50 because one locator could conceal two very different kinds of work. One scheme entered a continuing, stateful inquiry; the other attempted a tightly bounded retrieval of a server-identified item. The distinction is a small piece of…
Story
ARIN Can Attach a Ticket to an Org ID. That Does Not Make It the Organization’s Decision.
ARIN fixed a mundane but costly support problem: staff no longer need to begin every ambiguous question by asking which organization it concerns. The resulting Org ID selector gives a ticket context and a durable home. That is good service design. It also makes one distinction…
History
The Zero Handle Opened a Door. It Did Not Grant Entry
In 1996, RFC 2054 tried to remove two conversations that stood between an NFS client and its first useful file reference. Its answer was not a new permission system. It was a disciplined gamble: try the port most servers already used, try the newer protocol first, and present a…
Story
APNIC’s Priority Survey Has Three Bases: 1,039, 1,038 and 1,037.
APNIC asked its community to divide exactly 100 points among eight strategic activities. The resulting chart looks unusually complete: every point is accounted for and no priority overwhelms the rest. The publication trail is less settled. Three official artifacts attach three…
History
The Configuration Row Vanished. RFC 2051 Kept the Session Alive
RFC 2051 turned an obscure APPC management model into a durable lesson about evidence: the record of what should exist can disappear while the record of what is already running remains true.
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
RIPE Atlas Put Reconnects and Liveness Through One Event Processor. A Slow Backend Blocked Both.
A RIPE Atlas software probe could have working Internet access on 8 June and still be shut out of the measurement network after a routine disconnect. The public incident record explains why: reconnect work and controller-liveness evidence passed through the same event processor.…
Story
AFRINIC Calls 122 New Members a 4% Increase. The Baseline Is Missing.
AFRINIC’s statistics portal compresses five year-to-date counts into five whole-number growth labels. The figures look self-explanatory until one asks the ordinary questions behind any percentage: compared with what, at what time, under which inclusion rules, and rounded how? The…
History
The Unknown Attachment Was Not Text: RFC 2049’s Minimum Promise
MIME conformance did not mean that a mail program understood every format. In 1996 it meant something smaller and more useful: decode the common transfer forms, preserve the distinction between text and opaque bytes, and retreat predictably when a type was unknown.
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…
Story
ARIN Waited for a Geofeed Standard. Its RDAP Help Still Does Not Claim It.
Two years ago ARIN tied a community request to a visible trigger: once the common RDAP geofeed standard was accepted, three named product surfaces would change. The standard is now RFC 9877. The useful question is no longer whether the IETF will finish the vocabulary, but how an…