Content Type
Research Article
Within the Content Type facet, Research Article 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.
Global Cloud Services
GoDaddy's 2012 DNS Outage Made Router-Table Change Control an Accountability Test
GoDaddy's 10 September 2012 outage showed how an operator can retain valid domain records while failures in running network state make names, websites, email and the operator's own support systems unreachable. The accountability question is not whether one record or one backup…
Global Cloud Services
Turkey's 2014 Public DNS Interception Made Resolver Routing an Accountability Test
The 2014 interception of public resolver addresses inside Turkish networks showed why a configured DNS destination is not proof of the route, answering system, response integrity, or restoration state that users actually received.
Global Institutional
The 2002 Root DNS Attack Made Distributed Service Resilience an Accountability Test
The October 2002 attack against the DNS root server system showed why an accurate record of authority is not an availability guarantee. Accountability rests on reachable authoritative service, route and capacity diversity, resolver behavior, traffic controls, measurement…
North America National Telecom
The 2005 Cogent-Level 3 Depeering Made Full-Internet Reachability a Transit Accountability Test
When Cogent and Level 3 stopped exchanging traffic directly in October 2005, some dependent customers discovered that an Internet contract and a registered prefix did not guarantee a working path. The accountable control was the route actually exchanged, the alternate path…
Asia-Pacific National Telecom
The 2006 Hengchun Earthquake Made Submarine-Cable Route Concentration an Accountability Test
How a sequential cable-failure corridor exposed the difference between nominal redundancy, usable alternate capacity and repairable network continuity.
Europe and Middle East Institutional
The 2010 RIPE-Duke BGP Experiment Turned Standards Compliance into a Routing Accountability Test
How a valid experimental BGP attribute exposed an IOS XR propagation defect, session-reset amplification and the need for bounded routing experiments.
Global Cloud Services
OVH's 2017 Optical-Network Failure Made Redundancy Independence an Accountability Test
On 9 November 2017, OVH lost the optical paths connecting its Roubaix hosting site to major external points of presence. The event showed why redundant paths and saved configuration do not amount to resilient network infrastructure when they still depend on one software state…
Global National Telecom
Indosat's 2014 Route Leak Made Full-Table Export Controls an Accountability Test
Indosat's 2014 Route Leak Made Full-Table Export Controls an Accountability Test intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that…
Global Datacenter
Safe Host's 2019 Route Leak Made Peer Filtering a Cross-Border Accountability Test
The Safe Host routing incident of 6 June 2019 showed how an export mistake can become an international infrastructure event when another network accepts and propagates routes outside their intended relationship scope. The durable accountability question is not whether one…
Global National Telecom
TTNet's 2004 Route Leak Made Customer-Prefix Filtering an Accountability Test
TTNet's 2004 Route Leak Made Customer-Prefix Filtering an Accountability Test 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…
North America National Telecom
The 1997 AS7007 Leak Made Route Filtering an Internet Accountability Test
The 1997 AS7007 Leak Made Route Filtering an Internet Accountability Test 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…
North America National Telecom
Level 3's 2017 BGP Misconfiguration Made Backbone Change Control an Accountability Test
The 6 November 2017 Level 3 routing incident showed how one backbone policy error could redirect traffic across organizational boundaries before customers or access providers could see which control had failed. The accountability question is whether the operator and its peers…
Global Cloud Services
UltraDNS's 2014 DDoS Attack Made Authoritative DNS Continuity an Accountability Test
The 30 April 2014 disruption of Neustar's UltraDNS service showed why authoritative DNS must be treated as running network infrastructure rather than a static entry in a configuration file. The accountability question is whether the provider, its carriers and its customers could…
Global National Telecom
Bandwidth.com's 2021 DDoS Attack Made VoIP and 911 Continuity an Accountability Test
The September 2021 attack on Bandwidth's communications network showed how a disruption at a shared voice carrier can propagate through many customer brands. The accountable question is not only who sent the traffic. It is whether each operator could prove that detection…
Global Cloud Services
Azure's 2021 DNS Cache Defect Made Retry Amplification an Accountability Test
Azure DNS did not need every client request to be hostile for its 1 April 2021 outage to grow. Microsoft said an anomalous global query surge exposed a code defect that reduced the efficiency of DNS Edge caches. As the service overloaded, ordinary DNS clients retried unanswered…
Global Cloud Services
The 2019 Route 53 DDoS Made DNS Mitigation Coordination an Accountability Test
On 22 October 2019, Amazon Route 53 was hit by a distributed denial-of-service attack. The attack impaired resolution of some AWS names, but the most revealing part of the public record was not that a large authoritative DNS service received hostile traffic. It was that defenses…
Global Cloud Services
The 2018 Route 53 Hijack Made BGP-to-DNS Trust an Accountability Test
The 2018 Route 53 Hijack Made BGP-to-DNS Trust an Accountability Test 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.…
Global Cloud Services
Cloudflare's 2025 1.1.1.1 Outage Made Route Withdrawal a DNS Accountability Test
Cloudflare's 1.1.1.1 public DNS resolver became unreachable worldwide for 62 minutes on 14 July 2025 after a service-topology change withdrew the resolver's anycast prefixes from production locations. The failure was not caused by an attack, a defective DNS protocol, or the…
Global National Telecom
NTT Docomo's 2021 Network Switchback Outage Made Mobile-Core Capacity an Accountability Test
NTT Docomo's nationwide mobile-network disruption on 14 and 15 October 2021 began during a migration of an IoT subscriber and location-information server. When trouble appeared on the new equipment, the operator switched the population back. The return generated a mass of…
Global Cloud Services
Azure's 2023 WAN Change Outage Made Global Routing Validation an Accountability Test
A planned IP-address change on a Microsoft wide area network router became a global service incident on 25 January 2023. Microsoft's account said a command behaved differently across network devices, propagated messages to other WAN routers, and forced adjacency and…