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

Peering Policy

The rules that keep the Peer1IX fabric fair, stable and secure for every member.

Last updated 21 October 2026

1. Eligibility

Any organisation holding a public Autonomous System Number (ASN) and publicly routable IP address space may connect to Peer1IX, subject to a signed service agreement and compliance with applicable Indian law.

2. Peering LAN rules

  • Only one MAC address is permitted per port (or per LAG) unless agreed otherwise.
  • Only IPv4 (0x0800), IPv6 (0x86DD) and ARP (0x0806) ethertypes are allowed on the peering LAN.
  • Members must not forward link-local protocols other than ARP and IPv6 ND — for example STP, CDP, LLDP, DHCP, router advertisements, OSPF or IS-IS.
  • Members may only use the IP addresses assigned to them by Peer1IX on the peering LAN.
  • Proxy ARP must be disabled.

3. BGP and routing

  • Members must announce only prefixes they are authorised to announce, with a valid route object in an IRR and, where possible, a ROA in RPKI.
  • Route servers drop RPKI-invalid routes, bogon prefixes, bogon ASNs in the AS path, and prefixes without matching IRR objects.
  • Members must not point default or static routes at another member without that member’s written consent.
  • Maximum-prefix limits apply to route server sessions.

4. Bilateral peering

Members are free to establish bilateral sessions with each other on mutually agreed terms. Peer1IX does not require members to peer with everyone.

5. Traffic and monitoring

Peer1IX monitors the fabric for compliance and stability using aggregated traffic statistics. Peer1IX does not inspect the content of member traffic.

6. Enforcement

Peer1IX may quarantine or disable a port that endangers the stability of the fabric. We will notify the member and work with them to restore service.

7. Contact

Infivate Networks Private Limited
2nd Floor, Minarch Tower, Plot No-4, Sector-44, Gurugram, Haryana 122003, India
Email: [email protected]