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 Institutional
DFINFRA and AS210860: The Evidence Chain Still Stops Short of Operational Control
A cross-layer investigation can show how to test whether a registry identity is connected to a working network. In this case, the public evidence identifies the test but does not yet identify the actor able to cause or reverse a routing change.
Number Resource Society
DFINFRA and AS210860: The Evidence Chain Still Stops at the Registry
A public-record investigation can identify where a network-control question begins. It cannot answer that question by treating a registry name as proof of ownership, authority or active service delivery.
Global Institutional
DFINFRA and AS210860: What Routing Evidence Can—and Cannot—Prove
DFINFRA and AS210860: What Routing Evidence Can—and Cannot—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…
Story
ARIN’s RPKI Constraint Is Only as Current as the Package That Ships It
A trust boundary can be carefully designed, correctly signed and still arrive too late. ARIN’s planned RPKI constraint work makes that mundane distribution problem part of routing-security policy.
Story
APNIC and NIXI Cannot Close India’s ROV Plan With One Percentage
On 8 September, APNIC Labs could describe India’s observed ROV filtering as 1.14% or 6.03%. Both figures came from the same dated record. The difference was the window—and it is exactly why a national routing-security promise needs a receipt, not a headline number.
Story
A Scan Found 4,611 Exposed BGP Routers in APNIC. It Cannot Say Why They Were Open
At APNIC 62, researchers put a regional number on a quiet control-plane problem: 4,611 routers across 1,343 APNIC-region autonomous systems answered an unsolicited BGP OPEN exchange in a February IPv4 scan. That is firmer evidence than a port banner, but it is neither a breach…
Story
ARIN’s RPKI Failover Test Left the Dependency Question Open
ARIN blocked access to its RPKI repositories for an hour, restored it, confirmed redundancy five minutes later and reported a return to baseline after another fifteen. That is unusually concrete resilience evidence. It is also narrower than the dependency question ARIN had…
Global Institutional Trends
The RPKI Lab Restarted. Its Recovery Was Still Unconfirmed
A September follow-up moves the question beyond turning services back on: what proves recovery after a signed credential's lifetime has elapsed?
Story
ARIN Lets You Name a ROA. Its Online Search Still Ignores the Name
ARIN Lets You Name a ROA. Its Online Search Still Ignores the Name 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…
IETF
RPKI Router YANG Draft Names New Failure Counters. A Snapshot Is Not a History
A planned cache restart and a cache shutdown can both leave a router without a live RPKI feed. They demand different responses. A revised SIDROPS data model now gives operators more precise counters for that distinction. The harder governance task begins after collection…
Story
ARIN Closed the ROA Wording Fix. The Published Example Drops the Mask Interval
ARIN answered a precise operator complaint in five weeks and marked the documentation repair complete. That is the constructive part of the record. The harder question is why the live example no longer contains the length boundary that made the requested correction capable of…
Story
Barry’s README Uses the IPv6 Prefix Its Lexer Rejects
`::/0` and `0::/0` name the same IPv6 address space. In LACNIC’s experimental Barry generator, the first spelling is documented as a default yet an open issue says it stops at the descriptor lexer; adding one zero lets the token proceed. That is not an RPKI validation failure. It…
Story
ARIN Plans ROA Impact Warnings for the Web, Not the API
ARIN is building a warning for the moment before a Route Origin Authorization changes what observed routes look like. The warning belongs to its web interface. The registry’s programmatic writer is still expected to assemble the same evidence elsewhere. That is not a difference…
IETF
An Origin Validation Community Carries a Trust Decision Without Delegating Import Policy
An Origin Validation Community Carries a Trust Decision Without Delegating Import Policy intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
Story
LACNIC’s RPKI controls make route origin authority operable
LACNIC’s RPKI controls make route origin authority operable 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 Story…
Number Resource Society
An ASPA Is Not a Complete AS-Path Attestation
An ASPA can help an operator test whether an AS path is consistent with published customer-to-provider authorizations. That is valuable route-leak evidence. It is not a signature over every hop, a proof of route origin, a commercial contract, or a guarantee that the published…
Global Regional ISP Trends
When RPKI Validators Disagree, Redundancy Becomes a Policy Choice
Two healthy validators can give different answers about the same prefix. The moment an operator chooses which answer reaches a router, validator redundancy stops being a box-counting exercise and becomes a routing-policy decision.
Number Resource Society
An RPKI Cache Serial Is Not a Freshness Timestamp
Two RPKI caches can report perfectly accurate serial numbers and still tell an operator nothing about which cache holds newer global data. RFC 8210 scopes a serial to one cache session and protocol version. Treating the larger number as the fresher view manufactures a chronology…
Global Regional ISP Trends
A ROA maxLength Is Not a Traffic-Engineering Permission
A broad ROA can keep an emergency more-specific from becoming RPKI-invalid. It can also authorize origins that nobody intended to announce. The operating control is the exact origin plan, not the convenience of one large `maxLength`.
Number Resource Society
A ROA maxLength Is Not a Traffic-Engineering Policy
A route can be RPKI Valid because a ROA’s maxLength admits its prefix length. That result proves a bounded origin authorization. It does not prove that the more-specific route was planned, approved, currently announced or preferred by the operator. Those are separate facts, and…