Transit connectivity
Global Internet reachability through external backbone networks.
Architecture
A routing domain of its own.
Rather than functioning as a simple Layer 2 connection into another carrier, customer traffic entering AS7201 becomes part of a network with its own routing policies, interconnection relationships, route filtering, traffic-engineering capabilities and Internet exchange connectivity.
The architecture is built around a multihomed Internet edge, providing multiple potential paths between customer networks and the global Internet. Upstream connectivity is supplemented by direct and exchange-based interconnection with other autonomous systems.
This combination of transit and peering reduces dependence on any one external network and gives AS7201 considerably greater control over Internet routing than a single-provider transit architecture.
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 system | AS7201 |
| Edge design | Multihomed |
| Address families | IPv4 and IPv6 |
| Peering policy | Open |
| Exchange points | 7 across the United States |
| Route validation | RPKI / ROA and IRR |
| Directory listing | PeeringDB |
| Peering contact | Contact form |
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.
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.
Solid markers are live exchange points, plotted at true geographic position (Albers equal-area projection). Hollow amber markers are planned expansion markets, not yet live. Connecting lines indicate interconnection relationships, not physical fiber routes.
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.
DC1 — Detroit Data Center
24700 Northwestern HwySouthfield, MI 48075
Detroit metro · Carrier-neutral
Exchanges on-net
DET-IXGRR-IXKCIX
Available here
Colocation · IP Transit · Point-to-Point Layer 2
DC2 — Southfield NW
24275 Northwestern HwySouthfield, MI 48075
Detroit metro · Carrier-neutral
Exchanges on-net
DET-IXGRR-IXKCIX
Available here
Colocation · IP Transit · Point-to-Point Layer 2
DC3 — Southfield W
24245 Northwestern HwySouthfield, MI 48075
Detroit metro · Carrier-neutral
Exchanges on-net
DET-IXGRR-IXKCIX
Available here
Colocation · IP Transit · Point-to-Point Layer 2
DC4 — Grand Rapids
400 76th St SWByron Center, MI 49315
Grand Rapids metro · Carrier-neutral
Exchanges on-net
DET-IXGRR-IX
Available here
Colocation · IP Transit · Point-to-Point Layer 2
1530 Swift
1530 Swift StNorth Kansas City, MO 64116
Kansas City metro · Carrier-neutral
Exchanges on-net
KCIXSIXMICEHOUIXSpringIXSTLIX
Available here
Colocation · IP Transit · Point-to-Point Layer 2
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.