Summary

  • Internet Society’s 13 October revision updates a 2015 brief: the policy test is now whether local interconnection remains sustainable amid centralization, not simply whether an IXP has been built.
  • The brief welcomes remote and virtual peering when it expands reach, but worries about substitution for local participation; it also says IXP traffic statistics omit other forms of interconnection.

The important change in Internet Society’s new Internet Exchange Point (IXP) brief is in its unit of analysis. The 2015 version made the case for establishing exchanges and keeping local traffic local. The revision, published on 13 October 2026, says that in many countries the question has moved on: can a local interconnection ecosystem remain sustainable as interconnection concentrates in a smaller set of facilities, platforms and locations?

That is a more demanding question than counting exchanges. The brief describes an ecosystem as active peering communities, viable IXP operations, local hosting and content, data centres, technical capacity and varied ways to interconnect. Its proposed policy response is accordingly broader than building a switch fabric: preserve neutrality and voluntary peering, remove participation barriers, and avoid regulation that treats an exchange as a telecom carrier merely because networks meet there.

The qualification on remote peering matters. A network can reach an exchange without maintaining equipment at the exchange site. Virtual services can also make interconnection easier. The brief acknowledges those gains and says these arrangements are not inherently harmful. Its concern is substitution: if remote access or a centralized platform displaces local participation, the exchange may continue to report traffic while losing the people, operators and skills that made it a local institution.

A route server helps explain the distinction between the service and the traffic. Under the model described in RFC 7947, it distributes routing information among participants; it normally does not forward their packets. The local switching fabric, each participant’s routing policy, transport to the exchange, and the commercial relationship all remain separate parts of the arrangement. “Connected to an IXP” therefore says little by itself about where a network is located, which local peers it reaches, or how much capacity stays under local operational control.

The brief also supplies a useful limit on its own scorecard: published IXP traffic statistics do not capture every form of interconnection. Private peering can bypass a public exchange, and measurement studies have found that visible routing data can miss links. Traffic growth may show more activity on one fabric; it cannot alone establish diversity, affordability, resilience or community health. Membership counts have a similar limitation if they do not distinguish active local participants from remote access or selective peering.

On affordability, Internet Society points to its own analysis of 50 countries receiving IXP development and peering-ecosystem support, reporting that broadband affordability improved in 40. The organization also acknowledges competition, regulation, international connectivity and local economic conditions as contributing factors. That is an association reported by the sponsoring organization, not a controlled estimate of what an IXP caused.

The 2026 brief is best read as a policy agenda, not an ecosystem audit. It identifies a shift from deployment to persistence and names the institutional conditions that could support it. Whether those conditions are changing in any particular country requires a separate record: local and remote participant shares, route and traffic visibility, private interconnection, hosting and content presence, operating finances, governance, training and the response to outages. The exchange can remain on the map while the ecosystem around it thins. The new policy question is how to tell the difference.

Sources