Wellington Internet Exchange
Neutral Ethernet peering point on the CityLink network in Wellington
Wellington Internet Exchange (WIX) is a neutral peering point in Wellington, New Zealand, carried on CityLink's metropolitan Ethernet network. It lets connected organisations exchange traffic with each other directly instead of passing it through their internet service providers, using two route servers to keep the routing setup simple.
- Neutral Ethernet peering point on CityLink's Wellington metropolitan network
- Part of CityLink's ExchangeNET family of exchanges
- Two route servers simplify peering for participants
- First exchange to attach an OpenFlow-controlled device to the public internet
- Direct exchange keeps some traffic inside Wellington and off ISP links
What it is
Wellington Internet Exchange, usually shortened to WIX, is a neutral peering point in Wellington, New Zealand. It runs on top of CityLink's metropolitan Ethernet network and belongs to the ExchangeNET family of exchanges operated by that company. Organisations already attached to the CityLink network can hand traffic straight to one another across it instead of sending it out through their internet service provider first. That direct swap is called peering. WIX carries no published figures for membership, port count or traffic volume, and it is a layer for exchanging routes rather than a data centre building.
How it came about
WIX was set up so that parties on the CityLink metropolitan network could pass traffic between themselves without involving their ISPs. Managing those direct relationships by hand proved awkward: every network had to be entered on each router as a static route or a bilateral BGP session, and any addition, change or removal became slow and easy to get wrong once more than a handful of sessions existed. The exchange answered that with two route servers holding the routing details of all participants. It has been credited with two firsts: a distributed metropolitan Ethernet exchange of its kind, and the first exchange to attach an OpenFlow-controlled device to the public internet.
What runs inside
Members use WIX to peer, meaning they exchange traffic directly with one another. Because packets travel straight between the two parties, transfers are quicker and fewer copies of the same data cross the network through intermediate ISP routers. Some flows that would otherwise leave the city, or attract usage charges from an ISP, stay local and free of those charges. Two route servers carry the routing information for every participant, so most users need no manual route entries. Static routes and bilateral BGP sessions remain possible for anyone who wants a specific direct relationship.
The place
Wellington is the capital of New Zealand and the site of the CityLink metropolitan network on which WIX runs. The exchange is spread across that city-wide fibre rather than concentrated in one building, which is what makes it a distributed metropolitan exchange. Its purpose is local: keeping traffic that starts and ends in Wellington inside the city instead of sending it away and back.
Network and links
WIX sits on CityLink's metropolitan Ethernet network in Wellington and forms part of the ExchangeNET group of peering points. It offers two route servers that store the routing details of each participant, replacing the need for many separate bilateral Border Gateway Protocol sessions. An OpenFlow-controlled device, a switch whose forwarding is decided by software, was linked to the public internet through this exchange, a first for an internet exchange.
Questions people ask about Wellington Internet Exchange
What is the Wellington Internet Exchange for?
It lets organisations connected to CityLink's Wellington network pass traffic directly to each other instead of via their internet service provider. That direct exchange is called peering. It speeds transfers up and cuts the amount of duplicated traffic crossing intermediate ISP routers.
Who runs it?
CityLink operates the metropolitan Ethernet network that carries WIX, and the exchange sits within CityLink's ExchangeNET group of peering points in New Zealand.
How does peering work there?
Two route servers hold the routing details of every participant, so most members need no manual setup. Anyone wanting a specific direct link can still add static routes or bilateral Border Gateway Protocol sessions to their own routers.
What is special about it?
It has been credited as the first distributed metropolitan Ethernet-based internet exchange of its type, and it was the first exchange to connect an OpenFlow-controlled device, a software-managed switch, to the public internet.
Good reading and sources
The facts on this page come from the Wikipedia article "Wellington Internet Exchange", written by its contributors and used under the CC BY-SA 4.0 licence, and from its Wikidata record (CC0). EveryDatacenter rewrote the text in its own words, with AI assistance, and compares every page with the article to make sure no passage is copied. It may be reused under the same CC BY-SA 4.0 licence with a link back.
It may contain mistakes, and figures change over time. Nothing here is investment or buying advice. If something is wrong, tell us. Last refreshed 2026-11-14.