<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Leaks on Wirez</title><link>https://wirez.top/tags/leaks/</link><description>Recent content in Leaks on Wirez</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 23 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wirez.top/tags/leaks/index.xml" rel="self" type="application/rss+xml"/><item><title>Route leak lessons: What the 25-minute Cloudflare outage...</title><link>https://wirez.top/posts/route-leak-lessons-what-the-25-minute-cloudflare-outage/</link><pubDate>Fri, 23 Jan 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/route-leak-lessons-what-the-25-minute-cloudflare-outage/</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 automation error triggered a 25-minute &lt;a href="https://datatracker.ietf.org/doc/html/rfc4271" target="_blank" rel="noopener noreferrer">BGP&lt;/a> route leak that disrupted &lt;a href="https://datatracker.ietf.org/doc/html/rfc8200" target="_blank" rel="noopener noreferrer">IPv6&lt;/a> traffic across &lt;a href="https://www.cloudflare.com/" target="_blank" rel="noopener noreferrer">Cloudflare&lt;/a>&amp;#039;s Miami infrastructure on January 22, 2026. &lt;a href="https://blog.cloudflare.com/route-leak-incident-january-22-2026/" target="_blank" rel="noopener noreferrer">Cloudflare&amp;#039;s route leak incident january 22 2026&lt;/a> This incident highlights that despite industry progress, manual configuration errors remain a critical vulnerability in global routing stability. Readers will learn the precise mechanics of &lt;strong>RFC 7908 violations&lt;/strong>, analyze the specific AS path anomalies involving &lt;strong>AS13335&lt;/strong>, and explore how &lt;strong>RFC 9234&lt;/strong> adoption offers a viable path toward automated prevention.&lt;/p></description></item></channel></rss>