About this IXP
Data last updated December 2025
Capacity at this IXP
Cumulative port speeds of all IXP members. This shows the potential maximum traffic that can be exchanged at this IXP at one time.
Membership and capacity
The size and strength of an IXP is determined by a combination of how many members it has, and the total capacity. Larger networks tend to bring more capacity, which can benefit all members.
Data for CANIX Montreal as shown in PeeringDB in December 2025
Members of this IXP
ASNs (autonomous system numbers) are listed in PeeringDB
In the last 12 months
- ASNs left8
- New ASNs joined5
Participates in the MANRS IXP program
Yes
IXPs that join this voluntary program apply a framework of enhanced routing security in peering. It signals an extra commitment to responsible Internet stewardship.
Source: MANRS
RIPE Atlas anchor
No
Organizations that run IXPs can host anchors to measure Internet connectivity and traffic. An anchor is a large capacity probe often used by IXPs.
Source: RIPEStat
Member information
Last sync from PeeringDB: December 2025
Countries of registration
A summary of member registrations by country. An IXP with a mixture of international and near-neighbor members can indicate that an IXP is influential, or acts as a hub within its region or sub-region.
View all countries of registration
Types of network at this IXP
The mix of members is an indication of a strength or focus of an IXP.
View all network types
Members peering at the route server
58 / 76
The route server is a central hub that makes it easier for all networks to peer without having to create individual agreements with other members.
Members using RPKI
59 / 76
members at this IXP use Resource Public Key Infrastructure (RPKI), a security measure that helps ensure traffic is routed correctly. A member is counted as using RPKI if they have at least one valid ROA.
Peering policies of IXP members
Members of an IXP can choose how they peer with others. The Internet Society encourages open policies where possible.
Member list for CANIX Montreal
This list uses the data available in PeeringDB, which is based on self-reported data, and was last updated in Pulse December 2025
| Name | AS Number | Peering policy | RPKI Enabled |
|---|---|---|---|
Zscaler AS22616
|
22616 | Open | Yes |