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.

Story
The Two Companies Holding a Network Nobody Publicly Claims: What AS210057's Upstreams Reveal — and What They Still Cannot
The Two Companies Holding a Network Nobody Publicly Claims: What AS210057's Upstreams Reveal — and What They Still Cannot intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure…

Asia-Pacific Cloud Services
One ASN, Many Owners: How Thanh Trang's Address Space Rides on a Routing Hub It Does Not Control
One ASN, Many Owners: How Thanh Trang's Address Space Rides on a Routing Hub It Does Not Control intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…

Asia-Pacific Cloud Services
Thanh Trang Cloud Computing and Technology Company Limited: an RPKI-valid route that does not belong to the company
A Vietnamese cloud-computing company owns an autonomous-system number, an IPv4 /23 and an IPv6 /48. None of that routing is its own: the only route that reaches the internet from its address space is announced, and cryptographically protected, by a different operator entirely.

CASE FILE
When the registry cannot be read: DFINFRA, AS210860 and the broken verification chain
When the registry cannot be read: DFINFRA, AS210860 and the broken verification chain intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…

Europe and Middle East Regional ISP
Novacloud's AS209874: A Routing Footprint the Mirrors Can't Agree On
Novacloud's AS209874: A Routing Footprint the Mirrors Can't Agree On 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.…

Story
When the Routes Stop But the Registry Keeps Moving: The AS142207 Timeline After July 2026
When the Routes Stop But the Registry Keeps Moving: The AS142207 Timeline After July 2026 intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…

IETF
TCP-AO's KMAC Name Was Not a Complete Recipe
An algorithm label can look precise while leaving a key derivation ambiguous. The latest TCP-AO working-group draft names the NIST KMAC variant behind its proposed 128-bit authenticator, a small textual change with a concrete interoperability question for implementers.

IETF
The BGP Rule That Went Live Before It Was Finished
The latest GROW security inventory makes a configuration interval visible: on some routers, a permit command can start exporting routes before the rest of the intended policy exists. The change record must cover that interval, not just the finished text.

IETF
OSPFv3 Cannot Retire AH One Router at a Time
A new proposal would remove an old authentication choice from OSPFv3. Its operational test is less about selecting a replacement than about getting every router on a link to accept the same protected packets throughout a change.

Story
RIPE NCC is changing the RPKI key. The harder question is what it can touch
RIPE NCC is moving its RPKI dashboard and API credentials towards OpenID Connect. The more consequential disclosure sits lower on the same planning page: a proposed routing beacon was held back because its API could edit ROAs across all RIPE NCC space. Together, the two items set…

Story
DFINFRA's second tier: the live routing that a frozen registry cannot see
DFINFRA's second tier: the live routing that a frozen registry cannot see 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…

Global Datacenter
Who actually runs inside Datamatix's 212.236.10.0/24: the service layer the registry cannot answer
Who actually runs inside Datamatix's 212.236.10.0/24: the service layer the registry cannot answer intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…

Global Regional ISP
Shijiazhuang XuDing Technology Company Ltd: a Chinese-registered company inside RIPE NCC's registry, operating the CoreLink routing brand
Shijiazhuang XuDing Technology Company Ltd: a Chinese-registered company inside RIPE NCC's registry, operating the CoreLink routing brand intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context…

Europe and Middle East Cloud Services
The Routing-Policy Swap Behind AS210328: What the August 2026 Registry Edit Changed — and What It Did Not
The Routing-Policy Swap Behind AS210328: What the August 2026 Registry Edit Changed — and What It Did Not intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…

CASE FILE
DATAMATIX AS210973: what the live record proves about real operation
DATAMATIX AS210973: what the live record proves about real operation 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 Datacenter
Registered, authorised, and still unproven: what DATAMATIX's live posture says about operating a network
Registered, authorised, and still unproven: what DATAMATIX's live posture says about operating a network intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…

IETF
The Dashboard Still Showed 10,000 Valid Routes. They Were Not the Same 10,000.
The number survived the maintenance window without moving. That looked reassuring—until the operators compared the routes behind it. A new IETF YANG draft makes several RPKI validation totals observable across the BGP pipeline. It also makes clear why a total, detached from its…

Global Regional ISP
Three Clocks, One Handle: What the ACSK-RIPE Record Does and Does Not Settle
Three Clocks, One Handle: What the ACSK-RIPE Record Does and Does Not Settle 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…

Global Cloud Services
Five prefixes, five answers: what AS210973's mirror disagreement teaches about trusting the record
Every monitor that watches the routing table tells a slightly different story about the small Vienna network operated by DATAMATIX Datensysteme GmbH. Reading those differences carefully — rather than averaging them away — is the fastest way to learn which layers of the internet's…

Europe and Middle East Cloud Services
The fourth prefix: DATAMATIX's 149.62.35.0/24 and the gap between owning a block and controlling a route
The fourth prefix: DATAMATIX's 149.62.35.0/24 and the gap between owning a block and controlling a route intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…
