bgpreport

Network · data from 2026-11-12

AS10972 NF-CANET2 - Memorial University, NF CAnet 2 gigaPOP

Registry name: NF-CANET2 - Memorial University, NF CAnet 2 gigaPOP, CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10972, 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.

198.165.161.0/24 Valid Other IRR onlyCANARIE 20 3%low visibility 18

AS-SET

AS10972 isn't in PeeringDB, where networks name their AS-SET.

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 44 are in fix.csv.

  • Route object: RIR1
  • Route object: not announced43
ChangePrefix or setDetailFull-table peers
Route object: RIR198.165.161.0/24Route object only in CANARIE. Add it in the RIR database for the space.20 of 673

Route objects not announced

Route objects with origin AS10972 whose prefix no peer sees AS10972 announce. Many are kept on purpose (backup routes, space announced only in some places).

24.138.160.0/24CANARIEInvalid: origin
24.138.161.0/24CANARIEInvalid: origin
24.138.162.0/24CANARIEInvalid: origin
24.138.163.0/24CANARIEInvalid: origin
24.138.164.0/24CANARIEInvalid: origin
24.222.32.0/25CANARIEInvalid: origin
24.222.46.0/28CANARIEInvalid: origin
96.30.187.0/24CANARIEInvalid: origin
96.30.188.0/24CANARIEInvalid: origin
96.30.189.0/24CANARIEInvalid: origin
96.30.190.0/24CANARIEInvalid: origin
96.30.191.0/24CANARIEInvalid: origin
172.28.250.16/28CANARIENo ROA
192.75.14.0/24CANARIENo ROA
192.75.24.0/24CANARIEInvalid: origin
192.75.25.0/24CANARIENo ROA
192.197.244.0/24CANARIENo ROA
192.219.31.0/24CANARIEInvalid: origin
198.165.21.40/29CANARIENo ROA
198.165.42.0/24CANARIENo ROA
198.165.58.0/24CANARIENo ROA
198.165.98.0/24CANARIENo ROA
198.165.99.0/24CANARIENo ROA
198.165.140.0/24CANARIENo ROA
198.165.141.0/24CANARIENo ROA
198.165.212.0/25CANARIENo ROA
208.85.80.0/22CANARIEInvalid: origin
209.128.14.128/27CANARIEInvalid: origin
209.128.30.160/27CANARIEInvalid: origin
209.128.38.136/29CANARIEInvalid: origin
209.205.240.0/20CANARIEInvalid: origin
209.205.240.0/24CANARIEInvalid: origin
209.205.241.0/24CANARIEInvalid: origin
209.205.242.0/23CANARIEInvalid: origin
209.205.244.0/22CANARIEInvalid: origin
209.205.248.0/22CANARIEInvalid: origin
209.205.248.0/24CANARIEInvalid: origin
209.205.249.0/24CANARIEInvalid: origin
209.205.250.0/24CANARIEInvalid: origin
209.205.251.0/24CANARIEInvalid: origin
209.205.252.0/23CANARIEInvalid: origin
2001:410:c000::/40CANARIENo ROA
2001:410:c000::/48CANARIENo ROA

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.