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.
Global Cloud Services
CPP JSC and the small routed control surface behind AS211730
CPP JSC and the small routed control surface behind AS211730 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 Cloud Services
Ariantel and the latent routing record behind AS211828
Ariantel and the latent routing record behind AS211828 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 Cloud…
CASE FILE
YouTube showed how BGP route leaks can outrun the platform contract
The 2008 YouTube reachability failure is not only a routing incident. It is a durable accountability example of how users can experience a platform outage even when the decisive control sits outside the direct platform-user contract, in route announcements, upstream filtering…
Story
RIPE NCC showed why ROA mistakes can become common-mode routing dependencies
RPKI and Route Origin Authorizations improve routing security, but they also turn registry data, operator choices, validation state, and rollback discipline into shared dependencies. A bad or overly narrow ROA does not automatically cause a global outage, yet it can become a…
Global National Telecom
Pakistan Telecom made upstream route filtering the missing control in YouTube reachability
The 2008 YouTube route hijack remains a routing-accountability case because a domestic control route announced by Pakistan Telecom became a global reachability failure only after upstream acceptance and propagation turned a local network decision into an internet-wide disruption.
Global National Telecom
Orange Spain made RIPE account security a routing-control accountability test
The Orange Spain incident showed that Internet number-resource administration can become live routing harm when registry credentials, RPKI objects, ROAs, route filters, monitoring, and upstream validation do not contain the blast radius. The accountability question is not only…
Europe and Middle East Cloud Services
Cybermancer's real test is the infrastructure change that stays accepted
Cybermancer Infosec B.V. is not easy to judge through the usual software-company lens, because its public evidence is less a catalogue of packaged products than a trail of operating discipline: FreeBSD release engineering, reproducible-build work, CI/CD modernization, hostmaster…
History
The Measured Internet: Geoff Huston and the Authority of Public Evidence
Geoff Huston's public authority does not look like the authority of an operator, a regulator, or a registry board. It is quieter than that, and in some ways more durable. It sits in the space where hidden network behavior becomes measured, named, argued over, and made difficult…
History
The 2018 Google route leak showed the mismatch between routing contracts and real control
The November 2018 MainOne, China Telecom and Google route leak was not the same event as the 2008 Pakistan Telecom YouTube hijack. It was a different governance failure: routes learned through a peering relationship escaped into transit relationships, other networks accepted…
Global National Telecom
Pakistan Telecom showed how a local network block can transfer global costs
The 2008 Pakistan Telecom YouTube route hijack remains one of the clearest cases of cost transfer in internet routing. A domestic blocking measure escaped through BGP, PCCW propagated it, YouTube reachability failed globally, and the parties carrying the repair burden were not…
History
A faulty ROA can turn route security into a common-mode outage
The March 2025 North Korea RPKI incident showed the uncomfortable second edge of route-origin validation. RPKI is a necessary repair for BGP trust, but a faulty Route Origin Authorization can make legitimate routes invalid to networks that enforce validation. When many operators…
History
The DNSSEC root KSK rollover proved that readiness has to be verifiable
ICANN’s 2018 DNSSEC root key-signing-key rollover is often remembered as a successful global cryptographic maintenance event. For risk accountability, the more important lesson is narrower: success depended on making readiness and repair observable before public relations could…
Global Cloud Services
Cloudflare's route-leak response made verifiable repair more important than reassurance
Cloudflare's June 2019 route-leak outage was a reminder that a company can run resilient edge infrastructure and still depend on the routing discipline of networks it does not control. The public accountability lesson is not simply that Verizon and a smaller network propagated…
Global Cloud Services
Cloudflare, the June 2019 route leak, and accountability beyond the network edge
For a little more than two hours, routes intended to improve traffic inside one regional network escaped into the global routing system and pulled part of Cloudflare's anycast traffic toward links that could not carry it. The incident shows why network resilience cannot stop at…
Global National Telecom
Pakistan Telecom and the YouTube route hijack that escaped a national filter
The 2008 YouTube route hijack began as a national blocking instruction and became a global routing failure because the internet's control plane accepted a more specific announcement from the wrong origin. Pakistan Telecom originated a route for part of YouTube's address space.…
Europe and Middle East Institutional
NLnet Labs sells no boxes but anchors the DNS software economy
NLnet Labs is not a hardware vendor, access provider, cloud platform or registry. Its market weight comes from something less visible and more structural: a small Dutch public-benefit foundation maintains open-source DNS and routing-security software that operators, registries…
Story
ARIN and the economics of ROA revocation risk
RPKI made route-origin authority easier for machines to verify, but it also made registry decisions part of the operating risk around scarce IPv4 capital. In the ARIN region, the danger is not that Route Origin Authorizations exist; they are among the more useful safety…
Story
ARIN and the economics of RPKI governance risk
RPKI makes routing safer by letting resource holders publish cryptographic route-origin authority, but the same trust chain can make ARIN account control, agreement status, hosted-service dependence, transfer timing and revocation rules part of IPv4 continuity risk unless…
Story
AFRINIC ROA revocation and the need for notice, cure and appeal
A small routing-security record can become a large economic event when the registry behind it is under institutional stress. AFRINIC is a test case for how route-origin assurance can protect networks, and how the same assurance layer can become an operational shock if notice…
Story
The governance risk inside AFRINIC's RPKI layer
AFRINIC is examined through RPKI governance risk as a registry-governance and institutional-economics problem for the Africa region.