Joining NCIX
Eligibility requirements, peering options, and the onboarding process
Eligibility
NCIX operates an open peering policy. Networks meeting the following technical requirements are eligible to apply:
Required:
- Valid ASN allocated by ARIN, RIPE, APNIC, or equivalent RIR (private ASNs considered on request)
- Working BGP implementation capable of route filtering and community processing
- Documented routing policy accessible via PeeringDB or a public WHOIS database
- 24/7 NOC contact available for operational issues
- No history of sustained route leaks, prefix hijacking, or network abuse
Recommended:
- RPKI-signed route objects for your prefixes
- BGP Community support for traffic engineering
- BFD capability for fast failure detection
Peering Options
Public Peering
Shared switching fabric connection, suitable for most networks. Access to the NCIX route server (AS64512) for simplified multilateral peering. One BGP session to the route server establishes adjacency with all route server participants.
Specifications:
- Peering LAN: multiple isolated VLAN segments (IPv4 /24, IPv6 /64)
- Route Server: AS64512, RPKI-validated, IRR-filtered
- Port speeds: 1GbE, 10GbE, 100GbE, 400GbE
Costs:
- 10GbE port: CAD $500 setup + $600/month
- 100GbE port: CAD $1,000 setup + $1,800/month
- 400GbE port: CAD $2,000 setup + $4,500/month
- No traffic-based charges
Private Peering
Dedicated bilateral connection for high-volume network pairs requiring custom SLAs or dedicated bandwidth guarantees.
Specifications:
- Dedicated VLAN assignment
- Direct BGP session between peers
- Custom SLA terms available
Costs:
- Cross-connect fee (varies by facility)
- Monthly port fee as per public peering rate card
- SLA uplift negotiated per agreement
Route Server
The NCIX route server provides simplified multilateral peering. A single BGP session (IPv4 and IPv6) reaches all participating route server members.
Route server details:
- ASN: AS64512
- IPv4: 192.0.2.1
- IPv6: 2001:db8::1
- Software: BIRD 2.x
- RPKI validation: strict (invalid prefixes rejected)
- Community support: standard IXP community set
Co-Location
NCIX operates co-location services at its primary facility for members who wish to house equipment on-site.
- Cabinet rental from CAD $1,200/month (42U)
- Power metered at cost
- Carrier-diverse cross-connect options
- Remote hands available 24/7
Onboarding Process
The end-to-end onboarding process takes 6–8 weeks.
| Week | Phase | Description |
|---|---|---|
| 1 | Initial Inquiry | Submit peering request to peering@ncix.info |
| 2–3 | Technical Review | NCIX team reviews routing policy, prefix counts, and port requirements |
| 3–4 | Agreement | Sign NCIX Peering Agreement and Acceptable Use Policy |
| 4–6 | Physical Setup | Cross-connect provisioning and equipment installation |
| 6–8 | Testing & Go-Live | BGP session establishment, prefix verification, and traffic validation |
Required Information
When submitting your peering request, include:
- Organisation: Legal name, website, brief description of your network
- Network Details: ASN(s), IPv4 and IPv6 prefix list or aggregate, estimated traffic volume
- Technical Contact: Name, email address, phone number (24/7 NOC availability)
- Peering Type: Public / Private / Route Server (or combination)
- Port Speed Preference: 1GbE / 10GbE / 100GbE / 400GbE
- Facility Preference: NCIX-1 (primary) or NCIX-2 (secondary)
Frequently Asked Questions
Do I need a public ASN? Public internet peering requires a public, RIR-allocated ASN. Private ASNs (64512–65534, 4200000000–4294967294) can be accommodated for specific use cases — contact us to discuss.
Is peering charged by traffic volume? No. NCIX charges flat monthly port fees only. There are no traffic-based fees or burst charges.
Can I peer at both facilities? Yes. Multi-homed peering across NCIX-1 and NCIX-2 is encouraged for redundancy and is available at standard port rates per facility.
Do you support BGP Communities? Yes. NCIX supports a standard IXP community set for traffic engineering: prepend, no-export, no-advertise, and blackhole communities. Full community documentation is provided to members after onboarding.
What is your maintenance window policy? Scheduled maintenance is announced a minimum of 30 days in advance. Emergency maintenance affecting member sessions is communicated via NOC email immediately.
Ready to start? Submit your peering request to peering@ncix.info or contact our team.