Content Type
Longform
Within the Content Type facet, Longform 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
Five root-server letters, six listed instances: what Panama’s count can tell us
A LACNIC country report names five root-server identities in Panama. Operator site records retrieved later sum to six instances. The figures describe different units and dates; a response-time chart adds a third question: which route and instance did each measurement reach?
Story
APNIC’s Two Root-Key Signals Count Different Things
On 11 October, the DNS root is scheduled to begin using KSK-2024 to sign the zone. APNIC’s latest measurements put two percentages beside that date, but one follows key-tag signals from resolvers while the other tests end systems behind validating resolvers. Their denominators…
Story
What APNIC’s 2027 Balance Assumes About Foundation Funding
APNIC’s 2026 budget shows where a sharp reduction in Foundation receipts went: some costs moved into APNIC’s self-funded development budget, some activities were reduced, and M-Root support was proposed for JPRS to manage. Its published 2027 balance assumes Foundation funding…
Story
The Legacy Host Went Quiet. Its IPv4 Lease Did Not.
A /32 DHCPv4 mask can quiet an old client that cannot use IPv6-Only Preferred. The address it receives, the inbound packets it can still accept and the pool that supplies its lease remain operational questions.
Story
Jamaica’s Internet Exchange Turns on the Terms of Participation
A 2026 relaunch brings JAIXP back into view, but its durable value will depend on why independent operators choose to connect, exchange traffic and remain.
Story
RPKI’s Sub-One-Per-Cent BGP Result Is Useful. It Is Not a Stability Verdict.
A peer-reviewed study finds that RPKI-associated updates remain a small share of observed BGP UPDATE volume. That matters, but message volume is only one meaning of network stability.
Story
APNIC’s Helpdesk Averaged 7.47 Business Hours. The Average Has a Boundary.
APNIC’s first-quarter report puts two useful service results above their targets: a 7.47-business-hour average Helpdesk response time and 95.5% favorable ratings. The next question is not whether those numbers are good. It is what, exactly, they describe.
Story
Botswana’s IPv6 Plan Sets a 2026 Target. What Counts Toward 100%?
BOCRA’s roadmap assigns IPv6 targets through 2026, while Botswana’s accelerator records engineers trained and projects chartered. The missing public question is not whether work began; it is how a reader can distinguish readiness from measured deployment without exposing…
Story
RIPE Recovered RRC12’s Files; Its Restart Bug Still Needs a Structural Fix
RIPE NCC says it has regenerated RRC12’s missing BGP files since 2 October. The same incident update says the configuration has been corrected, but the latent restart bug behind the repeated timeouts still awaits a structural fix.
Story
ARIN’s IPv4 Calendar Has a Quarter and a Date
ARIN’s 7 October distribution announcement put the next IPv4 Waiting List distribution in “late” 2026’s fourth quarter. The live status page points to on or about 4 January 2027. Neither statement is an applicant-level delivery promise, but together they show why a public…
Story
When a TLS Allowlist Calls the Future Non-Compliant
A two-week study of 50.7 million TLS handshakes found that four national guidance sets could label between roughly 14% and 80% of the same institutional traffic non-compliant. The spread is not a direct measure of insecurity. It is a warning about what happens when a dated list…