Remote Peering Services
Reach AMS-IX, LINX, LONAP and FryIX over a single port with Exascale OnePort. Bring remote peering and optional IP Transit together through one connection to your network.
More peering options. One connection.
Remote peering with Exascale OnePort
Exascale OnePort connects your network to AMS-IX, LINX, LONAP and FryIX over a single port. You can also include IP Transit where required, bringing exchange access and wider Internet reach into the same service design.
Remote peering extends your reach to an Internet exchange without requiring you to install equipment at every exchange location. It gives network operators a practical way to build peering relationships with participating content, hosting and access networks.
Connect through a suitable data centre handoff or discuss Layer 2 connectivity to your premises. We will review your location, exchange choices and capacity requirements, then agree a delivery arrangement that fits your network.
Four exchanges. Optional transit. One port.
Access all four exchanges through Exascale OnePort. Choose the exchanges that fit your traffic destinations and peering strategy, with the required services agreed as part of your order.
Add Exascale IP Transit to OnePort for Internet reach beyond the routes available through your peering relationships. Peering and transit serve different purposes and can complement each other.
Consolidate multiple exchange connections onto a single port at your network edge. Plan total capacity across your selected services, leaving headroom for growth and changing traffic patterns.
Build your peering policy around the networks you want to reach. Review route-server participation and bilateral BGP sessions, subject to the exchange rules and each network’s peering policy.
Extend your exchange reach through Exascale instead of deploying your own equipment at every exchange. Discuss delivery from your data centre or a suitable Layer 2 connection to your premises.
Agree the handoff, service separation, bandwidth and routing requirements before delivery. Where resilience is essential, discuss additional independent connectivity alongside the single-port design.
Build the routes your network needs
Peering, transit and transport working together
Start with your traffic: where it goes, which networks you exchange it with, and how those patterns change at busy times. This helps identify the exchanges and peers that could provide useful alternative paths. Remote peering can improve routing options, but performance depends on the actual end-to-end path.
Peering provides access to routes shared by your peers; it does not provide every Internet destination. Add Exascale IP Transit to OnePort when you need wider reach, and decide how your routing policy should prefer peering and transit paths.
If your router is outside an available handoff location, discuss leased line and Layer 2 connectivity. For equipment hosted with Exascale, explore our data centre locations, including Wolverhampton colocation.
A single port simplifies delivery but remains a shared dependency. Tell us your availability targets so we can assess whether additional ports, diverse paths or separate equipment are needed.
Illustrative rack photograph: Brett Sayles / Pexels.
Remote peering and OnePort FAQs
Remote peering connects your network to an Internet exchange through a transport provider, rather than requiring your own equipment at that exchange location. Once connected, you can exchange routes with participating networks through agreed BGP peering relationships. The routes you receive depend on those relationships and policies.
Exascale OnePort can provide connections to AMS-IX, LINX, LONAP and FryIX over a single port. Tell us which exchanges you need, your handoff location and expected traffic. We will confirm the service configuration, delivery requirements and any applicable exchange arrangements as part of your proposal.
Yes. Exascale OnePort can include IP Transit if required, alongside access to the selected exchanges. Peering provides routes shared by your peers, while IP Transit provides wider Internet reach. Your routing policy determines how those services are used, and port capacity should be sized for the combined traffic.
Operating your own peering network normally requires a public autonomous system number (ASN), suitable IP address space and a router capable of BGP. Exchange admission rules, routing records and prefix authorisation must also be considered. Share your existing setup with Exascale so the prerequisites and responsibilities can be checked before ordering.
A route server helps participating networks exchange routing information without configuring a separate BGP session with every participant. Bilateral peering uses a BGP session directly between two networks. Availability and acceptance depend on the exchange and each network’s policy; an exchange connection does not automatically give you access to every member’s routes.
A single port brings services together but remains a shared dependency. Multiple exchanges on that port do not remove the risk of a failure affecting the common handoff or access path. If your availability requirements call for redundancy, discuss additional ports, independent paths and equipment, along with your BGP failover policy.
Let’s plan your OnePort connection
Tell us your ASN, handoff location, preferred exchanges and expected traffic levels. Let us know whether you need IP Transit and what resilience your network requires.
We can review capacity, delivery and routing requirements together and prepare a proposal for your Exascale OnePort service.
