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

Architecture & footprint

The AS7201 network

An independently operated Internet routing network — not a Layer 2 connection into somebody else’s carrier.

AS7201Independently operated ASN
7US Internet exchange points
5Carrier-neutral facilities
4Forms of interconnection
IPv4 + IPv6Throughout the network

Architecture

A multihomed Internet edge.

AS7201 is built around an edge with several ways out: upstream transit from more than one carrier, public peering at Internet exchange points, and private interconnection with networks we exchange enough traffic with to justify it.

Traffic a customer hands us becomes part of that routing domain. It gets our routing policy, our filtering, our traffic engineering and our interconnection — and it can leave by whichever of those paths is the best one at the time.

Combining transit with peering is what keeps the network from depending on any single external relationship, and it is what lets us shorten the path to the destinations our customers actually send traffic to.

Downstream networks are represented in our routing policy. Customer networks and other authorized routes are carried within AS7201's policy and propagated appropriately to external networks.

Network facts

Autonomous systemAS7201
Edge designMultihomed
Address familiesIPv4 and IPv6
Peering policyOpen
Exchange points7 across the United States
Route validationRPKI / ROA and IRR
Directory listingPeeringDB
Peering contactContact details

Routing diversity

Four ways traffic reaches the Internet.

Together these create a routing environment in which Internet traffic can take multiple potential paths rather than depending entirely on one upstream network.

Transit connectivity

Global Internet reachability through external backbone networks.

Public peering

Direct route exchange with networks reachable through Internet exchange points.

Private interconnection

Direct network-to-network interconnection where an exchange is not the right fit.

Customer BGP

Customers with their own ASN peer directly with us and advertise authorized prefixes.

Public Internet peering

Where AS7201 exchanges traffic.

Through these exchange environments we establish direct BGP relationships with other networks, rather than requiring every packet to traverse a conventional paid transit path.

Planned expansion markets

These are on the roadmap, not live today. We build where customer demand and interconnection opportunity line up — if you need capacity in one of them, tell us; committed demand moves a market up the list.

Chicago, ILDallas, TXAtlanta, GAMiami, FLPhoenix, AZLos Angeles, CA
DET-IXDetroit Internet ExchangeDetroit / Southfield, Michigan
GRR-IXGrand Rapids Internet ExchangeGrand Rapids, Michigan
KCIXKansas City Internet ExchangeKansas City, Missouri
STLIXSaint Louis Internet ExchangeSt. Louis, Missouri
SpringIXSpringfield Internet ExchangeSpringfield, Missouri
HOUIXHouston Internet ExchangeHouston, Texas
SIXSeattle Internet ExchangeSeattle, Washington

Direct peering can provide shorter AS paths, reduced dependency on intermediary transit networks, improved route diversity and more efficient delivery of traffic between Network Edge customers and participating networks. We continue to expand our interconnection footprint as opportunities become available.

Facilities

Where the network physically lives.

AS7201 is deployed in five carrier-neutral data centers across Michigan and Missouri — every 123NET facility in Michigan, plus NOCIX in North Kansas City. Each card shows the Internet exchanges reachable from that building and what is available there; you can take space in any of them, or cross connect to us from your own.

123NET

DC1 — Detroit Data Center

24700 Northwestern Hwy
Southfield, MI 48075

Detroit metro · Carrier-neutral

Exchanges on-net
DET-IXGRR-IXKCIX
Available here

Colocation · IP Transit · Point-to-Point Layer 2

123NET

DC2 — Southfield NW

24275 Northwestern Hwy
Southfield, MI 48075

Detroit metro · Carrier-neutral

Exchanges on-net
DET-IXGRR-IXKCIX
Available here

Colocation · IP Transit · Point-to-Point Layer 2

123NET

DC3 — Southfield W

24245 Northwestern Hwy
Southfield, MI 48075

Detroit metro · Carrier-neutral

Exchanges on-net
DET-IXGRR-IXKCIX
Available here

Colocation · IP Transit · Point-to-Point Layer 2

123NET

DC4 — Grand Rapids

400 76th St SW
Byron Center, MI 49315

Grand Rapids metro · Carrier-neutral

Exchanges on-net
DET-IXGRR-IX
Available here

Colocation · IP Transit · Point-to-Point Layer 2

NOCIX

1530 Swift

1530 Swift St
North Kansas City, MO 64116

Kansas City metro · Carrier-neutral

Exchanges on-net
KCIXSIXMICEHOUIXSpringIXSTLIX
Available here

Colocation · IP Transit · Point-to-Point Layer 2

Colocation in these facilities

Routing security

Modern routing-security practice, applied to AS7201.

These controls matter especially for a transit provider, because we have to protect both our customers and the wider Internet from accidental route leaks and invalid announcements.

RPKI / ROA validation

Helps validate whether an autonomous system is authorized to originate a particular IP prefix.

IRR-based routing policy

Machine-readable routing-policy information used to construct routing filters for customer and peer sessions.

Prefix filtering

Customer advertisements are restricted to explicitly authorized prefixes rather than blindly accepting arbitrary Internet routes.

BGP policy filtering

Import and export policy controls which routes may enter or leave each particular BGP relationship.

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.