bgpreport

Network · data from 2026-11-12

AS398813 MILLERSVILLE-UNIVERSITY - Millersville University of Pennsylvania

Registry name: MILLERSVILLE-UNIVERSITY - Millersville University of Pennsylvania, US · not in PeeringDB

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

Announced routes

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

166.66.0.0/17 Valid Nonecovered by 166.66.0.0/16 673 100% 68
166.66.128.0/18 Valid Nonecovered by 166.66.0.0/16 673 100% 68
166.66.192.0/21 Valid Nonecovered by 166.66.0.0/16 673 100% 68
166.66.200.0/23 Valid Nonecovered by 166.66.0.0/16 673 100% 68
166.66.203.0/24 Valid Nonecovered by 166.66.0.0/16 673 100% 68
166.66.204.0/22 Valid Nonecovered by 166.66.0.0/16 673 100% 68
166.66.208.0/20 Valid Nonecovered by 166.66.0.0/16 673 100% 68
166.66.224.0/19 Valid Nonecovered by 166.66.0.0/16 673 100% 68
192.206.29.0/24 Valid Other IRR onlyRADB 671 100% 69
204.235.168.0/23 Valid Other IRR onlyRADB 671 100% 69
2607:2240:5000::/36 Valid Other IRR onlyRADB 636 100% 67
204.235.168.0/24 Valid Other IRR onlyNTTCOM 2 0%low visibility 2

AS-SET

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

  • Route object: none8
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none166.66.0.0/17No route object for it. A route object for 166.66.0.0/16 with origin AS398813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398813 in the RIR database for the space.673 of 673
Route object: none166.66.128.0/18No route object for it. A route object for 166.66.0.0/16 with origin AS398813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398813 in the RIR database for the space.673 of 673
Route object: none166.66.192.0/21No route object for it. A route object for 166.66.0.0/16 with origin AS398813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398813 in the RIR database for the space.673 of 673
Route object: none166.66.200.0/23No route object for it. A route object for 166.66.0.0/16 with origin AS398813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398813 in the RIR database for the space.673 of 673
Route object: none166.66.203.0/24No route object for it. A route object for 166.66.0.0/16 with origin AS398813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398813 in the RIR database for the space.673 of 673
Route object: none166.66.204.0/22No route object for it. A route object for 166.66.0.0/16 with origin AS398813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398813 in the RIR database for the space.673 of 673
Route object: none166.66.208.0/20No route object for it. A route object for 166.66.0.0/16 with origin AS398813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398813 in the RIR database for the space.673 of 673
Route object: none166.66.224.0/19No route object for it. A route object for 166.66.0.0/16 with origin AS398813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398813 in the RIR database for the space.673 of 673
Route object: RIR192.206.29.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR204.235.168.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2607:2240:5000::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR204.235.168.0/24Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

166.66.0.0/16RADBValid

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.