Live Wire
View all briefingsLead Report / North America National Telecom
C-Root kept answering DNS queries while serving an old root-zone view for several days. The incident showed why root-service accountability must measure the freshness of authoritative state, not only whether a server responds.
Europe and Middle East National Telecom
A routine routing-policy update inside a major transit network blackholed traffic for contained prefixes. The incident showed that backbone accountability depends on what packets can reach, how quickly customers can withdraw a failing path, and whether an operator can prove that rollback restored service.
Global National Telecom
A vendor software update that had been tested before deployment still disconnected wireless customers across Canada, exposing the difference between change approval and evidence that a national mobile network can stop, reverse and recover a rollout safely.
Asia-Pacific Regional ISP
CHINANET Guangdong province Guangzhou MAN network has a conspicuous public routing surface: 36 observed IPv4 announcements, nine IPv6 announcements and five routing neighbours in a dated RIPEstat view. The records make AS134773 easy to identify and monitor. They do not reveal the physical metropolitan network, its legal perimeter, its customers, its capacity, or the dependencies that decide whether service survives the next failure.
Member Access
Become a BTW member for free daily updates across governance, market, membership, and RIR Watchdog sessions. Join now and manage your delivery preferences anytime.
Market / Companies
Alphawest Services Pty Ltd is a useful case study in what happens when a network integrator becomes part of a telecommunications carrier. Public records connect the company to network consulting, integration, outsourcing, managed-service administration, a private-cloud catalogue, and two active APNIC autonomous-system registrations. Those records establish identity and capability boundaries. They do not establish current route activity, service reliability, a private architecture, or customer production results. The operational question is therefore not whether the combined offer sounded comprehensive. It is how identity, access, change authority, monitoring, maintenance, escalation, and exception handling must remain coherent after a specialist integrator is absorbed into a larger operator.
Governance
The regional registries are right to prepare technical and financial support for an AFRINIC failure. But mirrored records, peer expertise and emergency funding do not by themselves authorize another registry to inherit contracts, exercise resource-management discretion or bind the operators that depend on AFRINIC. The unresolved issue is mandate, not the value of backup.
Market
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.
Market / Trends
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.
Governance / NOGS
A number can travel farther than the qualification printed beside it. The dispute that followed NANOG 96's presentation on IP geofeeds shows why vendor research should be judged neither by the employer on the title slide nor by the applause in the room. Its proper test is whether operators can follow a consequential claim through method, denominator, objection, response and correction after the microphone has been switched off.
Editorial position
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.
Governance, market, and membership branches operating in one integrated intelligence model.
Reporting on address stewardship, representation, and the institutions shaping number-resource governance.
Five regional sessions: ARIN, RIPE NCC, APNIC, AFRINIC, and LACNIC.
North America policy and transfer market signals.
Europe governance transparency and accountability monitoring.
Asia Pacific allocation pressure and policy dynamics.
Board legitimacy, election process, and legal continuity.
Institutional adaptation and ICP-2 governance trajectory.
Operational intelligence from the communities where routing, peering, resilience, and deployment practice are tested.
North America NOGs
Asia-Pacific NOGs
Europe and Middle East NOGs
Latin America and Caribbean NOGs
Asia-Pacific NOGs
Asia-Pacific NOGs
Africa NOGs
North America NOGs
North America NOGs
History of the Internet
Structural context for current governance behavior and infrastructure control models.
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.
Leadership Alliance
Capital, policy, and institutional leadership alignment in cross-border digital systems.
Sandhills Publishing appears in public Internet records as the organisation associated with AS20005 and an IPv4 routing footprint. The company now presents itself publicly as Sandhills Global and describes geographically separated data-centre operations, hosted applications, replication, load balancing, and technical work across networks and databases. Those records expose a meaningful operational control surface. They do not reveal a private architecture, prove current availability, or establish customer production results. The useful question is therefore not whether a registry entry or facility description sounds reassuring. It is how records, routes, facilities, data, applications, people, and exception handling must remain coherent for the declared design to work.
