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.
NPNOG
A decade of meetings, but where is the outcome ledger? Auditing npNOG’s institutional value
npNOG can document that it kept opening the room. Its public chronology runs from the first numbered meeting in 2016 to npNOG-11 in 2025, with a virtual programme in 2020. The archive shows workshops, conferences, fellows, committees and technical subjects. That is not trivial…
Story
RIPE’s IRR Study Says RPKI Can Replace a Route Object, Not a Customer Cone
A new RIPE Labs study makes a useful distinction that is easy to lose in general talk about replacing the IRR. A prefix–origin record and the policy information used to discover a customer cone are not the same operational entity, so they cannot share one retirement decision.
Story
AFRINIC Says Douala-IX Strengthens Local Exchange. Its Public Snapshot Does Not Yet Measure It.
AFRINIC’s March community bulletin frames its support for Douala-IX as a way to strengthen local interconnection in Cameroon. The public evidence now available is useful, but it is an inventory of exchange attributes—not a measurement of the claimed operational result.
Story
RIPE’s RPKI Key Plan Is Not Yet a ROA Scope Receipt
RIPE NCC’s plan to move RPKI API keys toward OpenID Connect is a statement about a future access mechanism. It is not yet a public way to reconstruct which resource authority and which state-changing action stood behind an individual ROA change.
Story
LACNIC’s Bogon Guide Has Three Different Data Clocks.
A BGP filter can reject a route without saying why that route was rejected. Treating every rejected route as one security statistic may be convenient for capacity reporting, but it is too coarse to explain what the underlying evidence meant at the moment of the decision.
Story
APNIC Reissued Four Expired ASPAs. Its Repair Needs a State Receipt.
APNIC has reported a bounded correction: automatic renewal did not run, four ASPA entities expired, and the entities were reissued and published at 11:03. That is useful operational disclosure. It is not yet a measurement of what every repository, validator, router or customer…
Story
ARIN Kept Five Services Running Without Updates. Its Service-Level Report Has No Freshness Column
A registry can answer a question and still have nothing new to say. ARIN's planned July maintenance made that distinction visible: five reader-facing services remained operational while updates were not being published. The public service-level report measures availability well…
Story
LACNIC’s FORT Guide Skips the Signature Published Beside Its Tarball
The guide checks the validator after installation. It never checks the archive before extraction, even though the release already offered a digest, a detached signature and a public keyring.
Story
ARIN's Two Audit Findings Sound Opposite. They Test Different Controls
One ARIN Board record says no audited ticket was out of policy; another says inconsistencies appeared in every area examined. The difference is not a proven reversal in performance. It is a warning that audit findings become misleading when the test, standard and denominator are…
Story
LACNIC Calls Postman Its Current API. The Website Still Says ROAs Change by Serial Number
LACNIC gives an API operator two public descriptions of the same control surface. Its Registration API page says Postman holds the most current v3 documentation, while the route table beside that instruction describes modifying or removing one ROA by `serialNumber`. Follow the…
Story
APNIC Called RPKI Mirroring Marginal. Its NNIX Pilot Tests a Different Benefit
In October 2025, APNIC assessed a repository mirror as a short-lived aid during a long outage and called the benefit very marginal. Seven months later, its agreement with NNIX proposed a Hangzhou mirror pilot around latency, validation speed and data availability. The…
Story
AFRINIC's Current RPKI CPS Says It Manages Asia-Pacific
The Certification Practice Statement linked from AFRINIC's current resource-certification page is version 3.0 from May 2020. In its CA-termination clause, the registry assigns itself the Asia-Pacific region. AFRINIC and IANA assign that region to APNIC and place AFRINIC in Africa…
Story
AFRINIC Has 3,573 Address Entities Pointing to Geofeeds. Its Schema Still Has No Geofeed Field
AFRINIC’s public database already carries geofeed pointers at material scale, but it carries them as prose. The fallback is valid and useful. The missing question is whether a convention used by thousands of address records should remain a string that the schema cannot identify…
Story
ARIN Links ROAs to IRR Objects. Only the ROA Side Has a Visible Action Log
ARIN has made it possible for one routing-security action to leave two related records. That convenience is real. The evidentiary problem begins when the records later separate: the documented public history can explain the ROA, but not yet the whole operation that created…
Europe and Middle East Regional ISP Trends
SeaExpress’s AS31444 makes route visibility easier than route-authorisation accountability
SeaExpress’s AS31444 makes route visibility easier than route-authorisation accountability intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
Number Resource Society
A ROA Change Needs an Authorization-and-Withdrawal Ledger
A route can be Valid while the organization behind it has already forgotten who approved the authorization, what changed, or how to reverse it. ROA governance needs evidence that joins intent, publication, observation and withdrawal—not another screenshot of a green status.
Story
APNIC's Firewall Reboot Put Registry Writes and Repository Reads Under One Clock
APNIC says a network firewall detected a hardware fault and rebooted on 28 August, interrupting six named service surfaces for an incident window of eight minutes. The short duration is reassuring. The single clock is not a complete recovery statement, because the list stretches…
IETF
RPKI’s Publication BCP Can Say MUST. Operators Still Need to Show What They Do
The IETF is reviewing a Best Current Practice for the machinery that carries signed routing intentions from certificate authorities to the repositories used by relying parties. Its capitalized rules are deliberately strong. Its own text also says they are not formal…
Story
ARIN’s ROA Alerts Follow Deletion, Not the Change in Routing Authority
ARIN can commit several routing authorizations in one transaction, yet its documented alert boundary still follows a single verb: delete. Two public suggestions expose the resulting choice between inbox noise and silence. A safer design would report the net change once.
Story
LACNIC's Four-Vendor BGP Claim Needs the Configuration Column
One malformed Prefix-SID attribute reportedly met three different actions as it crossed the Internet: discard, propagation and session reset. LACNIC's new routing-security article makes the divergence visible. To make it reproducible, the comparison now needs to name the release…