Transit connectivity
Global Internet reachability through external backbone networks.
Architecture & footprint
An independently operated Internet routing network — not a Layer 2 connection into somebody else’s carrier.
Architecture
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.
| 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 details |
Routing diversity
Together these create a routing environment in which Internet traffic can take multiple potential paths rather than depending entirely on one upstream network.
Global Internet reachability through external backbone networks.
Direct route exchange with networks reachable through Internet exchange points.
Direct network-to-network interconnection where an exchange is not the right fit.
Customers with their own ASN peer directly with us and advertise authorized prefixes.
Public Internet peering
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.
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.
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
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.
Detroit metro · Carrier-neutral
Colocation · IP Transit · Point-to-Point Layer 2
Detroit metro · Carrier-neutral
Colocation · IP Transit · Point-to-Point Layer 2
Detroit metro · Carrier-neutral
Colocation · IP Transit · Point-to-Point Layer 2
Grand Rapids metro · Carrier-neutral
Colocation · IP Transit · Point-to-Point Layer 2
Kansas City metro · Carrier-neutral
Colocation · IP Transit · Point-to-Point Layer 2
Routing security
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.
Helps validate whether an autonomous system is authorized to originate a particular IP prefix.
Machine-readable routing-policy information used to construct routing filters for customer and peer sessions.
Customer advertisements are restricted to explicitly authorized prefixes rather than blindly accepting arbitrary Internet routes.
Import and export policy controls which routes may enter or leave each particular BGP relationship.
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.