<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Billion on Wirez</title><link>https://wirez.top/tags/billion/</link><description>Recent content in Billion on Wirez</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 16 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wirez.top/tags/billion/index.xml" rel="self" type="application/rss+xml"/><item><title>BGP data: Filtering the 50% of routing noise</title><link>https://wirez.top/posts/bgp-data-filtering-the-50-of-routing-noise/</link><pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/bgp-data-filtering-the-50-of-routing-noise/</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 single peer, AS140627, generated 2.93 billion updates in one day, exposing the sheer scale of &lt;strong>pathological BGP noise&lt;/strong>.&lt;/p>
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">While the global enterprise networking market expands, the fundamental data powering these networks is increasingly corrupted by peers that flood collectors with repeated announcements reflecting no actual topological change. Ebrima Jaw and collaborators at RIPE NCC and the University of Oregon demonstrate that this concentration of noise inflates storage costs and obscures genuine routing intelligence within &lt;strong>MRT archives&lt;/strong>. &lt;a href="https://www.ripe.net/publications/docs/ripe-200/" target="_blank" rel="noopener noreferrer">Ripe 200&lt;/a>&lt;/p></description></item><item><title>CHINOG 2026: Real MPLS Shifts I See</title><link>https://wirez.top/posts/chinog-2026-real-mpls-shifts-i-see/</link><pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/chinog-2026-real-mpls-shifts-i-see/</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">The CHI-NOG 13 submission deadline of April 6, 2026, demands immediate attention from operators navigating a &lt;strong>$723.78 billion&lt;/strong> global market projection. Readers will examine how regional groups drive consensus on &lt;strong>Segment Routing&lt;/strong> and &lt;strong>zero-trust&lt;/strong> architectures, moving these from theoretical concepts to mandatory deployment patterns in large-scale environments. The discussion details the specific mechanical shifts required to support &lt;strong>AI workloads&lt;/strong>, analyzing the transition from general datacenter fabrics to specialized high-performance interconnects demanded by modern compute clusters.&lt;/p></description></item><item><title>APNIC IPv6 /32 vs /36: Why I Back the Larger Block</title><link>https://wirez.top/posts/apnic-ipv6-32-vs-36-why-i-back-the-larger-block/</link><pubDate>Tue, 24 Feb 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/apnic-ipv6-32-vs-36-why-i-back-the-larger-block/</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">&lt;a href="https://www.apnic.net/" target="_blank" rel="noopener noreferrer">APNIC&lt;/a> serves over four billion people, yet debates persist on reducing minimum &lt;strong>IPv6 address&lt;/strong> blocks to a /36. &lt;a href="https://blog.apnic.net/2026/01/20/ip-addresses-through-2025/" target="_blank" rel="noopener noreferrer">APNIC&amp;#039;s ip addresses through 2025&lt;/a>&lt;/p></description></item><item><title>RDAP and JSON: Handling 65 Billion Monthly Queries</title><link>https://wirez.top/posts/rdap-and-json-handling-65-billion-monthly-queries/</link><pubDate>Tue, 10 Feb 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/rdap-and-json-handling-65-billion-monthly-queries/</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 374 gTLDs disabling legacy services by September 2025, the Registration Data Access Protocol is now the mandatory backbone for internet identity. The era of unstructured text lookups has ended, replaced by a rigid, machine-readable architecture designed to handle the deluge of &lt;strong>AI-driven infrastructure&lt;/strong> demands. We dissect the strategic pivot triggered when ICANN removed contractual obligations for WHOIS in January 2025, a move that caused query volumes to plummet 60% within eight months. You will examine the technical transition toward &lt;strong>JSContact standards&lt;/strong>, which resolve long-standing privacy and formatting deficiencies inherent in the previous protocol. The data reveals a stark reality: automation drives this ecosystem, with monthly queries surging from seven billion to &lt;strong>65 billion&lt;/strong> in less than a year according to ICANN reports. As ARIN maintains steady query rates and bootstrapping services like rdap. Org handle millions of requests, the industry has effectively silenced the noisy, inefficient past. This is not merely a protocol upgrade; it is the essential plumbing required to sustain global connectivity as spending on artificial intelligence approaches &lt;strong>$2.5 trillion&lt;/strong>.&lt;/p></description></item></channel></rss>