Cloud Connect
off the public Internet
Join what you already run in a public cloud to your regional infrastructure.
- AWS
- Azure
- Oracle
Your PoP
The quote is scoped from the target cloud, port speed and redundancy.
19
PoPs
13
Countries
24/7
Critical incidents
up to99.9%
Network SLA
Real‑world use cases
Leave the application tier where it already runs and bring the data down to an in-country PoP.
Regulated data stays in a Tier III facility in-country, and the cloud's managed services query it from there.
Move datasets, copies and results between the cloud and your infrastructure, on a port sized to your needs.
Capabilities
Service scope
AWS, Azure, Google and Oracle
Each destination attaches as a logical interface on the same port, with no new fiber or hardware on your side.
Ports from 100 Mbps to 10 Gbps
Size the link to the real traffic between the cloud and your infrastructure, and change speed without redesigning the interconnection or renumbering routing.
Dual circuit for redundancy
The redundant design lights two circuits over diverse paths, so losing a single port never leaves your cloud workload cut off from the rest of your estate.
BGP with your own prefixes
BGP sessions over the link exchange IPv4 and IPv6 routes between your cloud virtual network and the IPXON network, with prefix filters agreed at turn-up.
Architecture
How it's built
Physically diverse paths
With dual circuits, BGP sessions converge on the link that stays up.
Turn‑up on both ends
The network team coordinates provisioning on both ends.
It validates route exchange against your virtual network and hands the link over in production.
Coverage
Present across the region
Cloud Connect originates at any PoP on the network and reaches the public clouds through the interconnection points where IPXON is present, including Miami / Fort Lauderdale as the US gateway.
Turn-up time depends on the origin PoP and the destination cloud.
See the data centersPortfolio