<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Traffic on Wirez</title><link>https://wirez.top/tags/traffic/</link><description>Recent content in Traffic on Wirez</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 10 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wirez.top/tags/traffic/index.xml" rel="self" type="application/rss+xml"/><item><title>Cloudflare's 500 Tbps capacity stops 31.4 Tbps attacks</title><link>https://wirez.top/posts/cloudflares-500-tbps-capacity-stops-314-tbps-attacks/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/cloudflares-500-tbps-capacity-stops-314-tbps-attacks/</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.cloudflare.com/" target="_blank" rel="noopener noreferrer">Cloudflare&lt;/a> now commands &lt;strong>500 Tbps&lt;/strong> of external capacity across 330+ cities, reserving the surplus explicitly as a &lt;strong>DDoS budget&lt;/strong>. You will examine the sheer physical reality of this &lt;strong>global backbone&lt;/strong>, dissect the &lt;strong>packet processing pipeline&lt;/strong> using eBPF and XDP for line-rate filtering, and explore how &lt;strong>Workers&lt;/strong> and &lt;strong>RPKI&lt;/strong> validate routes at the edge.&lt;/p></description></item><item><title>Akvorado IPv6 Visibility: See SOHO Traffic Clearly</title><link>https://wirez.top/posts/akvorado-ipv6-visibility-see-soho-traffic-clearly/</link><pubDate>Thu, 09 Apr 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/akvorado-ipv6-visibility-see-soho-traffic-clearly/</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">Deploying Akvorado on modest hardware like a 6-core Ryzen NUC eliminates blind spots in &lt;strong>IPv6-first networks&lt;/strong> instantly. This guide argues that open-source flow analysis via &lt;strong>Akvorado&lt;/strong> is now essential for SOHO administrators to visualize traffic without enterprise overhead. Readers will learn how &lt;strong>NetFlow enrichment&lt;/strong> leverages &lt;strong>SNMP queries&lt;/strong> to map interface indices, the mechanics of &lt;strong>packet sampling&lt;/strong> intervals, and a streamlined &lt;strong>Docker Compose&lt;/strong> deployment strategy.&lt;/p></description></item><item><title>Global traffic management: My take on the new K8s CRD</title><link>https://wirez.top/posts/global-traffic-management-my-take-on-the-new-k8s-crd/</link><pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/global-traffic-management-my-take-on-the-new-k8s-crd/</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">Routing traffic through AWS&amp;#039;s private backbone improves application performance by up to 60%, according to recent data from Amazon Web Services. This update fundamentally shifts global traffic management from manual, external scripts to a native, declarative &lt;strong>Kubernetes API&lt;/strong>. By embedding network logic directly into cluster definitions, organizations eliminate the configuration drift that has long plagued multi-region deployments.&lt;/p></description></item><item><title>IPv6 loops explained: Stop packet amplification now</title><link>https://wirez.top/posts/ipv6-loops-explained-stop-packet-amplification-now/</link><pubDate>Thu, 26 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/ipv6-loops-explained-stop-packet-amplification-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">Routing loops can exponentially amplify traffic when routers duplicate packets, a flaw prevalent in 34% of assigned &lt;a href="https://datatracker.ietf.org/doc/html/rfc8200" target="_blank" rel="noopener noreferrer">IPv6&lt;/a> blocks.&lt;/p>
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">The core thesis is clear: the sparse population of &lt;strong>IPv6 address space&lt;/strong> combined with misconfigured &lt;strong>provider-aggregatable&lt;/strong> assignments creates a fertile ground for &lt;strong>packet amplification&lt;/strong> that network operators are lazily ignoring. While cloud-native workloads drive adoption, the underlying routing hygiene has not kept pace, leaving infrastructure vulnerable to self-inflicted &lt;strong>DDoS attacks&lt;/strong>. Research indicates that despite the simplicity of the fix, the community fails to prioritize these dangerous misconfigurations, allowing unnecessary load to congest links and destabilize the global internet.&lt;/p></description></item><item><title>Public DNS logs reveal hidden CDN costs</title><link>https://wirez.top/posts/public-dns-logs-reveal-hidden-cdn-costs/</link><pubDate>Tue, 03 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/public-dns-logs-reveal-hidden-cdn-costs/</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 global companies losing nearly $400 billion annually to downtime, analyzing &lt;strong>DNS logs&lt;/strong> is a financial imperative, not just an IT task. You will learn how to extract strategic value from resolver data, architect real-time visualization pipelines using &lt;strong>ClickHouse&lt;/strong> and &lt;strong>Grafana&lt;/strong>, and enforce network automation through rigorous &lt;strong>Source of Truth&lt;/strong> principles.&lt;/p></description></item><item><title>Active path verification stops blackhole errors</title><link>https://wirez.top/posts/active-path-verification-stops-blackhole-errors/</link><pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/active-path-verification-stops-blackhole-errors/</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://datatracker.ietf.org/doc/html/rfc6480" target="_blank" rel="noopener noreferrer">RPKI&lt;/a> adoption for leased prefixes surging from 29.9% in 2021 to 71.0% by late 2024, validating &lt;strong>blackhole routes&lt;/strong> remains dangerously ambiguous. Blindly propagating these filters across all points of view often collapses complex routing topologies into a single, erroneous perspective that the source ASN never authorized.&lt;/p></description></item><item><title>Blackhole validation must use active path data now</title><link>https://wirez.top/posts/blackhole-validation-must-use-active-path-data-now/</link><pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/blackhole-validation-must-use-active-path-data-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">Strict path verification now overrides legacy IRR checks, as 2026 mandates enforce penalties for invalid blackhole route requests. The industry has decisively shifted from voluntary filtering to rigid &lt;strong>enforcement protocols&lt;/strong>, where regulators and Tier-1 providers penalize operators who fail to validate traffic forwarding paths accurately. Job Snijders confirmed in a March 2026 NANOG discussion that modern &lt;strong>blackhole validation&lt;/strong> must discard reliance on unverified IRR data, noting that such arbitrary lists lack the provenance required for today&amp;#039;s compliance environment. Instead, operators must verify if IP traffic is actively forwarded to the requesting entity before honoring any mitigation request.&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>ASPA records prove your upstream provider ties</title><link>https://wirez.top/posts/aspa-records-prove-your-upstream-provider-ties/</link><pubDate>Fri, 27 Feb 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/aspa-records-prove-your-upstream-provider-ties/</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.cloudflare.com/" target="_blank" rel="noopener noreferrer">Cloudflare&lt;/a> handles over 20% of global Internet traffic, yet standard BGP routing remains vulnerable to undetected path manipulation. &lt;a href="https://blog.cloudflare.com/bgp-hijack-detection/" target="_blank" rel="noopener noreferrer">Cloudflare&amp;#039;s bgp hijack detection&lt;/a> The deployment of &lt;strong>ASPA records&lt;/strong> under &lt;strong>RFC 9582&lt;/strong> represents the critical shift from verifying only traffic origins to validating the entire transmission path against configuration errors and malicious leaks. While &lt;strong>ROA&lt;/strong> systems successfully mitigate origin hijacks, they fail to detect when traffic traverses unauthorized intermediate networks, a gap this new cryptographic standard explicitly closes.&lt;/p></description></item><item><title>Routing security gaps threaten your 2026 supply chain</title><link>https://wirez.top/posts/routing-security-gaps-threaten-your-2026-supply-chain/</link><pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/routing-security-gaps-threaten-your-2026-supply-chain/</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 global cybercrime costs hitting $10.8 trillion in 2026, ignoring &lt;strong>Internet routing security&lt;/strong> is financial suicide. Dan Fidler&amp;#039;s February 2026 MANRS paper argues that enterprises must treat the global routing system as a critical, under-managed supply chain dependency rather than a background utility. The thesis is clear: voluntary operator goodwill has failed, and only aggressive &lt;strong>demand-side pressure&lt;/strong> via enterprise procurement can force the adoption of necessary safeguards.&lt;/p></description></item><item><title>Physical damage now drives global internet loss</title><link>https://wirez.top/posts/physical-damage-now-drives-global-internet-loss/</link><pubDate>Mon, 26 Jan 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/physical-damage-now-drives-global-internet-loss/</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">Only one government shutdown occurred in Q4 2027, proving &lt;strong>physical fragility&lt;/strong> now drives global connectivity loss more than political censorship. While 2025 saw a record 212 state-imposed outages across 28 countries, the final quarter marked a decisive shift where cable damage, power failures, and routine operational errors became the dominant disruptors. This transition highlights that the internet&amp;#039;s greatest vulnerability is no longer the kill switch, but the decaying infrastructure supporting.&lt;/p></description></item><item><title>Iran Network Blackout: Routing Withdrawn Fast</title><link>https://wirez.top/posts/iran-network-blackout-routing-withdrawn-fast/</link><pubDate>Tue, 13 Jan 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/iran-network-blackout-routing-withdrawn-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">Iran&amp;#039;s internet traffic collapsed by nearly 90% on January 8 as the state executed a near-total digital blackout. This event marks a strategic pivot from temporary censorship to permanent &lt;strong>digital isolation&lt;/strong>, effectively severing the domestic network from global infrastructure to crush dissent. Cloudflare Radar data confirms that connectivity did not merely degrade; it was surgically dismantled through coordinated protocol suppression. &lt;a href="https://blog.cloudflare.com/iran-protests-internet-shutdown/" target="_blank" rel="noopener noreferrer">Cloudflare&amp;#039;s iran protests internet shutdown&lt;/a>&lt;/p></description></item></channel></rss>