<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Byoip on Wirez</title><link>https://wirez.top/tags/byoip/</link><description>Recent content in Byoip on Wirez</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 20 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wirez.top/tags/byoip/index.xml" rel="self" type="application/rss+xml"/><item><title>Cloudflare Outage 2026: Why 1,100 Prefixes Failed</title><link>https://wirez.top/posts/cloudflare-outage-2026-why-1100-prefixes-failed/</link><pubDate>Fri, 20 Feb 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/cloudflare-outage-2026-why-1100-prefixes-failed/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:html -->
&lt;script type="application/ld+json">
{
 "@context": "https://schema.org",
 "@type": "FAQPage",
 "mainEntity": [
 {
 "@type": "Question",
 "name": "How many customer routes disappeared during the Cloudflare BYOIP incident?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "Approximately 25% of advertised BYOIP prefixes vanished from the network during the outage. This significant loss triggered BGP path hunting mechanics that prevented end-user connections from reaching their intended destinations successfully."
 }
 },
 {
 "@type": "Question",
 "name": "What specific behavior caused connections to fail while routes were missing?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "End users experienced BGP path hunting where traffic traversed networks searching for unreachable destinations. This loop-until-failure scenario persisted until connections timed out, affecting products relying on BYOIP for internet advertisement."
 }
 },
 {
 "@type": "Question",
 "name": "Why did some prefixes require manual engineering intervention to restore service?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "Automated re-advertisement attempts failed for roughly 300 prefixes due to a software bug removing configurations. Engineers had to manually restore these specific routes after dashboard self-remediation proved ineffective for those cases."
 }
 },
 {
 "@type": "Question",
 "name": "How long did the global disruption last before full service restoration?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "The disruption lasted 6 hours and 7 minutes while engineers worked to manually restore configurations. Most of this time was spent returning prefix configurations to their state prior to the initial automated change."
 }
 },
 {
 "@type": "Question",
 "name": "What scale of traffic volume was at risk during this configuration error?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "The incident occurred on a network handling 55 million HTTP requests per second globally. This massive volume illustrates how small configuration errors in the addressing API can scale rapidly into widespread service blackouts."
 }
 }
 ]
}
&lt;/script>
&lt;!-- /wp:html -->
&lt;!-- wp:html -->
&lt;style>
.faq-section { margin: 24px 0; padding: 24px 0; border-top: 2px solid #e5e7eb; }
.faq-section-title { color: #1a1a1a; font-size: clamp(1.2rem, 3vw, 1.4rem); font-weight: 700; margin-bottom: 24px; text-align: center; }
.faq-item { background: #fff; border: 1px solid #e5e7eb; border-radius: 8px; margin-bottom: 12px; overflow: hidden; transition: all 0.3s ease; }
.faq-item:hover { border-color: #2563eb; box-shadow: 0 4px 6px rgba(0,0,0,0.05); transform: translateY(-2px); }
.faq-question { background: #f9fafb; padding: 12px 16px; cursor: pointer; position: relative; transition: all 0.3s ease; border: none; width: 100%; text-align: left; font-family: inherit; display: block; }
.faq-question:hover { background: #e8f0fe; }
.faq-question-text { color: #1a1a1a; font-size: 1rem; font-weight: 600; line-height: 1.5; margin: 0; padding-right: 2rem; display: inline-block; }
.faq-answer { max-height: 0; overflow: hidden; transition: max-height 0.4s ease, padding 0.4s ease; padding: 0 16px; }
.faq-item.active .faq-answer { max-height: 1000px; padding: 0 16px 16px; }
.faq-answer-text { color: #4b5563; font-size: 1rem; line-height: 1.7; margin: 12px 0 0; }
&lt;/style>
&lt;script>
(function() {
 function initFAQ() {
 var qs = document.querySelectorAll(".faq-question");
 for (var i = 0; i &lt; qs.length; i++) {
 qs[i].addEventListener("click", function() {
 var item = this.closest(".faq-item");
 var wasActive = item.classList.contains("active");
 var allItems = document.querySelectorAll(".faq-item");
 for (var j = 0; j &lt; allItems.length; j++) { allItems[j].classList.remove("active"); }
 if (!wasActive) item.classList.add("active");
 this.setAttribute("aria-expanded", String(!wasActive));
 });
 }
 }
 if (document.readyState === "loading") {
 document.addEventListener("DOMContentLoaded", initFAQ);
 } else {
 initFAQ();
 }
})();
&lt;/script>
&lt;!-- /wp:html -->
&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> accidentally withdrew 1,100 BYOIP prefixes, breaking connectivity for a quarter of its bring-your-own-IP customers. (Cloudflare announces first quarter 2026 financial results)&lt;/p></description></item></channel></rss>