BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

Live Wire

View all briefings
ARIN 58 fellowship review window reaches 14 August without disclosing a selection|RIPE 93 plenary proposal deadline reaches 14 August, while lightning talks remain open|RIPE NCC schedules a document-management maintenance window for 22 August|RIPE NCC listed an IPv6 Security Training Course in Oslo for 14 August|RWE says two data centre site deals near agreement|VMO2 says equipment reuse avoided 5,262 tonnes CO₂e|Optus launches mission to extend D3 satellite life|Waterloo Region seeks data-centre impact report|Oakville imposes one-year moratorium on data centres|Envision commissions Ulanqab AI campus|RIPE NCC postmortem traces NRTM desynchronisation to invalid RPSL handling|RIPE NCC puts routing intent on the agenda with a live IRR webinar

Lead Report / Story

Marked-up policy pages separated by an eighteen-day timeline, with a red barrier struck out and an open consequence path continuing beyond it
AFRINIC’s official details and current proposal list place eighteen days between Draft 4 and Draft 5 of its abuse-contact proposal, then only twelve days between Draft 5 and the AFRINIC-31 discussion. That narrow interval matters because the new draft made a genuine concession: it deleted an express route from non-compliance to warnings, deeper follow-up and discretionary service blocking. Yet it still asked the private registry to test whether a resource holder had taken measures and answered abuse reports. The question was therefore not whether the redline changed, but whether it finished drawing the boundary between a reachable contact record and the adjudication of conduct.

Eighteen Days to Redraw a Boundary: What AFRINIC’s Draft 5 Left Unsettled

AFRINIC’s official details and current proposal list place eighteen days between Draft 4 and Draft 5 of its abuse-contact proposal, then only twelve days between Draft 5 and the AFRINIC-31 discussion. That narrow interval matters because the new draft made a genuine concession: it deleted an express route from non-compliance to warnings, deeper follow-up and discretionary service blocking. Yet it still asked the private registry to test whether a resource holder had taken measures and answered abuse reports. The question was therefore not whether the redline changed, but whether it finished drawing the boundary between a reachable contact record and the adjudication of conduct.

Read Full AnalysisStory Intelligence
  1. Editorial illustration of four distinct procedural gates linking a registry ledger to an operating network map

    Story

    Four Repairs, Four Gates: The Private Authority Map Inside AFRINIC’s PDP Bis Draft 4

    On 29 October 2018, AFRINIC published a proposed rulebook in which PDWG chairs would have up to two weeks to pronounce on consensus, yet their decision still sat inside a longer chain: a Board-appointed committee could review process, the Board could remand a proposal on procedural or fiduciary grounds, staff could implement only after ratification, and the Board retained a separate route for measures it considered necessary and urgent. The collision matters because each gate could delay, advance or reverse a rule affecting registry administration, while none of the gatekeepers thereby acquired public authority over African network operators.

  2. An editorial illustration of a registry ledger dividing a correction path from a six-month return clock

    Story

    Draft 7 offered six months, but did not clearly offer a cure

    On 6 April 2019, AFRINIC published Version 7.0 of its Internet Number Resources Review proposal, AFPUB-2016-GEN-001-DRAFT07. Its one stated change from Draft 6 sounded protective: an organisation would have at least six months, and perhaps longer, before resources were recovered. Yet the new sentence gave six months “to effect the return of the resources”, not an unmistakable right to correct a breach and keep the registration. AFRINIC’s own staff assessment on 21 May sharpened the contradiction. Staff said Draft 6 had seemed clearer about correction and notification of changed use, whereas Draft 7 no longer made that option clear. For a holder, the difference could determine whether evidence and accurate records preserve a network resource or merely defer surrender. For customers, it could shape renumbering, routing, DNS and service continuity. For the registry, it separated careful record correction from an assertion of power it did not possess. The decisive question was therefore not whether six months was generous in the abstract, but what the clock was for, who decided whether compliance was enough, and whether a neutral reviewer could halt irreversible action.

  3. Editorial illustration of an IPv6 network boundary splitting between third-party devices and independently controlled downstream connectivity

    Story

    Two words, two directions: AFRINIC’s IPv6 sub-assignment redline

    On 22 August 2018, the words “semi-permanent connectivity” appeared in an AFRINIC proposal about IPv6 provider-independent assignments. They seemed to tighten a familiar prohibition. Yet the same revision removed a numerical limit, discarded a peculiar restriction on point-to-point links and created a distinct shelter for third-party devices. Draft 2 was not a gate simply closing. It was a boundary changing shape—and doing so without saying when the public record should change with it.

Member Access

Daily Strategic Internet Intelligence, Free for Members

Become a BTW member for free daily updates across governance, market, membership, and RIR Watchdog sessions. Join now and manage your delivery preferences anytime.

  • 01Daily intelligence brief
  • 02Governance + market + RIR
  • 03Preference control anytime
Create AccountSign In

BTW Media on Air

Selected briefings, interviews, and live sessions from the BTW intelligence team, focused on internet infrastructure, governance, and market signals.

View All

UK Ministers Approve East London Data Centre

Australia’s AI Data-Centre Boom Faces a Power Challenge

Who Chose AFRINIC’s 2026 Nomination Committee?

Spain’s Military Satellite Replacement Will Take Four Years

Satellite 5G Is Getting Closer — But It’s Not Ready Yet

UK Full Fibre Reaches 85%—So Why Can’t Everyone Get It?

Zenith Data Breach: Why Your Contact Details Matter

ChainDrop Explained: How an npm Supply-Chain Attack Spreads

Twilio Reported Partial Recovery Across Safaricom SMS Routes

Nine Michigan Water Systems Reported Malicious Cyber Activity

Zoom Stayed Operational While Meeting Quality Declined

Twilio Saw Safaricom Delivery Receipts Recover After 57 Minutes

Fiber57’s Routing Silence Leaves Pimentel’s Recovery Path Unproven

Rolls-Royce Data-Centre Growth: Orders, Revenue and Margin Are Not Equal

China’s Data-Centre Expansion Continues Despite Overcapacity Risk

Photorealistic dark-walnut optical test bench with a clear upper glass channel, a separate cobalt lower side rail carrying three glass observation beads, an amber correction tile raised in a spring carriage, a brass interlocked allocation gate, and three receiver prisms showing different local lever outcomes, with no text or people

Governance

Five Minutes at the Registry, Longer on the Network

AFRINIC’s second draft of its RPKI AS0 proposal introduced a narrow but important restraint: a separate trust anchor could let networks choose whether to receive the registry-generated warning and let observers measure it apart from ordinary holder authorisations. That choice made the service more voluntary and more legible. It did not answer the harder question raised by an error: when the publisher removes a mistaken object, how and when does the correction become real everywhere that relied on it?

AI-generated editorial reconstruction: a Dominican field technician inspects an aerial fibre service loop beside a wet Pimentel-area street after rain.

Market / Companies

Fiber57's October routing silence leaves Pimentel's recovery path unproven

Fiber57 has a documented right to resell internet service across four municipalities in the Dominican Republic's Duarte province, and its own internet number resources briefly appeared in the global routing system in 2025. Yet the public record still does not show the cables, powered sites, usable capacity or repair arrangements that would determine whether a wet-season break near Pimentel becomes a short local incident or a prolonged loss of access.

AI editorial portrait of Patrick MeLampy against an abstract enterprise networking and session-routing background.

Market

Patrick MeLampy and the Long Bet on Session-Aware Networks

Patrick MeLampy's public record is not built around celebrity hardware launches or consumer-facing platforms. It is built around a quieter but consequential thesis: that networks behave better when they understand sessions, not just packets. From Acme Packet's session border controllers for all-IP communications, through 128 Technology's Session Smart routing and SD-WAN argument, to later Secure Vector Routing specification work, his career shows how control at the edge of a conversation can become an infrastructure strategy.

Photorealistic editorial portrait of Carlos Martinez-Cagnazzo in a routing-security operations setting.

Market / Trends

Carlos Martinez-Cagnazzo and the Boundary Work of Routing Security

Carlos Martinez-Cagnazzo's public record does not describe a lone architect making the internet safe. It shows a more instructive kind of authority: a regional registry strategist working where cryptographic standards, trust-anchor operations, operator education and cross-border incident coordination meet, and where each technical control remains dependent on institutions and people using it well.

Anonymous conference entrants move past an aggregate counting grid as four paths toward speaking, volunteering at a help desk, mentoring and committee service break at missing data connections.

Governance / NOGS

Counting Entry, Not Continuity: Where NANOG's Participation Record Stops

NANOG’s annual reports have become increasingly detailed about how people appear in its meeting record: registrations by mode, first-time participants, membership status, students, speakers, women in attendance, employment bands and organisation types. Its programme record also describes orientation, mentoring, ambassadors, a help desk and invitations to take on later roles. What the reviewed public record does not publish is the bridge between those two views—the share of a first-time cohort that returns, speaks, volunteers, becomes a member or serves in a formal role. That is a bounded measurement gap, not evidence that newcomers disappear.

Editorial position

Why BTW Media exists

  • Reality over advocacy
  • Evidence over sentiment
  • Systems over noise

Internet governance is too often described as theory, consensus, or institutional comfort while operators live with the consequences of structure, scarcity, jurisdiction, and incentives.

BTW shows how the system works when assumptions are tested: clear, uncomfortable, evidence-led reporting that keeps attention on structure rather than drama.

Core Architecture

Governance, market, and membership branches operating in one integrated intelligence model.

Governance

  1. The date that made the appeal: Draft 4 and the limits of internal review
  2. Resolution 202104.602 and AFRINIC’s Twenty-Four-Hour Appointment Bridge
  3. What AFRINIC’s 2019 Audit Assured—and What It Left Open
  4. AFRINIC ended a technical committee. The missing question is what survived it
  5. The Resolution That Opened the Ledger — and No More
  6. The Electorate Behind the Chair: What AFRINIC’s 2019 Draft Could—and Could Not—Authorise
  7. The Penalty Draft 4 Left Undefined
  8. The Fee at the Prefix Boundary: What Resolution 202001.546 Actually Authorised
  9. Four Weeks to Show the Work: Evidence Before AFRINIC Consensus
  10. What USD 71,217 Can — and Cannot — Prove About AFRINIC’s RPKI Priority
View Governance

Market

  1. Zayo Group, LLC and AS6461: What Can a Fiber Backbone Prove About Route Continuity?
  2. WHITETELECOM originates 36 IPv4 routes through one visible upstream, while Bonao's storm-ready last mile remains undisclosed
  3. Storm Iraq and the 333-Path Test: Where an Operator’s Control Really Ends
  4. Outofbox Cloud promises eight data-centre regions; public evidence still points to one Belagavi footprint
  5. Heartbleed made shared cryptographic maintenance a systemic-dependency accountability test
  6. Cdnbt Bilgi Teknolojileri ve Hizmetleri Limited Sirketi and the cash-flow test behind local network reliability
  7. Omni markets 1.2MW at Batam; the independent Tier III record stops at Jakarta's design
  8. Cox's 2025 Route Leak Showed What RPKI Containment Can Prove
  9. The Route That Vanished: What AS208355 Does—and Does Not—Prove About YAM Digital
  10. S3Wireless Colombia’s redundancy test begins at the building riser, not the router
View Market

Membership

  1. The two-page contract behind a shared registry
  2. The dashboard that could reveal a difference but could not create a punishment
  3. The Million-Address Switch: What SL-Update Draft 1 Actually Changed
  4. The Longer Clock and the Shorter Fuse: AFRINIC’s Draft 2 Abuse-Contact Paradox
  5. Three seats were enough on paper: AFRINIC’s disputed quorum repair
  6. The Zero That Had to Move First: AFRINIC’s First AS0 Draft and the Design of Reversible Warning
  7. The reciprocal bridge AFRINIC drafted before it had a transfer path
  8. The ledger behind the call: what AFRINIC needed to show for Resource Transfer Policy Draft 4
  9. The mailbox test that entered a meeting without a defined consequence
  10. One resolution, two proof burdens: what AFRINIC had to preserve in 202002.552
View Membership

Number Resource Society

Reporting on address stewardship, representation, and the institutions shaping number-resource governance.

View Number Resource Society
  1. When One Corporate Group Casts Twenty Registry Votes
  2. NRS Growth Without Mandate Laundering
  3. The Public Evidence Pack NRS Asks Registries to Publish
  4. A Global South Label Cannot Substitute for a Mandate
  5. A Future Registry Worth Leaving
  6. Registry Resolution Before Insolvency: The Safeguards NRS Advocates
  7. The User-Controlled RPKI Model NRS Advocates
  8. Bayan Telecommunications, AS6648 and the Boundary Between Network Records and Control
  9. One Resource Holder, One Verifiable Control Claim
  10. Why NRS Advocates Records for Leased and Delegated Use

RIR Watchdog

Five regional sessions: ARIN, RIPE NCC, APNIC, AFRINIC, and LACNIC.

Network Operator Group (NOGs)

Operational intelligence from the communities where routing, peering, resilience, and deployment practice are tested.

View Network Operator Groups

History of the Internet

The internet's hidden roots in military strategy

Structural context for current governance behavior and infrastructure control models.

Photorealistic editorial risk and accountability image for Dyn made managed DNS a revenue-continuity accountability boundary

Dyn made managed DNS a revenue-continuity accountability boundary

The 2016 Dyn attack did not take down the internet. It did something narrower and more costly for dependent services: it made revenue, login, payment, media, support, and public-information flows unreachable because a shared authoritative DNS provider was overwhelmed. The accountability question is who controlled DNS diversity, transit exposure, customer continuity, and practical revenue-cycle workarounds before a managed-DNS dependency became a common-mode failure.

  1. DigiNotar made certificate-authority failure an operational-harm control test
  2. Operator Rights Outside the Multistakeholder Theatre
  3. Let's Encrypt made root expiration a certificate-trust accountability boundary
Open History Session

Leadership Alliance

Global AI summit launches as world enters implementation decade

Capital, policy, and institutional leadership alignment in cross-border digital systems.

Five separate private registry stations linked to one shared blank ledger, with sealed contract folders, equal blank cost trays, mirrored archival data cases, a service-status mechanism and an empty successor dock holding a portable archive case

The two-page contract behind a shared registry

Five private regional registries signed a two-page instrument because a globally shared registry can fail at the seams between regional administrators. AFRINIC’s Board first authorised its chief executive to sign; the five organisations then accepted four duties and extended a private dispute route. That compact floor is useful. Its silences are useful too, because they reveal which questions about cost, service, data custody and succession cannot be answered by an institutional recital or a signature page alone.

  1. The dashboard that could reveal a difference but could not create a punishment
  2. The Million-Address Switch: What SL-Update Draft 1 Actually Changed
  3. The Longer Clock and the Shorter Fuse: AFRINIC’s Draft 2 Abuse-Contact Paradox
Open Alliance Session