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
The 92 Hours Came Back. APNIC’s Repair Record Did Not.
The 27 October archive snapshot was missing 92 hours; today’s directory contains them all. A chart rebuilt from the current files covers 92 more hourly intervals than one built from the old copy. APNIC still publishes no repair status for each interval.
Story
A Fresh RIPEstat Query Can Still Return Older Data
RIPE NCC’s 20 October status notice says data freshness varies by RIPEstat API endpoint. One official Looking Glass response makes the distinction tangible: a request at 18:04:43 UTC returned a latest observation stamped 12:13:37 UTC.
Story
ARIN survey shows a larger appetite for better service, but fee stability still leads
In the 2026 survey, 28% chose higher fees for higher service, up from 12% in 2023. A larger 59% still preferred the same fees and service.
Story
RIPE's IPv6 proposal adds an LIR closure clause beside an existing procedure
A local Internet registry (LIR) can face two separate questions when it closes: what happens to its service agreement and how its number resources are handled. RIPE NCC’s new IPv6 proposal names both, while existing RIPE-858 sets out separate procedures without explaining how the…
Story
AFRINIC logged 17 hours of MyAFRINIC access trouble without defining its scope
The status record gives the incident a start and an end, while the component list labels the portal operational. Neither says which member workflows were affected or how recovery was verified.
Story
At APNIC, winning a seat will not always mean winning three years
A staggered change of terms will make council turnover easier to predict. Finding the people who can contest those seats is a different job.
Story
Timor-Leste’s IXP Needs a Public Handover Record
An exchange can be installed with outside help and still depend on outside help to keep it running. Timor-Leste’s public record is now detailed enough to show why the transfer of routine responsibility deserves its own evidence.
Story
RIPE RIS Plans a Finer MRT Clock. The Records Need Provenance.
RIPE NCC’s Q4 plan would add subsecond timestamps to MRT files. That can distinguish records now stamped to the same second; it cannot, by itself, tell researchers how accurate a collector’s clock was or whether two collectors agreed.
Story
Digitel’s IPv6 Transition Had a Second Clock in Its Records
Venezuela’s IPv6 rule measures a network’s ability to carry the protocol. Digitel’s account points to a separate test: whether its subscriber records could identify the address used at a particular time. The public evidence does not show that the rule prescribed a CDR field.
Story
RIPE’s space-address draft names the NRO. Who sets the policy?
A September Internet-Draft requests IPv6 space for use beyond Earth and gives the NRO a role in structuring and distributing it. The institutional handoff remains unspecified: how would that coordination connect to the separate policy processes of five RIR communities, including…
Story
APNIC’s 70% KSK signal does not count the users at risk
APNIC Labs’ sentinel tests and Verisign’s resolver reports both tracked readiness for the 2026 root KSK rollover, but they sampled different populations from different vantage points. Neither percentage is a headcount of people who could lose DNS service.
Story
AFRINIC’s election results disclose rank, not the vote margins
The June 2026 results show who received longer terms in two ballot contests, but not how many votes separated the candidates or how many eligible voters took part. The guidelines say the Nomination Committee should publish final results and statistics; the pages reviewed show the…
Story
FRIDA’s 2026 Call Cut Its Menu in Half. The Application Data Cannot Explain the Shift
FRIDA moved from four thematic categories and grant and award tracks in 2025 to two categories and grants alone in 2026. The new cycle drew 57 applications, but its published figures do not explain why the invitation changed or how reviewers reached the final mix.
Story
LACNIC’s Board Ties Comisión Fiscal Access to Possible Financial Impact, but Does Not Define the Test
A sentence in LACNIC’s March 2025 Board minutes describes a private route from masked meeting material to the Comisión Fiscal. The route depends on possible financial impact. The record does not explain how that trigger is judged, and it does not show that any passage was…
Story
ARIN Closed the Suggestion; the URL Token Still Works
ARIN has delivered the safer authentication path that a community suggestion requested four years ago. The suggestion is closed, yet the older URL method remains accepted and has no public retirement date in the material reviewed here. That is not evidence of a breach or of slow…
History
The Pacific Circuit Was Only One Leg: TransPAC’s 1998 Link to Asia
The first TransPAC connection did not turn a Pacific cable into a ready-made Internet for every university on either shore. It joined several separately operated layers: an Asia-Pacific research network, carrier infrastructure, a Chicago exchange point and the U.S. research…
History
A Global Voice by Unanimity: The RIRs’ 2003 NRO Compact
Four regional registries created a way to act together without merging their operations. The 2003 NRO memorandum made shared representation depend on delegated authority and unanimous commitments; in 2004, a separate agreement placed the NRO inside ICANN’s address-policy process…
History
A Mailbox, a Route and a Country Code: Kazakhstan’s Internet, 1991–96
Kazakhstan’s early network story has several dates that are each defensible when attached to the right layer. A mail node, a persistent Internet route, a root-zone delegation and a commercial service did not arrive at the same moment.
History
The Backbone Had a Closing Date, Not a Single Switch: NSFNET, 1995
NSFNET’s backbone service ended on a date fixed in advance. The network’s own termination notice shows why that date should not be mistaken for a single nationwide cutover: many users already relied on another network for their primary path.
History
The Registry Could Draft a Filter; Operators Still Had to Apply It: RIPE, 1993–95
In 1993, RIPE proposed making routing policy legible to databases and tools. A tiny pilot could turn records into access lists; the records still did not show what a network had put into operation.