bgpreport

Network · data from 2026-11-12

AS31782 WLUAS - Wilfrid Laurier University

Registry name: WLUAS - Wilfrid Laurier University, CA · not in PeeringDB

10IPv4 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
0Low visibility seen by under 10% of full-table peers
11Route objects not announced registered with origin AS31782, seen from no peer

Announced routes

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

192.54.242.0/24 Valid Other IRR onlyCANARIE, RADB 673 100% 68
192.219.240.0/24 Valid Other IRR onlyCANARIE, RADB 673 100% 68
205.189.16.0/20 Valid Other IRR onlyCANARIE, RADB 673 100% 68
205.189.18.0/24 Valid Other IRR onlyCANARIE 673 100% 68
205.189.24.0/24 Valid Other IRR onlyCANARIE 673 100% 68
216.249.48.0/20 Valid Other IRR onlyCANARIE, RADB 673 100% 68
216.249.52.0/24 Valid Other IRR onlyCANARIE 673 100% 68
216.249.53.0/24 Valid Other IRR onlyCANARIE 673 100% 68
216.249.55.0/24 Valid Other IRR onlyCANARIE 673 100% 68
192.219.236.0/22 Valid RIR databaseARIN, CANARIE, RADB 673 100% 68

AS-SET

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

  • Route object: RIR9
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
Route object: RIR192.54.242.0/24Route object only in CANARIE, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR192.219.240.0/24Route object only in CANARIE, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR205.189.16.0/20Route object only in CANARIE, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR205.189.18.0/24Route object only in CANARIE. Add it in the RIR database for the space.673 of 673
Route object: RIR205.189.24.0/24Route object only in CANARIE. Add it in the RIR database for the space.673 of 673
Route object: RIR216.249.48.0/20Route object only in CANARIE, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR216.249.52.0/24Route object only in CANARIE. Add it in the RIR database for the space.673 of 673
Route object: RIR216.249.53.0/24Route object only in CANARIE. Add it in the RIR database for the space.673 of 673
Route object: RIR216.249.55.0/24Route object only in CANARIE. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

205.189.16.0/23CANARIE, RADBValid
205.189.19.0/24CANARIE, RADBValid
205.189.20.0/22CANARIE, RADBValid
205.189.24.0/21CANARIE, RADBValid
205.189.24.0/23CANARIEValid
216.249.48.0/22CANARIEValid
216.249.54.0/23CANARIEValid
216.249.56.0/21CANARIEValid
216.249.58.0/23CANARIE, RADBValid
216.249.59.0/24CANARIE, RADBValid
216.249.60.0/22CANARIE, RADBValid

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.