RPKI / ROA validation
Validates whether an autonomous system is authorized to originate a particular IP prefix before we accept and propagate it.
Transit that behaves like a network, not a reseller agreement.
Unlike connectivity products built around the resale of a single upstream Internet provider, Network Edge operates its own autonomous system, maintains independent BGP routing policy, participates in public Internet peering and uses a multihomed network architecture.
That lets us make routing decisions based on reachability, path quality, network policy and available interconnection — rather than simply forwarding all customer traffic through a single carrier.
Our IP Transit service suits customers operating their own Autonomous System Number and IP address space, as well as customers who need Internet connectivity without running a full independent BGP network.
At a glance
| Autonomous system | AS7201 |
| Port speeds | 100M / 1G / 10G / 25G / 40G / 100G |
| Address families | IPv4 and IPv6 |
| Route options | Full table, partial, default, static |
| Customer ASN | Supported |
| Customer IP space | Supported (IPv4 and IPv6) |
| Validation | RPKI / ROA and IRR based |
| Public listing | PeeringDB |
Delivery options
Structure the service around your network, not ours.
Depending on your requirements, connectivity can be built around any combination of the following.
- Full BGP routing
- Customer BGP announcements
- Default-route delivery
- Selective routing
- Static routing
- Customer-owned IPv4 address space
- Customer-owned IPv6 address space
- Provider-assigned addressing where applicable
- Multi-router and redundant network designs
- High-bandwidth Internet connectivity
- Dedicated point-to-point interconnection into the backbone
- Diverse physical paths between sites
Customers operating their own ASN establish BGP directly with AS7201, allowing their prefixes to propagate through our upstream and peering relationships. That makes the service well suited to networks needing considerably more routing flexibility than a conventional DIA or broadband Internet connection.
BGP and routing engineering
Built for customers that actually use BGP.
Our architecture accommodates the controls a service-provider network expects to have, on day one, without a change-request queue.
Scope a session- Full Internet routing tables
- Customer prefix advertisement
- Customer ASN connectivity
- BGP communities
- Local-preference routing policies
- AS-path traffic engineering
- Route filtering
- Prefix filtering
- IRR-based routing policy
- RPKI-based route validation
- IPv4 and IPv6 BGP
- Default-route configurations
- Redundant BGP sessions
- Multiple physical interconnections
- Multi-site network architectures
- Customer ASN migration support
Routing security
Modern routing hygiene, applied to every session.
As a transit provider we have to protect both our customers and the wider Internet from accidental route leaks and invalid announcements.
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 accepting arbitrary Internet routes.
BGP policy filtering
Import and export policy controls which routes may enter or leave each particular BGP relationship.
Engineered for sustained volume
- Hosting providers
- Dedicated server operators
- Cloud platforms
- Content delivery infrastructure
- VPN networks
- Internet service providers
- Regional networks
- Data-center operators
- SaaS platforms
- Streaming and content networks
- Other bandwidth-intensive infrastructure
High-bandwidth connectivity
Room to grow past the enterprise ceiling.
We can provide ports from 100M all the way up to 100G.
100M1G10G25G40G100G
Network Edge IP Transit is intended to scale beyond ordinary enterprise Internet connectivity. Connectivity is delivered over appropriately sized Ethernet interfaces and transport circuits based on your required capacity and location.
We would rather work with a customer whose bandwidth requirement grows significantly over time than force that customer into a traditional small-enterprise Internet service model.
Network-to-network transit
Bring your ASN. Keep your ASN.
Network Edge is particularly suited to providing wholesale IP transit to another autonomous system. A customer brings:
- Their ASN
- Their IP addresses
- Their routing policy
- Their network infrastructure
…and uses AS7201 for global Internet reachability. We act as your Internet transit provider while you retain control and ownership of your routing resources.
This is fundamentally different from buying ordinary dedicated Internet access. Your ASN remains visible to the global Internet and you keep the ability to establish additional transit and peering relationships independently.
Flexible network architecture
Because we operate at the BGP and carrier-network level, the service does not have to fit a single standardized Internet-access configuration. Solutions can be engineered around:
- Single-location IP transit
- Redundant transit connections
- Diverse physical paths
- Multiple routers
- Multiple data centers
- Multiple BGP sessions
- Customer ASN migration
- New ASN deployments
- Internet exchange connectivity
- Private network interconnection
- Dedicated transport combined with IP transit
- Regional network expansion
Why Network Edge
What you are actually buying.
Connectivity into an independently operated BGP network with its own ASN, routing policy, peering strategy, multihomed architecture and exchange presence — and direct control over how traffic enters and leaves it.
- Carrier-grade BGP IP transit
- An independently operated autonomous system
- Multihomed Internet architecture
- Public Internet exchange connectivity
- Direct network peering
- Customer BGP support
- IPv4 and IPv6 capability
- IRR and RPKI-aware routing policy
- High-bandwidth connectivity
- Flexible routing configurations
- Support for customer-owned ASN and IP resources
- Traffic-engineering suitable for service-provider networks
- A growing US interconnection footprint
The objective is straightforward: reliable, scalable Internet transit with as much routing diversity, direct interconnection and network-level control as practical. For organizations operating serious Internet infrastructure, that distinction matters.
Questions
Frequently asked
What routing options can I take?
Full Internet routing tables, partial or selective routes, a default route, or static routing. Dual-stack IPv4 and IPv6 are available on all of them, and redundant sessions across multiple routers are supported.
Can I announce my own IPv4 and IPv6 space?
Yes — that is the normal case. Customers with their own ASN establish BGP directly with AS7201 and their prefixes propagate through our upstream and peering relationships. Provider-assigned addressing is available where applicable if you do not hold your own space.
What do you need before you turn a session up?
Your ASN, the prefixes you intend to announce, the IRR objects or ROAs backing them, and the port and location you want the hand-off on. We build the filters from your published routing policy.
Do you support BGP communities and traffic engineering?
Yes. BGP communities, local-preference policy, AS-path based engineering, route filtering and prefix filtering are all part of the service for customers who need to steer traffic.
Can you scale past a normal enterprise circuit?
That is what the product is for. Connectivity is delivered over appropriately sized Ethernet interfaces and transport circuits, and we expect customer bandwidth to grow rather than forcing you into a small-business Internet tier.