bgpreport

Network · data from 2026-11-12

AS397501 PURDUE-RESNET - Purdue University

Registry name: PURDUE-RESNET - Purdue University, US · not in PeeringDB

10IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
0Route objects not announced registered with origin AS397501, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS397501, 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.211.64.0/24 Valid Other IRR onlyRADB 672 100% 67
128.211.96.0/24 Valid Other IRR onlyRADB 672 100% 67
128.211.112.0/24 Valid Other IRR onlyRADB 672 100% 67
128.211.120.0/24 Valid Other IRR onlyRADB 672 100% 67
128.211.124.0/24 Valid Other IRR onlyRADB 672 100% 67
128.211.126.0/24 Valid Other IRR onlyRADB 672 100% 67
128.211.184.0/23 Valid Other IRR onlyRADB 672 100% 67
128.211.186.0/23 Valid Other IRR onlyRADB 672 100% 67
128.211.188.0/22 Valid Other IRR onlyRADB 672 100% 67
128.211.192.0/18 Valid Other IRR onlyRADB 672 100% 67
2607:ac80:400::/40 Valid Other IRR onlyRADB 634 100% 69

AS-SET

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

  • Route object: RIR11
ChangePrefix or setDetailFull-table peers
Route object: RIR128.211.64.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR128.211.96.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR128.211.112.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR128.211.120.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR128.211.124.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR128.211.126.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR128.211.184.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR128.211.186.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR128.211.188.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR128.211.192.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2607:ac80:400::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

Every route object with origin AS397501 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.