AS7201 network operationalDual-stack IPv4 + IPv6Ports to 100GPeeringDBPeering policyNOC

Interconnection

Exchange points

The 7 US Internet exchanges where AS7201 meets other networks directly, and what each of them is.

Why it matters

Shorter paths between networks that are already near each other.

An Internet exchange point is a common switching fabric in a carrier-neutral building. Networks that join it hand traffic to one another directly instead of paying a third party to carry it, and the traffic stops leaving the region to get somewhere inside the region.

For a customer the effect is practical rather than theoretical: fewer networks between you and the places your users actually go, a shorter path for the regional traffic that makes up much of a normal day, and one less dependency on any single upstream.

In plain terms

  • Traffic between two networks on the same fabric does not transit a third one.
  • Regional traffic stays regional instead of routing out of the market and back.
  • Each exchange is another independent way off AS7201, alongside upstream transit and private interconnection.
  • Peering is settlement-free: neither side bills the other for the traffic they trade.

Where we are

7 exchanges, 4 states.

Each of these is a separate organization with its own membership and its own rules. What they have in common is that AS7201 is on the fabric and will peer with any network that asks and can meet a reasonable routing policy.

DET-IX Detroit Internet Exchange

Detroit / Southfield, MichiganIn service since 2014

The exchange for southeast Michigan. Before it existed, two networks a few miles apart in metro Detroit commonly reached each other by way of Chicago.

How it is run. Run as a non-profit by a volunteer board drawn from its own participants, with space and transport donated by a Michigan network operator.

Who meets there. Regional access providers, content and cloud networks, universities and K-12 networks, and enterprises that run their own routing.

GRR-IX Grand Rapids Internet Exchange

Grand Rapids, Michigan

The exchange for west Michigan, keeping Grand Rapids traffic in Grand Rapids rather than hauling it to Chicago and back.

How it is run. Operated by a Michigan network operator and open to participants without a port charge.

Who meets there. Regional providers, content networks, education networks and businesses across the west side of the state.

KCIX Kansas City Internet Exchange

Kansas City, Missouri

The Kansas City exchange, and the interconnection point for a large part of the central plains.

How it is run. Operated by IX.NET.

Who meets there. Regional and rural providers, content networks, education and government networks, and enterprises in the metro.

STLIX Saint Louis Internet Exchange

St. Louis, Missouri

The St. Louis exchange, sitting on one of the oldest east-west routes in the country.

How it is run. Operated by IX.NET.

Who meets there. Regional providers, content networks, education networks and enterprises across eastern Missouri and southern Illinois.

SpringIX Springfield Internet Exchange

Springfield, Missouri

The exchange for southwest Missouri and the Ozarks, a part of the country where the nearest alternative is several hundred miles away.

How it is run. Operated by IX.NET.

Who meets there. Rural and regional providers, content networks, education networks and local enterprises.

HOUIX Houston Internet Exchange

Houston, Texas

The Houston exchange, serving the upper Gulf Coast.

How it is run. Operated by IX.NET.

Who meets there. Regional providers, content networks, energy and industrial enterprises, and education networks.

SIX Seattle Internet Exchange

Seattle, WashingtonIn service since 1997

The Seattle exchange, in service since June 1997 and one of the principal interconnection points on the West Coast.

How it is run. A non-profit. Participants pay a one-time port fee and no recurring charge after that.

Who meets there. Access providers, content and cloud networks, transit carriers, education and research networks, and enterprises, from across the Pacific Northwest and well beyond it.

See AS7201 on PeeringDB

How to read this

What a listing here does and does not mean.

It means AS7201 is on that exchange’s fabric and exchanges traffic there with the networks that will peer with us. It does not mean every destination on the Internet is reachable over it — most of the Internet is not on any one exchange, which is why transit exists and why we buy it from more than one carrier.

It also is not a statement about capacity. How much we run at a given exchange is an operational matter that changes, and we do not publish it.

Want to peer?

We peer openly. Send us your ASN and your AS-SET and we will build the filter and bring the session up.

Our peering policy

Let’s scope your circuit.

Tell us the capacity you need and where you need it. An engineer reviews every request and comes back with a design and a price.