Topic
Network-resource Evidence
Within the Topic facet, Network-resource Evidence topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.

Asia-Pacific Regional ISP
Planet Information Technology Solution and AS136903: IPv4, IPv6, RPKI, DNS, and ISP Continuity Costs
Planet Information Technology Solution and AS136903: IPv4, IPv6, RPKI, DNS, and ISP Continuity Costs intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…

Europe and Middle East Institutional
Spamhaus's 2013 DDoS Made Open DNS Recursion a Network Accountability Test
The March 2013 campaign showed how exposed recursive DNS, source-address spoofing and shared interconnection paths could turn individually small configuration failures into a large external cost. Accountability depends on proving which operator controlled each executable step and…

Leaders
Dave Oran and the Operational Boundaries from IS-IS to IP Anycast
Dave Oran’s shared technical record shows how dependable forwarding begins with a clear account of identity: which routing domain, service instance, name, or piece of state a system is actually using, and where continuity can break when that identity changes.

Asia-Pacific Regional ISP
Techno Asia Infotech and AS135037: Routing, RPKI, DNS, and ISP Continuity Costs
Techno Asia Infotech and AS135037: Routing, RPKI, DNS, and ISP Continuity Costs 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…

Asia-Pacific Regional ISP
AS139618 Stays in the Registry While Its Public Routing Surface Is Silent
AS139618 Stays in the Registry While Its Public Routing Surface Is Silent 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…

Leaders
Peter Psenak and the Link-State Decisions Behind Segment Routing and Flexible Algorithms
Peter Psenak's attributed IETF record offers a practical way to examine how routing policy becomes operational state. The relevant standards do not promise an automatically optimal network. They define identities, constraints, participation rules, forwarding bindings, and failure…

North America Cloud Services
Microsoft's 2001 DNS Outage Made Shared Router Failure Domains an Accountability Test
Microsoft's January 2001 outage demonstrated a basic but still consequential property of network infrastructure: correct DNS records and several authoritative server processes do not create a resilient naming service when every reachable path to those servers depends on the same…

Asia-Pacific Institutional
IBC Digital and AS10078: Hosting, DNS, Connectivity, and Operational Continuity Costs
Public registry, routing, DNS, hosting, maintenance, and contractual records expose a real operating surface while leaving private architecture, longitudinal reliability, and customer production outcomes subject to separate evidence.

Leaders
Hannes Gredler and the Failure Boundaries Behind IS-IS and BGP-LS
Hannes Gredler’s co-authored standards work offers a practical lesson in routing automation: useful decisions begin with records that identify topology precisely, state their scope, and remain honest about what they cannot authorize or prove.

Asia-Pacific National Telecom
KT's 2021 Routing Error Made Protocol-Boundary Validation a National Network Accountability Test
KT's nationwide Internet disruption showed why a carrier cannot treat an approved maintenance plan or two layers of manual review as proof that a live routing change is safe: accountability depends on the exact commands routers execute, the protocol boundaries they preserve, the…

Global Cloud Services
GitHub's 2015 Great Cannon DDoS Made On-Path Code Injection a Network Accountability Test
The 2015 attack on GitHub showed that network accountability begins with the bytes a user actually receives, not merely the address, certificate, contract or status page associated with a service.

Europe and Middle East National Telecom
Belgacom's 2013 Intrusion Made Roaming-Router Access an Operator Accountability Test
The lasting issue in the Belgacom case is whether an international carrier could substantiate its assurances with preserved evidence about privileged access, running router state, customer-traffic effects and operational continuity.

Asia-Pacific Regional ISP
AS148972 Keeps Zero Cirrus in the Registry After Its Visible Route Goes Quiet
AS148972 Keeps Zero Cirrus in the Registry After Its Visible Route Goes Quiet 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…

Europe and Middle East Institutional
dot Webcam Limited and the .webcam Control Plane: Delegation, RDAP, DNSSEC, and Registry Continuity Costs
dot Webcam Limited is the accountable registry operator for .webcam, while the namespace visible to users depends on delegation records, DNS and DNSSEC, WHOIS and RDAP, registrar interfaces, escrow, reporting, provider boundaries, and recoverable operating responsibility…

Global National Telecom
Raptor Train Made Edge-Router Lifecycle Evidence an Operator Accountability Test
Raptor Train showed how a rapidly rotating population of compromised edge devices can remain operationally persistent even when individual malware instances are short-lived, making support state, network evidence, remediation authority and proof against reinfection an…

Leaders
Yakov Rekhter and the Operational Boundaries Built into BGP and Private Addressing
Yakov Rekhter's public standards record shows how inter-domain routing and address scope became manageable through explicit permissions, visible protocol state, bounded uniqueness, and honest accounting for the cost of later change.

Asia-Pacific Institutional
Function4 and AS153748: Connectivity, RPKI Gaps, and Business Continuity Costs
Function4 and AS153748: Connectivity, RPKI Gaps, and Business Continuity Costs 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…

Asia-Pacific Regional ISP
AS136922 Keeps Anttel Wholesale in the Registry While Its Public Routing Surface Is Silent
AS136922 Keeps Anttel Wholesale in the Registry While Its Public Routing Surface Is Silent intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…

Global National Telecom
The 2023 Pumpkin Eclipse Made CPE Recovery Evidence an ISP Accountability Test
The October 2023 destruction of hundreds of thousands of home and small-office routers turned firmware authority, fleet inventory, hardware replacement and proof of restored connectivity into one operator-accountability test.

Asia-Pacific Regional ISP
Chittagong Multi Channel Limited and AS137029: IPv4 Routing, RPKI, and ISP Continuity Costs
Chittagong Multi Channel Limited offers a compact view of how an access provider's public company identity, Internet-number records, route announcements, security metadata, customer-facing promises, and day-to-day operating duties have to remain aligned.
