Peer1IX
Internet Exchange
Services

Interconnection

Internet ExchangeMicro PoPsEdge Data Centers

Network Services

Data Center to Data CenterVirtual Connectivity HubData Center to CloudCloud to CloudPeer1ix Cloud RouterPeer1ix Virtual EdgeNAT GatewayPeer1ix PortVirtual Cross Connect

Security Services

DDoS ProtectionPeer1ix FWaaSIPsec Tunnel

Cloud Interconnect

Cloudflare Network Interconnect
Locations
Network toolsAll-in-One Network ReportBGP Looking GlassRPKI ValidatorBGP Security & Hijack CheckIP WHOISAS WHOISBGP Route ExplorerASN InsightsBGP Hijacks & Route LeaksInternet Outage TrackerCountry Internet InsightsTop Domains RankingDNS LookupSubnet CalculatorWhat Is My IP
BlogAboutContact Get connected

How to Join an Internet Exchange: A Step-by-Step Checklist for ISPs

· 2 min read · Peer1IX Team

How to Join an Internet Exchange: A Step-by-Step Checklist for ISPs

From getting an ASN to your first route, here is the practical checklist regional ISPs can follow to start peering at an internet exchange.

Before you start

Joining an exchange is less complicated than many operators expect. If you already run BGP with an upstream, you have most of the skills you need. The main work is preparation: making sure your routing information is clean, and deciding where and how you will connect.

1. Get your own ASN and address space

To peer, your network needs a public Autonomous System Number and IP prefixes it is entitled to announce. In India these are obtained through APNIC directly or via IRINN, the national registry. If you currently use addresses from your upstream, ask whether you can announce them with your own ASN — but owning your space is far more flexible.

2. Register route objects

Most exchanges and large networks filter routes using Internet Routing Registry data. Create a route (and route6) object for each prefix, with your ASN as origin, in the registry used by your RIR. Also create an as-set listing your ASN and your customers’ ASNs, so peers can build filters for everything you announce.

3. Publish ROAs in RPKI

Route Origin Authorisations tell the world which ASN may originate your prefixes. Exchanges like Peer1IX drop RPKI-invalid routes at the route servers, and a growing share of networks do the same. Create ROAs in your RIR portal and check them with an RPKI validator before you go live.

4. Choose your port

Start from your traffic profile. A regional ISP with a few gigabits of peak traffic to content networks usually begins with a 10G port. Plan for growth — moving to a bigger port later is straightforward, but frequent upgrades are disruptive.

5. Arrange the cross-connect

Your router needs a fibre path to the exchange switch. If you are colocated in the same facility, this is an in-building cross-connect. If not, you will need transport into the facility — Peer1IX can advise on options in each city.

6. Configure and test BGP

  • Configure the peering LAN addresses assigned to you.
  • Bring up sessions with both route servers.
  • Apply inbound filters and sensible max-prefix limits.
  • Verify what you announce and receive using the looking glass.

7. Add bilateral peers

Contact your largest traffic destinations on the exchange and set up direct sessions. These give you more control and an extra layer of resilience.

8. Monitor and iterate

Port graphs show you how much traffic has moved off transit. Use them to plan capacity and to identify where private VLANs would help.

Ready to begin? Register your interest and our team will walk you through availability in your city.

join IXASNpeering checklistISP