One cross connect into the DCConnect network gives you remote peering ports at SGIX, EIE, idEX, BBIX, MYIX, JKTIX, HKIX, and AMSIX — no overseas colocation, no extra circuits to manage, one contract for every exchange.
Internet exchanges deliver the cheapest, lowest-latency traffic exchange available — but only if you have a port inside that facility. Building out colocation in every market you want to peer in is slow and expensive.
DCConnect’s Remote Peering service extends a single physical port, in a market you already operate from, out to eight major exchanges across Southeast Asia, North Asia, and Europe — all delivered over our private backbone, all billed on one invoice.
What you get
Every remote peering port from DCConnect includes these capabilities, regardless of which exchange you join.
Single Port, Multi-IX
Order once and fan out to as many of the 8 supported exchanges as your peering policy requires, without new circuits per IX.
Private Backbone Transport
Traffic between your port and each IX peering LAN rides DCConnect’s own network — not the public internet — for consistent low latency.
Fast Activation
Most new exchange connections activate in under 10 business days once route-server peering and LOAs are confirmed.
Consolidated Billing
One invoice covering port and per-IX usage, replacing the multiple local contracts you’d otherwise need to manage.
How it works
DCConnect handles the provisioning across both ends. You just plug in at each site and go.
Choose your exchanges
Pick from SGIX, EIE, idEX, BBIX, MYIX, JKTIX, HKIX, and AMSIX based on where your traffic — and your peers — actually are.
Provision the port
We provision a single remote peering port sized to your aggregate traffic across all chosen exchanges, plus the LOA paperwork each IX requires.
Establish BGP sessions
Set up BGP sessions to each exchange’s route server (or bilateral peers), confirm prefixes are visible, and you’re exchanging traffic.
Real peering LANs, real locations — reachable today over your existing remote peering connection.
SGIX
Singapore
Peering LAN
IPv4/IPv6
Port speed
Route server
SGIX
Singapore
Peering LAN
IPv4/IPv6
Port speed
Route server
SGIX
Singapore
Peering LAN
IPv4/IPv6
Port speed
Route server
SGIX
Singapore
Peering LAN
IPv4/IPv6
Port speed
Route server
SGIX
Singapore
Peering LAN
IPv4/IPv6
Port speed
Route server
SGIX
Singapore
Peering LAN
IPv4/IPv6
Port speed
Route server
Technical specifications
What’s actually behind a DCConnect remote peering port.
1 – 10 Gbps
One physical port carries traffic for all exchanges you’ve joined, sized to your combined peering traffic across all 8 IXs.
Coverage
7 Countries
Southeast Asia, North Asia, and Europe peering LANs are all reachable from a single backbone connection point.
Routing
BGP via Route Server
Peer via each exchange’s route server for broad reach, or set up bilateral BGP sessions with specific peers as needed.
Activation
<10 Business Days
Typical timeline from signed LOA to live BGP sessions, assuming an existing remote peering port is already in place.
Transport
Private Backbone
Traffic from your port to each peering LAN is carried entirely on DCConnect-owned and leased infrastructure.
Billing
Consolidated
Port and usage fees across every exchange you join appear on a single recurring invoice — no per-country billing relationships.
Who uses this
If your traffic crosses borders, remote peering usually pays for itself quickly.
Content & CDN Networks
Peer directly with eyeball networks across Southeast Asia and beyond, cutting transit costs and improving delivery latency for video, gaming, and web traffic.
ISPs & Carriers
Expand your peering footprint into new markets without standing up local infrastructure — ideal for testing demand before committing to physical presence.
Cloud & SaaS Providers
Improve performance for regional customers by peering closer to their networks, reducing reliance on long-haul transit for everyday application traffic.
Enterprises with Global Footprint
Multinational organizations consolidate peering relationships across Asia and Europe into one provider relationship instead of negotiating local presence market by market.
Frequently asked
Still deciding which exchanges to join? Our peering team can help you map traffic to the right IXs.
Can I join all 8 exchanges from one port?
Yes — a single remote peering port can fan out to as many of the 8 supported exchanges as you need, sized to your combined traffic across all of them.
Do I need a physical presence in each country?
No. That’s the entire point of remote peering — DCConnect’s backbone extends your port to each exchange’s peering LAN without requiring colocation in that market.
How fast can I add a new exchange?
If you already have an active remote peering port, adding a new exchange typically takes under 10 business days, primarily limited by each IX’s own LOA and route-server onboarding process.
Do I peer via route server or bilaterally?
Both are supported. Most customers start with each exchange’s multilateral route server for broad reach, then add bilateral BGP sessions with specific high-value peers as needed.
What port speeds are available?
Remote peering ports range from 1 Gbps to 10 Gbps. We size the port to your aggregate peering traffic across all exchanges you’ve joined, with room to grow.
Is billing separate for each exchange?
No — all port and usage charges across every exchange you join are consolidated onto a single recurring DCConnect invoice.
Tell us which markets your traffic touches, and we’ll recommend which exchanges to join first — with a proposal usually within 24 hours.
