Profile
Analysis
Analysis profile intelligence connects person, company, institution, and other entity coverage for readers comparing the subjects behind BTW.MEDIA reporting. The page helps compare public profiles, related events, evidence packs, role changes, operating footprints, governance exposure, organisational links, and market relevance while keeping organisation and people records distinct from ordinary news chronology. Readers can understand the subject behind the headline, the evidence supporting that profile, and the infrastructure or market relationships that make the profile relevant. They can see who or what the profile represents, which public sources support it, how it connects to companies, markets, governance bodies, or events, and what changes may deserve continued attention as the subject evolves.
Story
LACNIC’s BGP Case Counts 368 Route Peers. The Vendor Could Not Produce a Definitive Installation List.
LACNIC’s latest routing-security case is unusually rich in network evidence and unusually poor in application evidence. The route, certificate and attack window can be reconstructed in detail; the vendor still cannot say which installations accepted the malicious update. That gap…
Story
AFRINIC's Prefix Checker Can Supply the ASN From BGP. The Verdict Keeps Only the RPKI Time.
AFRINIC's Prefix Checker Can Supply the ASN From BGP. The Verdict Keeps Only the RPKI Time. intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
Story
APNIC Prop-173 Would Make Every Directory Query an Agreement. The Response Would Carry No Version.
An acceptable-use policy can change while the response governed by it remains in a cache for years. APNIC's prop-173 would make ordinary WHOIS, RDAP and web queries subject to a clear, versioned policy and would tell users that querying or using the service means agreeing to…
Story
RIPE Atlas Firmware 5130 Added an OpenWrt Hardware Architecture. The Rollout Needs More Than a Version Number
Firmware 5130 gives RIPE Atlas a new `openwrt-hwprobe` architecture for next-generation firmware on existing hardware probes. That is a concrete engineering change, not merely a roadmap line. Yet the number 5130 can identify a release without proving which source, toolchain…
History
One Class A Subnet Could Defeat the Default: RFC 2036’s Compatibility Test
Opening unused Class A space in 1996 was not just a registry decision. It changed what every provider, customer domain and peer had to mean by a route: once a small component of an old classful parent appeared, inherited assumptions could send the rest of that parent away from an…
Story
AFRINIC Can Close a Support Ticket After About Ten Working Days. It Never Ranks the Risk.
A registry is right to ask who is touching its records. AFRINIC's public Contractual Obligations Check makes that defence concrete: the sender must be registered, the member must be in good standing and a signed agreement must be on file. The problem begins after a check fails.…
Story
LACNIC's Open-Source Election Lookup Puts the Email Address in the Request Path
LACNIC's open-source election system authenticates a participation lookup before returning its answer. Yet the documented interface has already placed the entity identifier in the part of the request most likely to be copied by infrastructure. The distinction is not a disclosed…
History
The Org Chart Was Not the Decision Log: RFC 2028 and the Map of IETF Responsibility
In 1996, RFC 2028 put the people and institutions of the IETF standards process into seven public pages. The map made responsibility easier to locate. It did not prove that any named role had acted, that a record was complete, or that the same allocation of authority still…
Story
A Space IPv6 Draft Gives Every Planet Up to Five RIR Prefixes. It Never Defines the Region.
The appealing part of a new space-address proposal is that it does not start a sixth registry from scratch. The harder part is hidden in two words. Applicants would use their “appropriate RIR”, but a moving spacecraft has no obvious place on a map built for terrestrial service…
Story
ARIN Can Trace an API Key. Its Dashboard Still Cannot Say What the Key Is For
ARIN tells customers to separate credentials so that actions can be traced, but its public key-management guide says those credentials are identified only by prefix and creation date. The missing description field is a small interface omission with a large operational…
History
The Tokens Diverged. The Endpoint Was Still Unproven: RFC 2023
RFC 2023 gave early IPv6-over-PPP links a precise local bargain: establish the data link, enter PPP’s network phase, negotiate different 32-bit tokens, and only then admit IPv6. Every receipt in that sequence stopped short of identity, ownership, reachability and delivery.
Story
APNIC Will Automate Route-Record Alignment. The Roadmap Does Not Name the Conflict Winner
“Alignment” sounds like database housekeeping. In APNIC’s Q3 2026 roadmap, it means something harder: deciding how resource holdings, a route-management template, Whois route objects and RPKI authorizations should change when they disagree—and preserving enough evidence to show…
Story
ARIN Let Consultant Hiring Advance Before the Control Plane Vote.
ARIN’s draft Board minutes preserve an awkward but legitimate sequence: outside-consultant hiring could keep moving while the Registry Control Plane itself awaited a detailed plan and a later approval meeting. The issue is not whether preliminary expertise is useful. It is how…
History
The Catalogue Was Verified. The Training Material Could Still Be Gone: RFC 2007
In 1996, a volunteer directory tried to keep Internet training reusable by recording three different clocks: when a resource changed, when its catalogue entry changed, and when someone last checked it. RFC 2007 shows why those dates were useful—and why none was a promise about…
Story
AIRRS Sends “amp;profile”. RIPEstat’s Real AFRINIC Profile Returns 500
A regional statistics portal can look complete while the choice that is supposed to make it regional never reaches the service under the expected name. AIRRS currently demonstrates that uncomfortable distinction: seven tabs can arrive, yet the evidence says they came through…
Story
APNIC 62 Had Seven Policy Proposals. Two Had No Consensus Call.
APNIC’s conference report does something more useful than recording winners and losers. It preserves a third procedural state. Prop-165 and prop-172 were discussed, but no consensus call was held. The next record should explain where that state leads without pretending it means…
History
The MIB Saw the Binding. It Did Not See the Journey: RFC 2006
RFC 2006 gave operators a disciplined view of Mobile IP’s moving parts. Its tables, counters and alert could expose what a management agent believed had happened, while leaving delivery, identity, authority and continuity outside the frame.
Story
AFRINIC’s Co-Chair Calendar Leaves 7½ Days After Nominations Close. Its Suggested Vetting Period Is Two Weeks.
The number is not evidence of a rushed decision. It is evidence of an unexplained join. AFRINIC has published a precise closing time, a precise slate time and an indicative vetting duration that does not fit between them unless some work happens before the door closes.
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.
Story
RIPE’s IPv6 PI Draft Reserves Growth Space. Partial Transfers Can Make It Unusable.
RIPE’s current IPv6 PI proposal tries to make future growth easier by reserving a larger nibble-boundary envelope around a new assignment. Its own impact analysis identifies the catch: if the assigned block can be transferred in pieces, the untouched reservation may no longer be…