bgpreport

Exchanges · data from 2026-11-19

CANIX Winnipeg

Winnipeg, CA · IX Report finds no sign this exchange is running · members from IX Report (2026-11-19)

4Members 2 originate routes
17Their routes 64.7% RPKI valid · 64.7% with a route object
4RPKI invalid from 1 members
2No ROA 6 with no route object for their origin
0AS-SET includes own ASN 0 missing it · 0 not found · 1 none
3Route-server members 6 of their 17 routes left out by an RPKI + IRR filter

Route servers: RPKI + IRR filtering

For each member on the route servers: of the routes it originates, how many a route server would leave out if it dropped RPKI-invalid routes and filtered on the IRR the way IXP route servers commonly build their prefix lists: the member's AS-SETs from PeeringDB (with none, its own AS number), expanded as bgpq4 does against whois.radb.net, with more-specifics of a route object accepted down to /24 and /48 (bgpq4 -A -R 24 / -R 48). 4 routes are RPKI invalid and 6 fail the IRR filter. Only each member's own routes are counted: the collectors show a route's origin, not which network it came through, so customers' routes aren't in these numbers. Route objects only in LEVEL3 or IDNIC (no public dump) count as missing.

AS112DNS-OARC-112 AS112 8 4 4 4 50%
AS21774The Exchange Global Server Center AS21774 no AS-SET in PeeringDB 9 0 2 2 22%

0 other route-server members would have every route they originate accepted; 1 originate no routes the collectors see.

Members

Every member on IX Report's lists for CANIX Winnipeg, with the routes it originates. Also as members.csv.

AS21774The Exchange Global Server Center Yes 99 v4 · 0 v6 78% 0 78% none in PeeringDB
AS112DNS-OARC-112 Yes 86 v4 · 2 v6 50% 4 50% AS number only
AS13595CANIX Winnipeg Route Servers No none seen
AS403134CANIX Winnipeg Services Yes none seen