Internet exchange & carrier connectivity
A network reaches the Internet through transit, through peering, or both. Transit means paying an upstream provider to carry traffic to everywhere; peering means exchanging traffic directly with another network, usually at an Internet exchange point (IXP) or over a private cross-connect inside a data center. Our team designs which mix fits a business: how many upstreams, which exchanges, and where the physical handoffs happen.
What we do
- Transit versus peering analysis and upstream selection
- IXP port, route-server and remote-peering setups
- PeeringDB records and peering policy preparation
- Cross-connect and meet-me-room coordination in colocation facilities
- Wavelength and dark-fiber options between sites
- Software-defined interconnection to cloud on-ramps
- MANRS-style filtering, anti-spoofing and RPKI validation
- Capacity planning and failover tests across carriers
At an exchange, a route server (RFC 7947) lets one BGP session reach many peers instead of configuring a session with each. PeeringDB, the community directory of networks and facilities, is where we check who is present where and what their policies are. Routing hygiene follows the MANRS actions: filtering, anti-spoofing, coordination and validated routing information such as RPKI.
For capacity between sites and clouds we work with carrier services: cross-connects, wavelengths, dark fiber, and software-defined interconnection such as Megaport and Equinix Fabric to reach cloud on-ramps. This work sits under Managed IT and Cloud Management, and pairs with our BGP and DDoS practices.
Leading platforms we work with
- PeeringDB
- MANRS
- Megaport
- AMS-IX
- DE-CIX
- LINX
- Equinix Fabric
Platforms and practices
- Internet exchange points (IXPs)
- BGP route servers
- Transit and peering strategy
- Cross-connects
- Wavelengths & dark fiber
- Cloud on-ramps
- Remote peering
- Routing security (RPKI, IRR filtering)
References
- RFC 7947: Internet Exchange BGP Route Server
- PeeringDB
- MANRS: Mutually Agreed Norms for Routing Security
- Megaport (ports, virtual cross connects, cloud on-ramps)
- AMS-IX (Amsterdam Internet exchange: peering and remote peering)
- RFC 4271: A Border Gateway Protocol 4 (BGP-4)
- DE-CIX
- LINX
Sources last checked .
Product names are trademarks of their owners and are listed to describe our experience; they do not imply endorsement or partnership.
How we use Internet exchange & carrier connectivity for clients
Managed IT Services
We run your IT day to day so it stays secure: help desk, devices, Microsoft 365, Exchange, Active Directory, backups, networks and monitoring.
Learn moreCloud Management
Cloud cost review and management, without compromising on quality or security.
Learn moreCybersecurity
We find out whether everything you run is safe from attackers, then we fix it.
Learn moreWhere this matters most
Frequently asked questions
Direct answers to the questions we hear most. Something else on your mind?
Send us a messageDoes a business need transit, peering or both?
Every network needs a way to reach everywhere, which is usually transit from one or more upstream providers. Peering adds direct exchange of traffic with other networks at an Internet exchange or over a private cross-connect. We compare the two for your traffic and decide the number of upstreams, the exchanges and the physical handoffs.
What is a route server and why do exchanges offer one?
A route server (RFC 7947) lets one BGP session at an exchange reach many peers, so you do not configure a separate session with each network. It saves effort when you join an exchange. You can still add a direct session with a network when you want specific terms.
What do you use PeeringDB for?
PeeringDB is a free, community-maintained directory of networks and interconnection facilities. We check who is present at which exchange or facility and what their peering policies are before recommending a location. We also help prepare your own record, so other networks can find and contact you.
What does MANRS ask a network operator to do?
MANRS is a global routing-security initiative. Its actions cover filtering, anti-spoofing, coordination and validated routing information such as RPKI. We apply the same hygiene when we set up peering and transit sessions, so a mistake on your side does not leak or hijack routes.
What is the difference between a cross-connect, a wavelength and a cloud on-ramp?
A cross-connect is a physical link between two networks inside a data center. A wavelength or dark fiber carries capacity between sites. A cloud on-ramp is a private path into a cloud provider, which services such as Megaport and Equinix Fabric can set up as software-defined interconnection. We choose by capacity, distance and cost.
Are you a partner of Megaport, AMS-IX or the other names listed?
No. Those names show tools and services our team has worked with. They are not a ranking, an endorsement or a partnership. We choose carriers, exchanges and interconnection providers by what fits your sites, traffic and budget, and we say plainly when a different provider is a better fit.