asn.dev

Internet exchange

Atlantic IXP- MonctonIX

active Moncton, Canada YQM

Recorded members 25 addresses on file
Connected ports 11 across all participants
Peak traffic Not reported no figure on file
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
Moncton, Canada
Region
North America
Airport code
YQM
Status
Active

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
206.71.137.0/24IPv4Active11
2001:504:37:30::/64IPv6Active10

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

25 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
AS6939Hurricane Electric LLC2001:504:37:30::70Open
AS6939Hurricane Electric LLC206.71.137.7he-peer.monctonix.caOpen
AS42WoodyNet, Inc.206.71.137.4Open
AS42WoodyNet, Inc.2001:504:37:30::40
AS3856Packet Clearing House, Inc.2001:504:37:30::50
AS3856Packet Clearing House, Inc.206.71.137.5Open
AS55195CIRA Canadian Internet Registration Authority Autorit Canadienne pour les enregistrements Internet206.71.137.9
AS22995Xplore Inc.2001:504:37:30::130Open
AS22995Xplore Inc.206.71.137.13Open
AS5645TekSavvy Solutions, Inc.2001:504:37:30::80Selective
AS5645TekSavvy Solutions, Inc.206.71.137.8teksavvy-peer.monctonix.caSelective
AS26523Province of New Brunswick2001:504:37:30::120Selective
AS26523Province of New Brunswick206.71.137.12Selective
AS3367Xplore Inc.206.71.137.6F6-peer.monctonix.caOpen
AS3367Xplore Inc.2001:504:37:30::60Open
AS21659Alt Telecom2001:504:37:30::100Open
AS21659Alt Telecom206.71.137.11altTelecom2-peer.monctonix.caOpen
AS21659Alt Telecom2001:504:37:30::110Open
AS21659Alt Telecom206.71.137.10altTelecom-peer.monctonix.caOpen
AS63356Tinuum Networks Inc2001:504:37:30::140Open
AS63356Tinuum Networks Inc206.71.137.14Open
AS53649ATLANTIC IXPS INC.2001:504:37:30::30Open
AS53649ATLANTIC IXPS INC.2001:504:37:30::20Open
AS53649ATLANTIC IXPS INC.206.71.137.3rs2-peer.monctonix.caOpen
AS53649ATLANTIC IXPS INC.206.71.137.2rs1-peer.monctonix.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.