bgpreport

Network · data from 2026-11-12

AS397913 ESU-AS - East Stroudsburg University of Pennsylvania

Registry name: ESU-AS - East Stroudsburg University of Pennsylvania, US · not in PeeringDB

8IPv4 routes 100.0% RPKI valid · 75.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 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS397913, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS397913, 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.
206.225.96.0/20 Valid Nonecovered by 206.225.96.0/19 673 100% 68
206.225.112.0/20 Valid Nonecovered by 206.225.96.0/19 673 100% 68
192.147.113.0/24 Valid Other IRR onlyRADB 671 100% 69
192.148.218.0/24 Valid Other IRR onlyRADB 671 100% 69
192.153.187.0/24 Valid Other IRR onlyRADB 671 100% 69
204.108.182.0/23 Valid Other IRR onlyRADB 671 100% 69
206.225.96.0/19 Valid Other IRR onlyRADB 671 100% 69
2607:2240:b000::/36 Valid Other IRR onlyRADB 636 100% 67
204.235.160.0/23 Valid RIR databaseARIN, RADB 671 100% 69

AS-SET

AS397913 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 8 are in fix.csv.

  • Route object: none2
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
Route object: none206.225.96.0/20No route object for it. A route object for 206.225.96.0/19 with origin AS397913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397913 in the RIR database for the space.673 of 673
Route object: none206.225.112.0/20No route object for it. A route object for 206.225.96.0/19 with origin AS397913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397913 in the RIR database for the space.673 of 673
Route object: RIR192.147.113.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR192.148.218.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR192.153.187.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR204.108.182.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR206.225.96.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2607:2240:b000::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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