bgpreport

Network · data from 2026-11-12

AS17 PURDUE

Registry name: PURDUE - Purdue University, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17, 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.
128.210.132.0/23 Valid Nonecovered by 128.210.0.0/16 672 100% 67
128.210.250.0/24 Valid Nonecovered by 128.210.0.0/16 672 100% 67
2607:ac80:500::/48 Valid Nonecovered by 2607:ac80::/32 635 100% 70
128.10.0.0/16 Valid Other IRR onlyRADB 671 100% 69
128.46.0.0/16 Valid Other IRR onlyRADB 671 100% 69
128.210.0.0/16 Valid Other IRR onlyRADB 671 100% 69
128.211.0.0/16 Valid Other IRR onlyRADB 671 100% 69
192.5.40.0/24 Valid Other IRR onlyRADB 671 100% 69
192.12.63.0/24 Valid Other IRR onlyRADB 671 100% 69
192.31.0.0/24 Valid Other IRR onlyRADB 671 100% 69
2001:18e8:800::/44 Valid Other IRR onlyRADB 635 100% 70
2607:ac80::/32 Valid Other IRR onlyRADB 635 100% 70

AS-SET

AS17's PeeringDB record names no 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 28 are in fix.csv.

  • Route object: none3
  • Route object: RIR9
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
Route object: none128.210.132.0/23No route object for it. A route object for 128.210.0.0/16 with origin AS17 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17 in the RIR database for the space.672 of 673
Route object: none128.210.250.0/24No route object for it. A route object for 128.210.0.0/16 with origin AS17 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17 in the RIR database for the space.672 of 673
Route object: none2607:ac80:500::/48No route object for it. A route object for 2607:ac80::/32 with origin AS17 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17 in the RIR database for the space.635 of 636
Route object: RIR128.10.0.0/16Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR128.46.0.0/16Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR128.210.0.0/16Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR128.211.0.0/16Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR192.5.40.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR192.12.63.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR192.31.0.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2001:18e8:800::/44Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2607:ac80::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

69.51.160.0/19RADBValid
128.211.64.0/24RADBValid
128.211.96.0/24RADBValid
128.211.112.0/24RADBValid
128.211.120.0/24RADBValid
128.211.124.0/24RADBValid
128.211.126.0/24RADBValid
128.211.184.0/23RADBValid
128.211.186.0/23RADBValid
128.211.188.0/22RADBValid
128.211.192.0/18RADBValid
192.5.48.0/24RADBValid
192.5.91.0/24RADBValid
192.5.101.0/24RADBValid
192.5.102.0/24RADBValid
205.215.64.0/18RADBValid

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.