Topic
RPKI and Route Security
Within the Topic facet, RPKI and Route Security 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.
Leaders
John Scudder and the Standards Work Behind BGP Origin Validation and Routing Policy
John Scudder's public IETF record connects early network operations, BGP implementation, route-origin validation, bounded error handling, and route observability. The record matters because inter-domain routing is not made trustworthy by one database, one standards document, or…
Global National Telecom
Rostelecom's 2020 Route Leak Made Origin Validation Limits an Accountability Test
Rostelecom's April 2020 routing incident showed why a valid origin record is not a complete route-policy guarantee. Accountability depends on accurate RPKI data, current relying-party caches, explicit boundary filters, path-aware controls, independent monitoring and coordinated…
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.
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…
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
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 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…
Global Cloud Services
Cloudflare's 2022 Outage Made BGP Change Staging an Accountability Test
Cloudflare's June 2022 outage did not begin with an attack or a broken fiber. It began with a reviewed network change whose rollout steps did not exercise the architecture that could fail. When reordered BGP policy terms withdrew site-local prefixes from 19 high-traffic…
Global National Telecom
Telekom Malaysia's 2015 Route Leak Made Upstream Filtering a Transit Accountability Test
Telekom Malaysia's 2015 Route Leak Made Upstream Filtering a Transit 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…
Leaders
Guillermo Cicileo and the Infrastructure Work Behind Routing Security in Latin America
Across registry design, exchange-point deployments, operator guidance, and training, Cicileo's record shows how routing-security ideas become controls that networks can actually maintain.
North America National Telecom
CenturyLink's 2020 FlowSpec Outage Made Backbone Change Control an Internet Accountability Test
The narrow task sounded ordinary for a large carrier: block unwanted traffic from one IP address for a customer. The result was not ordinary. On 30 August 2020, a problematic BGP FlowSpec announcement spread through the CenturyLink/Level 3 network, interfered with BGP session…
Global National Telecom
Cox's 2025 Route Leak Showed What RPKI Containment Can Prove
Cox's 2025 Route Leak Showed What RPKI Containment Can Prove 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. The Global…
Global National Telecom
Rostelecom's 2017 Financial-Route Leak Made Attribution Evidence an Accountability Test
Rostelecom's 2017 Financial-Route Leak Made Attribution Evidence 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…
JPNOG
When Trust Data Goes Dark: The Safety Question Inside RPKI
Origin validation can make Internet routing safer. But a repository fault, an incomplete cache view or a mistaken local policy must not be allowed to turn a degraded security signal into lost connectivity. A six-month JANOG experiment in 2013 brought that tension into an operator…
Number Resource Society
A Ten-Year Stress Test for Number Resource Institutions
Number-resource institutions are built around continuity. Allocations, registrations, transfers, directory data and route-security credentials must remain dependable while boards change, laws conflict, markets move and systems age. Their public language therefore emphasizes…