bgpreport

Network · data from 2026-11-12

AS823 UWO-AS - University of Western Ontario

Registry name: UWO-AS - University of Western Ontario, CA · not in PeeringDB

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

Announced routes

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

2605:500::/32 No ROA Other origin only 635 100% 69
129.100.0.0/24 No ROA Other IRR onlyRADB 673 100% 70
129.100.0.0/16 No ROA Other IRR onlyCANARIE, RADB 671 100% 68
129.100.0.0/18 No ROA Other IRR onlyCANARIE, RADB 671 100% 69
129.100.64.0/20 No ROA Other IRR onlyCANARIE, RADB 671 100% 69
129.100.80.0/21 No ROA Other IRR onlyCANARIE, RADB 671 100% 69
129.100.96.0/19 No ROA Other IRR onlyCANARIE, RADB 671 100% 69
129.100.128.0/18 No ROA Other IRR onlyCANARIE, RADB 671 100% 69
129.100.224.0/19 No ROA Other IRR onlyCANARIE 671 100% 69
205.189.1.0/24 No ROA Other IRR onlyCANARIE 671 100% 69
129.100.192.0/23 No ROA Other IRR onlyCANARIE 111 16% 39
129.100.196.0/23 No ROA Other IRR onlyCANARIE 111 16% 39
129.100.198.0/23 No ROA Other IRR onlyCANARIE 111 16% 39
129.100.200.0/23 No ROA Other IRR onlyCANARIE 111 16% 39
129.100.202.0/23 No ROA Other IRR onlyCANARIE 111 16% 39
129.100.204.0/24 No ROA Other IRR onlyCANARIE 111 16% 39
129.100.206.0/23 No ROA Other IRR onlyCANARIE 111 16% 39
129.100.208.0/23 No ROA Other IRR onlyCANARIE 111 16% 39
129.100.210.0/23 No ROA Other IRR onlyCANARIE 111 16% 39
129.100.212.0/23 No ROA Other IRR onlyCANARIE 111 16% 39
129.100.214.0/23 No ROA Other IRR onlyCANARIE 111 16% 39
129.100.216.0/23 No ROA Other IRR onlyCANARIE 111 16% 39
129.100.219.0/24 No ROA Other IRR onlyCANARIE 111 16% 39
129.100.220.0/23 No ROA Other IRR onlyCANARIE 111 16% 39
129.100.222.0/23 No ROA Other IRR onlyCANARIE 111 16% 39

AS-SET

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

  • ROA: none25
  • Route object: none1
  • Route object: RIR24
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none2605:500::/32No ROA covers it. Add a ROA for AS823, maxLength 32.635 of 636
Route object: none2605:500::/32Route objects for it name AS819. Add a route object with origin AS823 in the RIR database for the space.635 of 636
ROA: none129.100.0.0/24No ROA covers it. Add a ROA for AS823, maxLength 24.673 of 673
Route object: RIR129.100.0.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none129.100.0.0/16No ROA covers it. Add a ROA for AS823, maxLength 16.671 of 673
Route object: RIR129.100.0.0/16Route object only in CANARIE, RADB. Add it in the RIR database for the space.671 of 673
ROA: none129.100.0.0/18No ROA covers it. Add a ROA for AS823, maxLength 18.671 of 673
Route object: RIR129.100.0.0/18Route object only in CANARIE, RADB. Add it in the RIR database for the space.671 of 673
ROA: none129.100.64.0/20No ROA covers it. Add a ROA for AS823, maxLength 20.671 of 673
Route object: RIR129.100.64.0/20Route object only in CANARIE, RADB. Add it in the RIR database for the space.671 of 673
ROA: none129.100.80.0/21No ROA covers it. Add a ROA for AS823, maxLength 21.671 of 673
Route object: RIR129.100.80.0/21Route object only in CANARIE, RADB. Add it in the RIR database for the space.671 of 673
ROA: none129.100.96.0/19No ROA covers it. Add a ROA for AS823, maxLength 19.671 of 673
Route object: RIR129.100.96.0/19Route object only in CANARIE, RADB. Add it in the RIR database for the space.671 of 673
ROA: none129.100.128.0/18No ROA covers it. Add a ROA for AS823, maxLength 18.671 of 673
Route object: RIR129.100.128.0/18Route object only in CANARIE, RADB. Add it in the RIR database for the space.671 of 673
ROA: none129.100.224.0/19No ROA covers it. Add a ROA for AS823, maxLength 19.671 of 673
Route object: RIR129.100.224.0/19Route object only in CANARIE. Add it in the RIR database for the space.671 of 673
ROA: none205.189.1.0/24No ROA covers it. Add a ROA for AS823, maxLength 24.671 of 673
Route object: RIR205.189.1.0/24Route object only in CANARIE. Add it in the RIR database for the space.671 of 673
ROA: none129.100.192.0/23No ROA covers it. Add a ROA for AS823, maxLength 23.111 of 673
Route object: RIR129.100.192.0/23Route object only in CANARIE. Add it in the RIR database for the space.111 of 673
ROA: none129.100.196.0/23No ROA covers it. Add a ROA for AS823, maxLength 23.111 of 673
Route object: RIR129.100.196.0/23Route object only in CANARIE. Add it in the RIR database for the space.111 of 673
ROA: none129.100.198.0/23No ROA covers it. Add a ROA for AS823, maxLength 23.111 of 673
Route object: RIR129.100.198.0/23Route object only in CANARIE. Add it in the RIR database for the space.111 of 673
ROA: none129.100.200.0/23No ROA covers it. Add a ROA for AS823, maxLength 23.111 of 673
Route object: RIR129.100.200.0/23Route object only in CANARIE. Add it in the RIR database for the space.111 of 673
ROA: none129.100.202.0/23No ROA covers it. Add a ROA for AS823, maxLength 23.111 of 673
Route object: RIR129.100.202.0/23Route object only in CANARIE. Add it in the RIR database for the space.111 of 673
ROA: none129.100.204.0/24No ROA covers it. Add a ROA for AS823, maxLength 24.111 of 673
Route object: RIR129.100.204.0/24Route object only in CANARIE. Add it in the RIR database for the space.111 of 673
ROA: none129.100.206.0/23No ROA covers it. Add a ROA for AS823, maxLength 23.111 of 673
Route object: RIR129.100.206.0/23Route object only in CANARIE. Add it in the RIR database for the space.111 of 673
ROA: none129.100.208.0/23No ROA covers it. Add a ROA for AS823, maxLength 23.111 of 673
Route object: RIR129.100.208.0/23Route object only in CANARIE. Add it in the RIR database for the space.111 of 673
ROA: none129.100.210.0/23No ROA covers it. Add a ROA for AS823, maxLength 23.111 of 673
Route object: RIR129.100.210.0/23Route object only in CANARIE. Add it in the RIR database for the space.111 of 673
ROA: none129.100.212.0/23No ROA covers it. Add a ROA for AS823, maxLength 23.111 of 673
Route object: RIR129.100.212.0/23Route object only in CANARIE. Add it in the RIR database for the space.111 of 673
ROA: none129.100.214.0/23No ROA covers it. Add a ROA for AS823, maxLength 23.111 of 673
Route object: RIR129.100.214.0/23Route object only in CANARIE. Add it in the RIR database for the space.111 of 673
ROA: none129.100.216.0/23No ROA covers it. Add a ROA for AS823, maxLength 23.111 of 673
Route object: RIR129.100.216.0/23Route object only in CANARIE. Add it in the RIR database for the space.111 of 673
ROA: none129.100.219.0/24No ROA covers it. Add a ROA for AS823, maxLength 24.111 of 673
Route object: RIR129.100.219.0/24Route object only in CANARIE. Add it in the RIR database for the space.111 of 673
ROA: none129.100.220.0/23No ROA covers it. Add a ROA for AS823, maxLength 23.111 of 673
Route object: RIR129.100.220.0/23Route object only in CANARIE. Add it in the RIR database for the space.111 of 673
ROA: none129.100.222.0/23No ROA covers it. Add a ROA for AS823, maxLength 23.111 of 673
Route object: RIR129.100.222.0/23Route object only in CANARIE. Add it in the RIR database for the space.111 of 673

Route objects not announced

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

129.100.0.0/17CANARIENo ROA
129.100.88.0/21RADBNo ROA
129.100.192.0/18RADBNo ROA
129.100.192.0/19CANARIENo ROA
129.100.194.0/23CANARIENo 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.