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
AFRINIC's Certificate Deadline Split Into Four Clocks
The 18 August notice described one cutoff. Operations produced four different clocks: the announced date, the upstream source, the portable release and the validator runs that networks could actually observe. They did not strike together.

IETF
RPKI draft proposes a separate credential for blackhole routes
RPKI draft proposes a separate credential for blackhole routes 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…

Story
India’s Routing-Security Coverage Is Rising Faster Than Invalid-Route Filtering
APNIC’s latest India ecosystem review points to rapid gains in RPKI coverage alongside a much smaller reported share of networks filtering invalid announcements. The gap is a monitoring problem, not a verdict on national resilience.

IETF
IETF Updates Erik Sync Draft for RPKI Publication
An updated IETF Internet-Draft describes a relay-based way to distribute RPKI publication data. It is a current design proposal, not a new Internet standard or a deployment announcement.

Story
The Consequential Verb Was Publish: AFRINIC’s Resolution 202201.673 and the Limits of an AS0 Mandate
In January 2022, AFRINIC’s Board ratified a policy that asked the registry to do something concrete with its own cryptographic machinery: identify IPv4 and IPv6 inventory recorded as unallocated or unassigned, create covering AS0 Route Origin Authorisations, and publish the…

Story
The Resolution Between Consensus and Execution
Resolution 202201.673 crossed a narrow but consequential threshold: AFPUB-2019-GEN-006-DRAFT03 was the same proposal before and after the AFRINIC Board acted in January 2022, yet the private corporation’s responsibility was not. Consensus had recommended a course; ratification…

Story
The Meaning of “End”: AFRINIC’s Draft 3 and the Discipline of Negative Routing Assertions
One sentence added to an AFRINIC policy proposal in April 2021 drew a vital line: reclaimed number resources should enter the registry’s AS0 coverage only after reclamation ends. That line can protect routing security, but only if “the end” is made into a state that outsiders can…

Story
What USD 71,217 Can — and Cannot — Prove About AFRINIC’s RPKI Priority
In June 2020, AFRINIC’s Board chose to move a single total of USD 71,217 from the MyAFRINIC and infrastructure budgets to the RPKI project. The precision of the sum makes the choice inspectable, but it does not turn an approval into delivery: the consequential story lies in the…

Story
Five Minutes at the Registry, Longer on the Network
AFRINIC’s second draft of its RPKI AS0 proposal introduced a narrow but important restraint: a separate trust anchor could let networks choose whether to receive the registry-generated warning and let observers measure it apart from ordinary holder authorisations. That choice…

Story
When ‘No Consensus’ Must Give Reasons: The 2020 RPKI AS0 Draft 2 Appeal
In 2020, a proposal for a machine-readable routing-security signal was halted by a distinctly human judgement: AFRINIC’s co-chairs assessed that its second draft lacked consensus. The ensuing appeal put the negative decision itself under scrutiny. Its enduring significance lies…

Story
The Zero That Had to Move First: AFRINIC’s First AS0 Draft and the Design of Reversible Warning
On 4 November 2019, AFRINIC published its first proposal to originate AS0 ROAs for address space recorded as unallocated. The idea offered operators a useful authenticated warning: ordinary public routing should not emerge from space that the registry ledger said nobody had been…

Global Regional ISP Trends
An IPv4 lease expiry is a routing deadline, not an invoice date
The critical distinction behind **What Happens When an IPv4 Lease Expires: A Deep Analysis of Market Realities** is easy to miss: a commercial IPv4 lease does not behave like the DHCP lease on a laptop. When contractual access to public address space ends, continuity depends on…

Global Regional ISP Trends
Hosting concentration needs an independent recovery path
Rahkar-Pardazesh-Khavarmianeh appears concentrated in one prefix and observed upstream. A small routing change can therefore affect many hosted services at once.

Story
APNIC capacity connects records, routes and members
A regional registry is more than an allocation database. In Asia Pacific, usable capacity also depends on routing security, local skills and member accountability.

Global Regional ISP Trends
RIP needs a bounded domain and an exit plan
Routing Information Protocol is simple enough to teach and operate in a small network. Its convergence and scale limits become risk when the network outgrows that boundary.

Global Cloud Services Trends
Changing an IP address needs a dependency inventory
The routing change may take minutes; hidden allowlists, DNS records, certificates, reputation systems and support procedures can take far longer to follow.

Global Cloud Services Trends
Network architecture needs visible failure domains
A diagram of devices is not an architecture unless it shows which links, controls and people can fail together.

Global Cloud Services Trends
A static IP is an identifier, not a security control
A stable address simplifies hosting, monitoring and partner allowlists. It also gives attackers a durable target and does not authenticate the system behind it.

Story
AFRINIC's 2010 infrastructure reinvestment jumped to USD 346,203—but the office took most of it
AFRINIC's own presentations show a Board-authorised capital programme whose largest disclosed result was a new office, not a documented technical transformation. The useful question is not whether premises can count as infrastructure, but whether each capital decision can be…

Europe and Middle East Regional ISP
MIX's 2025 peering-LAN resilience note made route reconvergence an accountability test
MIX made a deliberately narrow point in June 2025: a peering LAN should not automatically become a single point of failure for a properly prepared network, because entities can retain transit capacity and diversify where they peer. The harder part comes after that design claim.…
