Content Type
News Analysis
Within the Content Type facet, News 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
LACNIC's Four-Vendor BGP Claim Needs the Configuration Column
One malformed Prefix-SID attribute reportedly met three different actions as it crossed the Internet: discard, propagation and session reset. LACNIC's new routing-security article makes the divergence visible. To make it reproducible, the comparison now needs to name the release…
Story
At ARIN, Resource-Level Tech Authority Stops Before the ROA
ARIN's records can give a Technical Point of Contact authority over one network resource while routing-security actions remain organized around the containing organization. A newly confirmed suggestion asks ARIN to bridge that gap. The hard part is not adding another permission…
Story
One Source IP Accounted for 38.76% of APNIC's WHOIS Queries in an Hour
One Source IP Accounted for 38.76% of APNIC's WHOIS Queries in an Hour 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 Validator Counted One Fewer Duplicate. The Final Set Stayed at 30,847
Two consecutive validation records moved in an oddly disciplined way. AFRINIC's public Routinator first counted 39,059 valid input VRPs and 8,212 duplicates, then 39,058 inputs and 8,211 duplicates. The final set offered to routers remained 30,847. That unchanged number is not…
Story
RIPE Marked the Upgrade Complete. Retrieval Failed Twice Afterward
At 17:56 CEST on 22 August, RIPE NCC marked its Alfresco maintenance complete. On Monday afternoon, document creation still worked but some files could not be viewed or downloaded. On Wednesday, a second incident began; RIPE NCC later changed the document system’s configuration…
Story
One LACNIC Office Has Three Public Calendar States
LACNIC’s contact record describes one Montevideo office, one set of weekday opening hours and one institutional doorway. Change the language, however, and its public holiday calendar changes year. Spanish presents thirteen dates in 2026; English leaves three in 2025; Portuguese…
Story
ARIN Published a 15-Seat Fellowship Ceiling. Its Roster Has 19
ARIN’s Fellowship timeline and its selected-Fellows announcement describe the same ARIN 58 cohort with different capacities. The planning page stops at 10 in-person and five virtual places. The announcement keeps the 10 in-person places and raises the virtual count to nine. A…
Story
APNIC’s NRO Ballot Has Two Electorates. Its Result Needs the Mix
At 14:00 in Brisbane on 27 August, APNIC opened one electronic ballot for one regional seat on the NRO Number Council. It did not open that ballot to one electorate. Member organizations and qualified conference regulars enter through different doors, vote on different clocks and…
Story
AFRINIC’s Trust Anchor Still Runs to 2030. The NRO Roadmap Said “Short-Lived” by the End of 2025
A roadmap can name a destination and a date. It cannot prove that a live trust anchor has crossed the line. AFRINIC’s retrievable certificate shows why RPKI commitments need an implementation receipt rather than a silently ageing table.
Story
AFRINIC Has Named Its Next CEO. It Has Not Yet Named the Owner of Every Decision Before January
Mike Silber is due to become AFRINIC's chief executive on 1 January 2027. The 130 days between announcement and assumption of office need a public responsibility map, not an assumption that a future title already carries today's authority.
Story
RIPE's NRTMv3 Stream Can Skip an Invalid Object. A Moving Serial Is Not a Completeness Receipt
RIPE Database release 1.124 made a small change with a large evidentiary consequence: the NRTMv3 server should skip invalid objects. Keeping a replication stream alive may be the right operational choice, but continuity alone can no longer answer the mirror operator's most…
Story
LACNIC’s 70% Pass Mark Is Not a Candidacy Receipt
LACNIC’s Board-election rules contain a consequential distinction: a person can pass the mandatory competency assessment and still not become a validated candidate. The Electoral Commission receives the score and remote-proctoring incident evidence, but the public process does…
Story
ARIN Put the Reg-RWS Key in a Header. That Does Not Make It Uncapturable
ARIN now accepts a Reg-RWS API key in the `Authorization` header while continuing to accept the same credential in a URL query string. The new channel removes a dangerous source of routine propagation, but the public record still needs to distinguish a safer request shape, client…
CASE FILE
The Block Was Explained. The Policy Was Still a Claim.
The night shift sees an authenticated DNS response that says a name was blocked, identifies a policy category and offers a support route. The explanation is orderly, machine-readable and intact. It still does not reveal whether the upstream classification was right, who had…
Story
The 27 August Redline: Reading APNIC’s prop-165 Through Its Assessment Delta
APNIC’s canonical `prop-165` record now points to `prop-165-v004`, published on 27 August 2026, while the Secretariat analysis displayed on that record is expressly introduced as applying to version 3. With the APNIC 62 Open Policy Meeting scheduled for 10 September 2026, the…
CASE FILE
The Proof Verified. The Fork Was Still Private.
Every response on Alice’s device verifies. Every later tree head extends the one before it. Across town, Bob sees the same tidy sequence—except his latest head commits to a different key for Alice. The log has not broken either local proof chain. It has separated the witnesses.
CASE FILE
The Certificate Was Fresh. The Number Authority Had Its Own Clock.
A verifier receives a PASSporT with an intact signature, a valid certificate path and a certificate that will expire in hours. Between issuance and the call, however, control of the calling number has changed. The credential can be fresh in the precise X.509 sense while the fact…
CASE FILE
The Tokens Stayed Server-Side. The Browser Still Spent the Session.
The incident review found no exported access token, no stolen refresh token and no readable session cookie. Yet a state-changing request had crossed the Backend for Frontend and reached the protected service. The missing fact was not secret custody. Compromised code had run…
CASE FILE
The SID Chose a Member Link. It Did Not Own the Bundle.
One peering interface was really three physical links. The ordinary Peer Adjacency SID sent traffic to the logical bundle and let its own balancing choose a member. The new member SID could instead place one flow on the lane that looked emptiest. That sharper instruction did not…
CASE FILE
The Certificate Named an Interface. It Did Not Prove the Device.
The commissioning test produced two honest identifiers. The certificate named the factory address of one Wi-Fi interface. The frame arriving at the access point used a private address chosen for that network. Rejecting the connection would punish a real device for using a privacy…