bgpreport

Network · data from 2026-11-12

AS6509 CANARIE Inc

Registry name: CANARIE-NTN - CANARIE Inc, CA · PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 routes 66.7% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 0 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS6509, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS6509, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
2001:410::/32 No ROA Other IRR onlyCANARIE 634 100% 69
199.212.24.0/24 Valid Other IRR onlyCANARIE, RADB 671 100% 68
2001:410:101::/48 Valid Other IRR onlyCANARIE 635 100% 69
2001:410:10a::/48 Valid Other IRR onlyCANARIE, RADB 635 100% 69
205.189.32.0/24 Valid Other IRR onlyCANARIE 20 3%low visibility 18
208.75.75.0/24 Valid Other IRR onlyRADB 20 3%low visibility 18

AS-SET

PeeringDB's irr_as_set for AS6509: CANARIE::AS6509:AS-CANARIE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS6509 isn't in the set, or no route object for AS6509 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS6509 in itNot covered
CANARIE::AS6509:AS-CANARIE CANARIE3 member sets in no database: AS21640:AS-GIGAPOP, AS376:AS-CLIENTS, AS394995:AS-GIGAPOP 187112,983 Yes 0

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 10 are in fix.csv.

  • ROA: none1
  • Route object: RIR6
  • AS-SET: missing member3
ChangePrefix or setDetailFull-table peers
ROA: none2001:410::/32No ROA covers it. Add a ROA for AS6509, maxLength 32.634 of 636
Route object: RIR2001:410::/32Route object only in CANARIE. Add it in the RIR database for the space.634 of 636
Route object: RIR199.212.24.0/24Route object only in CANARIE, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2001:410:101::/48Route object only in CANARIE. Add it in the RIR database for the space.635 of 636
Route object: RIR2001:410:10a::/48Route object only in CANARIE, RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR205.189.32.0/24Route object only in CANARIE. Add it in the RIR database for the space.20 of 673
Route object: RIR208.75.75.0/24Route object only in RADB. Add it in the RIR database for the space.20 of 673
AS-SET: missing memberCANARIE::AS6509:AS-CANARIEAS6509:AS-CANARIE (CANARIE) lists AS21640:AS-GIGAPOP; no IRR database read has it.
AS-SET: missing memberCANARIE::AS6509:AS-CANARIEAS6509:AS-CANARIE (CANARIE) lists AS376:AS-CLIENTS; no IRR database read has it.
AS-SET: missing memberCANARIE::AS6509:AS-CANARIEAS6509:AS-CANARIE (CANARIE) lists AS394995:AS-GIGAPOP; no IRR database read has it.

Route objects not announced

Every route object with origin AS6509 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.