Layer 3 IP Transit
BGP transit on AS7201 with full tables, partial routes or a default route. Announce your own prefixes, use your own ASN, and take a hand-off anywhere from 100M to 100G.
IP Transit detailsWhat we do
Three services. One network.
Network Edge sells the parts of the Internet that other providers bundle away from you: the routing, the space and the transport.
Colocation
Cabinets, partial racks and cages across five data centers in Michigan and Missouri, with A+B power, cross connects and AS7201 on-net in every one.
Colocation detailsPoint-to-Point Layer 2
Transparent Ethernet circuits between your sites, data centers and exchange points. Your VLANs and your frames pass end to end — we stay out of your Layer 3.
Layer 2 detailsIndependent BGP network
Not a resale of somebody else’s Internet connection.
Plenty of "IP transit" on the market is a Layer 2 hand-off into one upstream carrier. Every packet takes that carrier’s path, inherits that carrier’s outages and follows that carrier’s policy.
Network Edge operates AS7201 as its own autonomous system. Traffic entering our network becomes part of a routing domain with its own policy, its own filtering, its own traffic engineering and its own interconnection relationships.
Independent routing policy. Import and export policy, prefix filtering and route validation are ours to set — not inherited from an upstream carrier’s product tier.
What that buys you
- Multiple potential paths to the global Internet, not one
- Routing decisions made on reachability, path quality and policy
- Direct peering that shortens AS paths where it is available
- Your ASN stays visible to the global routing table
- Freedom to add your own additional transit and peering
- An operator you can reach who speaks BGP
Public Internet peering
Connected where traffic actually changes hands.
AS7201 participates at Internet exchange points across the United States, establishing direct BGP relationships instead of pushing every packet down a paid transit path.
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
Open peering policy
No presence at multiple common sites, no minimum traffic ratio, no mandatory contract. If there is a reasonable technical benefit to either network, we want the session.
Read the peering policyTransit + Peering
Upstream transit provides global reachability; exchange and private interconnection provide directness. Together they give AS7201 path diversity a single-provider design cannot.
See the networkPrivate interconnection
Where an exchange is not the right fit, we can build direct network-to-network interconnection with your ASN instead.
Discuss an interconnectRouting security
Filters that protect you and the rest of the Internet.
A transit provider that accepts anything is a hazard. Our policy is built to keep invalid announcements and accidental route leaks out of the global table.
RPKI / ROA validation
Route origin validation checks whether an autonomous system is actually authorized to originate a given prefix.
IRR-based filtering
Machine-readable routing policy, so customer and peer filters can be generated automatically from published objects.
Prefix filtering
Customer sessions accept explicitly authorized prefixes. We do not blindly take whatever arrives on a BGP session.
BGP policy filtering
Import and export policy governs which routes may enter or leave each individual relationship.
Who we serve
Built for networks that actually use BGP.
Our customers are typically running infrastructure, not a branch office. If routing control is operationally important to you, this service is designed around that assumption.
Internet service providersHosting providersDedicated server operatorsData center operatorsContent delivery networksCloud platformsSaaS platformsVPN networksStreaming networksRegional carriersColocation customersEnterprises with their own ASN
Common designs we build
- Single-location IP transit with a full table
- Redundant transit over diverse physical paths
- Multiple BGP sessions across multiple routers
- Multi-site architectures across several data centers
- Customer ASN migration and new ASN deployment
- Internet exchange connectivity and private interconnects
- Dedicated transport combined with IP transit
- Networks whose bandwidth grows faster than an enterprise product allows
Questions
Frequently asked
Do I need my own ASN to buy IP transit?
No. If you operate your own ASN and IP space we will run BGP with you and propagate your prefixes. If you do not, we can deliver a default route, static routing or provider-assigned addressing where applicable, and help you move to your own resources later.
Is Network Edge reselling another ISP?
No. AS7201 is operated as an Internet network in its own right, with its own routing policy, upstream relationships, Internet exchange presence and customer BGP sessions. Traffic entering AS7201 has multiple potential paths to the wider Internet rather than a single carrier.
Do you support IPv6?
Yes. Dual-stack is delivered over the same physical port, normally as a separate BGP session per address family. The same routing policy, prefix filtering and origin validation apply to both.
Will you peer with my network?
Most likely. We maintain an open peering policy with no requirement for multiple common locations, minimum traffic ratios or a peering contract. Send a peering request through the contact form and we will get a session up.
How do you decide what to accept from my session?
We build your prefix filters from the routing policy you publish — your IRR objects and your ROAs — and apply RPKI-based origin validation. Send us the prefix list you intend to announce and we will confirm the filter before turn-up.