Why IXPs matter: Building Infrastructure Beyond the Hype

01/08/2025

Why IXPs matter: Building Infrastructure Beyond the Hype
Designed by Freepik

By Antonio Prado and Flavio Luciani

Internet Exchange Points (IXPs) are often overlooked in discussions about critical infrastructure. Yet their role in routing stability, local resilience, and digital sovereignty is undeniable. In this article, we explore what happens when IXPs fail, and why classifying them as critical infrastructure is not just a bureaucratic formality, but a systemic necessity.

When IXPs fa:il real-world consequences and lessons

What is an IXP and why does it matter?

An Internet Exchange Point is a physical interconnection facility where multiple Autonomous Systems (ASes) exchange IP traffic. Instead of routing traffic via expensive upstream providers, networks can peer directly, reducing cost, latency, and dependence on transit. Most IXPs consist of high-performance switching infrastructure, route servers, and optional measurement and monitoring tools. Beyond technical efficiency, IXPs support national resilience, improve user experience by keeping traffic local, and serve as critical coordination nodes in times of crisis. Yet, despite their foundational role in Internet architecture, IXPs often operate in the shadows of public awareness and policy frameworks. As a result, their vulnerabilities tend to be underestimated.

The visibility paradox

Despite their crucial function, IXPs are often invisible in both public discourse and infrastructure policy. This “visibility paradox” creates three systemic risks:

  1. economic optimization over resilience. Traffic is increasingly routed through major IXPs due to cost and efficiency, concentrating risk.
  2. dependency of smaller networks. Many small ISPs depend on a single IXP to access affordable connectivity and major content providers.
  3. topological centralization. A handful of physical IXP locations carry disproportionate amounts of regional traffic, creating structural vulnerabilities.

When IXPs go down: real-world examples

Let’s examine what happens when an IXP fails. Below are real incidents that illustrate systemic dependencies on these nodes.

Kenya (KIXP): building resilience on a budget

In 2000, the Kenyan government attempted to block the launch of the Kenya Internet Exchange Point. Only strong advocacy from the local technical community preserved it. Since then, KIXP has reduced national transit costs by over 70% and improved routing stability despite limited resources.

Sudan: total national isolation

During the 20212023 Internet shutdowns, Sudan’s lack of a robust local IXP meant that even internal traffic was cut off. The absence of domestic interconnection rendered the country completely dependent on international links, which were politically and technically severed.

(Free access, no subscription required)

Source: Cloudflare

Brazil (IX.br): Multistakeholder-led redundancy*

Brazil’s IX.br, coordinated by CGI.br, operates 35 IXP locations. During the 2020 pandemic surge, its wide geographical coverage helped absorb massive traffic increases. Its model shows that collaborative coordination and decentralization enhance systemic resilience.

Germany (DE-CIX): power failure, wide impact

In 2018, a power outage at Interxion FRA5 (hosting a major DE-CIX switch) caused partial IXP failure. The resulting loss of BGP visibility affected routes across Europe. Even with built-in redundancy, this incident highlighted how dependent many ASes are on a single physical location.

The views expressed by the authors of this blog are their own and do not necessarily reflect the views of LACNIC.

0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments