asn.dev

Internet exchange

CANIX Internet Exchange - Toronto

active Toronto, Canada

Recorded members 22 addresses on file
Connected ports 9 across all participants
Peak traffic 92.0 Mbps peak, as recorded
Peering LANs 2 shared subnets

Overview

What this is

recorded

An internet exchange is shared switching where networks interconnect directly instead of paying a transit provider to carry traffic between them. Members take a port on the fabric and an address on the peering LANs below, then agree bilaterally (or through a route server) about which routes to exchange. Turning up at one is a deliberate choice about how a network wants to be reached, which is why exchange presence says something a routing table cannot.

Location
Toronto, Canada
Region
North America
Status
Active
PCH record updated
2026-08-08

Everything on this page is what Packet Clearing House had recorded when the directory was collected, not a live view of the fabric. Member counts in particular lag reality, and around 45% of the exchanges in this dataset publish no participant list at all.

Fabric

Peering LANs

2 on file

The shared subnets members take an address on. A network with an interface in one of these blocks is at this exchange by definition, which is what makes exchange presence a recorded fact rather than an inference. Most exchanges run one IPv4 and one IPv6 LAN; extra blocks are usually growth or a migration.

PrefixFamilyStatusParticipants
149.112.134.0/23IPv4Active9
2602:f777:400::/64IPv6Active9

Deprecated and retired blocks are listed rather than dropped. A decommissioned LAN still records how this fabric used to be reached, and filtering it would quietly rewrite the exchange's history.

Participants

Member networks

22 shown

Every network PCH records with an address on one of the peering LANs above, ordered as the source ranks them: the most-connected participants first. One row per recorded address, so a network running dual-stack appears once for its IPv4 interface and once for its IPv6 one.

ASNetworkAddressrDNSPolicy
AS16276OVH SAS2602:f777:400::134:11Open
AS16276OVH SAS149.112.134.11OVH.YYZ.Canix.caOpen
AS60068Datacamp Limited149.112.134.6cdn77.yyz.canix.caOpen
AS60068Datacamp Limited2602:f777:400::134:6Open
AS112DNS-OARC149.112.135.252Open
AS112DNS-OARC2602:f777:400::135:252Open
AS33185Hive Data Center Inc.149.112.134.5hive.yyz.canix.caOpen
AS33185Hive Data Center Inc.2602:f777:400::134:5Open
AS19523FlexNetworks2602:f777:400::134:8Open
AS19523FlexNetworks149.112.134.8flex.yyz.canix.caOpen
AS400202Municipality of the County of Pictou2602:f777:400::134:9Open
AS400202Municipality of the County of Pictou149.112.134.9mopc.yyz.canix.caOpen
AS25858CANIX SOLN & SVC149.112.135.253Mandatory
AS25858CANIX SOLN & SVC2602:f777:400::135:253Mandatory
AS25858CANIX SOLN & SVC149.112.135.254Mandatory
AS25858CANIX SOLN & SVC2602:f777:400::135:254Mandatory
AS25870CANIX SOLN & SVC149.112.135.249Open
AS25870CANIX SOLN & SVC2602:f777:400::135:248Open
AS25870CANIX SOLN & SVC2602:f777:400::135:249Open
AS25870CANIX SOLN & SVC149.112.135.248Open
AS212232Port 179 LTD2602:f777:400::134:7Open
AS212232Port 179 LTD149.112.134.7bgptools.yyz.canix.caOpen

Peering policy is what the network declared to PCH, not something anyone verified, and an open policy is an invitation rather than a commitment. Absence of a network here means PCH has no record of it at this exchange, not that it is not present.

Provenance

Where this comes from

Exchange records come from the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member addresses, licensed CC BY-NC-SA 3.0.

This is a snapshot, not a live view. Members join and leave continuously, and the figures above are what PCH had on file on the collection date. PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.