<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>RPKI on Wirez</title><link>https://wirez.top/tags/rpki/</link><description>Recent content in RPKI on Wirez</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 28 Apr 2026 16:02:57 +0000</lastBuildDate><atom:link href="https://wirez.top/tags/rpki/index.xml" rel="self" type="application/rss+xml"/><item><title>The Role of Cleared IPv4 Blocks in Modern Resource Management</title><link>https://wirez.top/posts/the-role-of-cleared-ipv4-blocks-in-modern-resource-management/</link><pubDate>Tue, 28 Apr 2026 16:02:57 +0000</pubDate><guid>https://wirez.top/posts/the-role-of-cleared-ipv4-blocks-in-modern-resource-management/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">On January 13, 2026, &lt;a href="https://www.arin.net/" target="_blank" rel="noopener noreferrer">ARIN&lt;/a> fulfilled 149 waiting list requests using just 59 reclaimed &lt;a href="https://en.wikipedia.org/wiki/IPv4" target="_blank" rel="noopener noreferrer">IPv4&lt;/a> blocks. &lt;a href="https://www.arin.net/blog/2026/01/22/ip-addresses-through-2025/" target="_blank" rel="noopener noreferrer">ARIN&amp;#039;s ip addresses through 2025&lt;/a> This distribution event highlights the critical reality that &lt;strong>cleared legacy resources&lt;/strong> remain the primary lifeline for enterprise connectivity despite decades of IPv6 advocacy.&lt;/p></description></item><item><title>RPKI route validation cuts $4.44M breach risk</title><link>https://wirez.top/posts/rpki-route-validation-cuts-444m-breach-risk/</link><pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/rpki-route-validation-cuts-444m-breach-risk/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">With cybercrime costing $10.5 trillion in 2026, ignoring &lt;strong>cryptographic route validation&lt;/strong> is financial negligence. The stability of the global network now demands that operators abandon fragile manual databases for &lt;strong>RPKI Route Origin Authorizations&lt;/strong> to prevent catastrophic hijacking. Readers will examine the critical transition from the error-prone &lt;strong>Internet Routing Registry&lt;/strong> to modern cryptographic standards that bind prefixes to origin ASNs automatically. We dissect the mechanics of &lt;strong>AS path authorization&lt;/strong>, detailing how routers drop invalid routes in real-time rather than relying on outdated static lists. Finally, the analysis covers practical deployment using &lt;strong>MyAPNIC&lt;/strong> and &lt;strong>DASH monitoring&lt;/strong> to visualize complex data streams. &lt;a href="https://blog.apnic.net/2025/12/12/nro-rpki-program-2025-in-review/" target="_blank" rel="noopener noreferrer">APNIC&amp;#039;s nro rpki program 2025 in review&lt;/a>&lt;/p></description></item><item><title>BGP hijacking in 2025: When forged docs beat RPKI</title><link>https://wirez.top/posts/bgp-hijacking-in-2025-when-forged-docs-beat-rpki/</link><pubDate>Tue, 31 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/bgp-hijacking-in-2025-when-forged-docs-beat-rpki/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">In July 2025, attackers bypassed cryptographic safeguards by manipulating a multinational provider through forged documents and social engineering. This incident proves that &lt;strong>BGP route hijacking&lt;/strong> has evolved from a purely technical exploit into a hybrid threat where human deception defeats &lt;strong>RPKI validation&lt;/strong>. While networks obsess over protocol anomalies, adversaries now target the administrative onboarding processes that grant legitimacy to malicious routes.&lt;/p></description></item><item><title>RPKI stops hijacking: Why 43% IPv4 coverage matters</title><link>https://wirez.top/posts/rpki-stops-hijacking-why-43-ipv4-coverage-matters/</link><pubDate>Tue, 31 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/rpki-stops-hijacking-why-43-ipv4-coverage-matters/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">With &lt;a href="https://en.wikipedia.org/wiki/IPv4" target="_blank" rel="noopener noreferrer">IPv4&lt;/a> ROA coverage hitting 43.17% per Kentik data, &lt;strong>RPKI adoption&lt;/strong> is no longer optional for serious network operators.&lt;/p>
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">The upcoming &lt;a href="https://www.arin.net/" target="_blank" rel="noopener noreferrer">ARIN&lt;/a> Deep Dive in Albuquerque highlights that &lt;strong>routing security&lt;/strong> has shifted from theoretical best practice to immediate operational necessity. &lt;a href="https://www.arin.net/resources/manage/rpki/hybrid/" target="_blank" rel="noopener noreferrer">ARIN&amp;#039;s hybrid&lt;/a> While the global PKI market explodes, the real story lies in the sharp divergence between networks that validate BGP announcements and those still vulnerable to hijacking. This article dissects the critical mechanics of &lt;strong>Resource Public Key Infrastructure&lt;/strong>, arguing that understanding the distinction between hosted and delegated models is now a core competency for any engineer managing autonomous systems.&lt;/p></description></item><item><title>RPKI validation stops 820k daily IoT attacks by 2026</title><link>https://wirez.top/posts/rpki-validation-stops-820k-daily-iot-attacks-by-2026/</link><pubDate>Mon, 23 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/rpki-validation-stops-820k-daily-iot-attacks-by-2026/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">With over 820,000 daily IoT attacks projected for early 2026, &lt;strong>RPKI deployment&lt;/strong> is the only viable defense against mass routing hijacks. The central thesis is clear: manual configuration is obsolete, and &lt;strong>cryptographic validation&lt;/strong> via &lt;strong>Route Origin Authorizations&lt;/strong> is now the baseline for operational survival.&lt;/p></description></item><item><title>RPKI validation gaps: Why 84% skip enforcement</title><link>https://wirez.top/posts/rpki-validation-gaps-why-84-skip-enforcement/</link><pubDate>Thu, 12 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/rpki-validation-gaps-why-84-skip-enforcement/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">With only 12.3% of analyzed ASes actively enforcing Route Origin Validation, global routing security remains critically fragile despite rising signature rates. The stark reality is that signing routes via &lt;strong>Resource Public Key Infrastructure&lt;/strong> means nothing without the mandatory filtering of invalid announcements at the network edge. Readers will examine the core mechanics of &lt;strong>Route Origin Validation&lt;/strong> and why current adoption metrics from APNIC data reveal a dangerous disconnect between signed prefixes and protected traffic. &lt;a href="https://blog.apnic.net/2025/07/22/how-can-rpki-can-be-made-quantum-safe/" target="_blank" rel="noopener noreferrer">APNIC&amp;#039;s how can rpki can be made quantum safe&lt;/a> We dissect the specific failure modes of legacy BGP verification and how &lt;strong>Autonomous System Provider Authorization&lt;/strong> closes the loop on path hijacking by cryptographically validating upstream relationships. The analysis moves beyond theory to present a concrete operational playbook for deploying these controls, drawing direct lessons from IDNIC&amp;#039;s successful mandate in Indonesia.&lt;/p></description></item><item><title>APNIC data shows routing silos collapsing fast</title><link>https://wirez.top/posts/apnic-data-shows-routing-silos-collapsing-fast/</link><pubDate>Fri, 06 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/apnic-data-shows-routing-silos-collapsing-fast/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">With TWNIC reporting 98% &lt;a href="https://datatracker.ietf.org/doc/html/rfc8200" target="_blank" rel="noopener noreferrer">IPv6&lt;/a> RPKI validity, National Internet Registry coordination has become the definitive mechanism for securing Asia Pacific&amp;#039;s routing infrastructure. &lt;a href="https://blog.apnic.net/2026/01/20/ip-addresses-through-2025/" target="_blank" rel="noopener noreferrer">&lt;a href="https://www.apnic.net/" target="_blank" rel="noopener noreferrer">APNIC&lt;/a>&amp;#039;s ip addresses through 2025&lt;/a> The strategic alignment of seven regional NIRs under APNIC governance is no longer administrative overhead but a critical defense against escalating route hijacking and resource exhaustion.&lt;/p></description></item><item><title>RTBH validation: Secure blackhole routing fast</title><link>https://wirez.top/posts/rtbh-validation-secure-blackhole-routing-fast/</link><pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/rtbh-validation-secure-blackhole-routing-fast/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">Validating &lt;strong>RTBH routes&lt;/strong> requires checking for the &lt;strong>BLACKHOLE community&lt;/strong> within seconds, not relying on stale IRR data. The central thesis is that operators must shift to &lt;strong>originAS-only validation&lt;/strong> specifically for blackhole traffic, enforcing strict community attachment while ignoring maxLength constraints to ensure rapid, secure mitigation.&lt;/p></description></item><item><title>RPKI in 2025: Why Path Validation Matters Now</title><link>https://wirez.top/posts/rpki-in-2025-why-path-validation-matters-now/</link><pubDate>Fri, 20 Feb 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/rpki-in-2025-why-path-validation-matters-now/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">With Unique &lt;a href="https://datatracker.ietf.org/doc/html/rfc9582" target="_blank" rel="noopener noreferrer">ASPA&lt;/a> Customer ASIDs surging 539% in 2025 per RPKIViews. Org data, the industry has decisively pivoted from simple origin checks to thorough path validation. Readers will examine how &lt;strong>RPKI&lt;/strong> evolved from a niche preference to a critical infrastructure component, underpinned by a 23% increase in ROA objects reaching over 344,000 entries according to ARIN and RIPE NCC trust anchors. &lt;a href="https://www.arin.net/vault/blog/2017/10/31/implementing-rpki-its-easier-than-you-think/" target="_blank" rel="noopener noreferrer">ARIN&amp;#039;s implementing rpki its easier than you think&lt;/a> We dissect the mechanics of &lt;strong>validation performance&lt;/strong>, noting that despite a 20% growth in total cache size, optimized implementations like rpki-client reduced wall time validation runs by 23% on standard hardware. The analysis further details the strategic imperative for &lt;strong>ASPA objects&lt;/strong>, where all Regional Internet Registries have committed to full service availability by late 2026.&lt;/p></description></item><item><title>RPKI path security: The shift past origin checks</title><link>https://wirez.top/posts/rpki-path-security-the-shift-past-origin-checks/</link><pubDate>Sun, 01 Feb 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/rpki-path-security-the-shift-past-origin-checks/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">A 539% surge in Unique &lt;a href="https://datatracker.ietf.org/doc/html/rfc9582" target="_blank" rel="noopener noreferrer">ASPA&lt;/a> Customer ASIDs proves the &lt;strong>RPKI database&lt;/strong> has shifted from simple origin checks to complex path validation.&lt;/p></description></item><item><title>RPKI signed docs now in MyAPNIC</title><link>https://wirez.top/posts/rpki-signed-docs-now-in-myapnic/</link><pubDate>Fri, 23 Jan 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/rpki-signed-docs-now-in-myapnic/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">As of January 23, 2026, &lt;a href="https://www.apnic.net/" target="_blank" rel="noopener noreferrer">APNIC&lt;/a> members can now generate &lt;strong>verifiable digital signatures&lt;/strong> directly within the MyAPNIC portal. &lt;a href="https://blog.apnic.net/2026/01/23/rscs-are-now-supported-in-myapnic/" target="_blank" rel="noopener noreferrer">Rscs are now supported in myapnic&lt;/a> This launch signals a critical pivot where &lt;strong>RPKI infrastructure&lt;/strong> evolves from a narrow routing security tool into a broad-spectrum mechanism for general-purpose document attestation. For over a decade, the industry treated &lt;strong>Route Origin Authorizations&lt;/strong> as the sole viable output of resource certification, ignoring the potential for broader identity proofing. That stagnation ends with the formal adoption of &lt;strong>RPKI Signed Checklists&lt;/strong>, which use existing IP address and &lt;strong>Autonomous System Number&lt;/strong> allocations to sign arbitrary digital files. Unlike previous methods demanding complex command-line manipulation, this update embeds the capability directly into the registry interface, effectively democratizing access to high-assurance cryptographic proofs.&lt;/p></description></item></channel></rss>