bgpreport

Network · data from 2026-11-12

AS11975 WM - The College of William and Mary

Registry name: WM - The College of William and Mary, US · not in PeeringDB

8IPv4 routes 0.0% RPKI valid · 75.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
8No 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 AS11975, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS11975, 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.
139.70.224.0/19 No ROA Nonecovered by 139.70.128.0/17 672 100% 67
128.239.33.0/24 No ROA Nonecovered by 128.239.0.0/17 287 43% 62
128.239.0.0/16 No ROA Other IRR onlyRADB 669 99% 68
128.239.0.0/17 No ROA Other IRR onlyRADB 669 99% 68
128.239.128.0/17 No ROA Other IRR onlyRADB 669 99% 68
139.70.0.0/16 No ROA Other IRR onlyRADB 669 99% 68
139.70.0.0/17 No ROA Other IRR onlyRADB 669 99% 68
139.70.128.0/17 No ROA Other IRR onlyRADB 669 99% 68

AS-SET

AS11975 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 16 are in fix.csv.

  • ROA: none8
  • Route object: none2
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none139.70.224.0/19No ROA covers it. Add a ROA for AS11975, maxLength 19.672 of 673
Route object: none139.70.224.0/19No route object for it. A route object for 139.70.128.0/17 with origin AS11975 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11975 in the RIR database for the space.672 of 673
ROA: none128.239.33.0/24No ROA covers it. Add a ROA for AS11975, maxLength 24.287 of 673
Route object: none128.239.33.0/24No route object for it. A route object for 128.239.0.0/17 with origin AS11975 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11975 in the RIR database for the space.287 of 673
ROA: none128.239.0.0/16No ROA covers it. Add a ROA for AS11975, maxLength 16.669 of 673
Route object: RIR128.239.0.0/16Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none128.239.0.0/17No ROA covers it. Add a ROA for AS11975, maxLength 17.669 of 673
Route object: RIR128.239.0.0/17Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none128.239.128.0/17No ROA covers it. Add a ROA for AS11975, maxLength 17.669 of 673
Route object: RIR128.239.128.0/17Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none139.70.0.0/16No ROA covers it. Add a ROA for AS11975, maxLength 16.669 of 673
Route object: RIR139.70.0.0/16Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none139.70.0.0/17No ROA covers it. Add a ROA for AS11975, maxLength 17.669 of 673
Route object: RIR139.70.0.0/17Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none139.70.128.0/17No ROA covers it. Add a ROA for AS11975, maxLength 17.669 of 673
Route object: RIR139.70.128.0/17Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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