IP Transit with egress
to the entire Internet
Over a multihomed network that absorbs your peaks.
Internet
Multihomed network
Your port
The quote is scoped from the commit and the burst scheme.
19
PoPs
13
Countries
up to10 Gbps
Commit
24/7
Critical incidents
up to99.9%
Network SLA
Real‑world use cases
E-commerce with campaign peaks
Bursts without renegotiating
Your commit covers baseline traffic and automatic bursts absorb campaign days, measured at the 95th percentile instead of forcing you to buy the peak all month.
Growing ISP or WISP
Multihomed upstream on one port
You take a full table from a network that is already multihomed to several upstreams, so a carrier failure is resolved inside IPXON's AS instead of at your edge.
SaaS with users across countries
Transit in your users' country
Order transit at the PoP in the country where you operate and egress is resolved from there. Add one PoP per market without changing provider.
Capabilities
Service scope
Commits from 100 Mbps to 10 Gbps
Commit at the level your sustained traffic reflects and step up when consumption justifies it, over the same physical port already delivered.
95th percentile or flat rate
A flat rate if you want a fixed amount. 95th percentile if the month's usage should set the price.
BGP with your ASN and prefixes
IPv4 and IPv6 sessions with your own autonomous system: you advertise your prefixes, with routing policy defined alongside our engineers.
Delivery in a PoP or colocation
The port is delivered at the PoP where your compute runs or in your own colocation rack, with the cross-connect coordinated by on-site smart-hands technicians.
Architecture
How it's built
Several upstreams
Commit
Burst
Carrier‑neutral network
Transit is not tied to a single upstream provider.
Uplink above the commit
Port capacity is sized above the contracted commit.
Addressing over the port
Advertise your own IPv4 and IPv6 space if you already hold it, or run transit over network-assigned addressing while you obtain yours from the regional registry.
How the session is operatedFilters before turn-up · Policy changes · Looking glass per PoP
Filters before turn‑up
Your ASN and prefixes are documented in the routing registries, and filters are agreed before the session goes live.
Policy changes
An announcement or filter change is raised as an operational request and carried out by the network team.
Looking glass per PoP
From each PoP's looking glass you check how your prefixes propagate.
Coverage
Present across the region
Transit is delivered at any PoP on the network, with egress toward the United States through Miami / Fort Lauderdale and to the rest of the world through the backbone's upstreams.
Turn-up time depends on the PoP and on whether the port runs over your own cross-connect or over last mile.
See the data centersPortfolio
Integrates with the rest of the platform
Pay for the traffic you sustain, not for your peaks
Tell us your commit and how you want to handle bursts. Get your custom quote.