Remote Peering
Exchange traffic with third-party networks at regional and global IXPs without deploying hardware there.
19
PoPs
13
Countries
Per PoP
Turn-up time
24/7
Critical incidents
up to99.9%
Network SLA
What it's for
Real‑world use cases
- 01
Gaming or CDN with regional traffic
Direct delivery to access networks
Traffic toward an ISP's subscribers leaves through the exchange instead of transit, crossing fewer intermediate networks and not depending on a third party's routing.
- 02
Regional ISP with a single upstream
Peering to offload transit
Shift the traffic you already exchange with networks on the IXP to peering and keep transit for the rest of the Internet, with per-prefix control in your BGP policy.
- 03
OTT with audiences in Brazil and Mexico
Presence at several IXPs at once
Light ports at PTT São Paulo and NAP México under one contractual relationship, from the PoP where you already sit, without opening physical presence in each country.
Capabilities
Service scope
IXPs across LATAM and Europe
Ports to NAP Colombia, PTT São Paulo, CABASE Buenos Aires, IXP Chile and NAP México inside the region, plus DE-CIX and LINX beyond it.
Ports from 100 Mbps to 10 Gbps
Start at the port your exchanged volume justifies and step it up as peering grows, without changing the relationship already established at the exchange.
With your ASN or over ours
The model is defined when the service is shaped: peer with your own autonomous system and prefixes, or ride the network's if you don't have one yet.
Route server and bilateral sessions
Reach the exchange's route server for open peering and negotiate bilateral sessions with the networks that require them, all over the same port.
No physical presence at the IXP
You need no rack, no equipment and no cross-connect in the exchange's city: the port is delivered remotely over the network from the PoP where you already operate.
IPv4 and IPv6 on one port
Both address families are announced over the same logical port, with sessions split per protocol and prefix filters defined together with your network team.
Architecture
How it's built
Dedicated backhaul to the exchange
Between your PoP and the IXP, traffic rides network capacity rather than the Internet: the peering port behaves as if you were connected at the exchange itself.
A dedicated VLAN per exchange
Each IXP is delivered on its own 802.1Q VLAN over your port, so adding a second exchange neither mixes domains nor forces you to reconfigure the first.
Transport over the multi-region fabric
The remote port is built on the same fabric as every other network service.
Diagnostics with looking glass
Check session state and advertised routes from each PoP's looking glass and from the PRESENCE® platform. When needed, the network team steps in on the session. 24/7/365 technical support for critical incidents. Operational requests.
Coverage
Present across the region
The remote port originates at any PoP on the network, including Miami / Fort Lauderdale as the US gateway, and reaches the regional exchanges plus DE-CIX and LINX. Turn-up time depends on the origin PoP and on the IXP's own lead times.
19
PoPs
13
Countries
Portfolio
Integrates with the rest of the platform
Private connectivity to international IXPs.
Remote peering to global internet exchange points.