bgpreport

Network · data from 2026-11-12

AS1929 UMASSNET-NET - University of Massachusetts - AMHERST

Registry name: UMASSNET-NET - University of Massachusetts - AMHERST, US · not in PeeringDB

5IPv4 routes 0.0% RPKI valid · 40.0% with a route object
3IPv6 routes 0.0% RPKI valid · 33.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
8No ROA 5 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS1929, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS1929, 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.
205.172.168.0/22 No ROA Other origin only 673 100% 68
69.16.44.0/24 No ROA Nonecovered by 69.16.44.0/23 5 1%low visibility 5
205.172.169.0/24 No ROA None 5 1%low visibility 5
2001:48e8:6400::/48 No ROA Nonecovered by 2001:48e8:6400::/44 4 1%low visibility 4
2001:48e8:6402::/48 No ROA Nonecovered by 2001:48e8:6400::/44 4 1%low visibility 4
69.16.44.0/23 No ROA RIR databaseARIN 673 100% 68
198.22.255.0/24 No ROA RIR databaseARIN 673 100% 68
2001:48e8:6400::/44 No ROA RIR databaseARIN 636 100% 68

AS-SET

AS1929 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.

  • ROA: none8
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: none205.172.168.0/22No ROA covers it. Add a ROA for AS1929, maxLength 22.673 of 673
Route object: none205.172.168.0/22Route objects for it name AS198949. Add a route object with origin AS1929 in the RIR database for the space.673 of 673
ROA: none69.16.44.0/24No ROA covers it. Add a ROA for AS1929, maxLength 24.5 of 673
Route object: none69.16.44.0/24No route object for it. A route object for 69.16.44.0/23 with origin AS1929 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1929 in the RIR database for the space.5 of 673
ROA: none205.172.169.0/24No ROA covers it. Add a ROA for AS1929, maxLength 24.5 of 673
Route object: none205.172.169.0/24No route object for it. Add a route object with origin AS1929 in the RIR database for the space.5 of 673
ROA: none2001:48e8:6400::/48No ROA covers it. Add a ROA for AS1929, maxLength 48.4 of 636
Route object: none2001:48e8:6400::/48No route object for it. A route object for 2001:48e8:6400::/44 with origin AS1929 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1929 in the RIR database for the space.4 of 636
ROA: none2001:48e8:6402::/48No ROA covers it. Add a ROA for AS1929, maxLength 48.4 of 636
Route object: none2001:48e8:6402::/48No route object for it. A route object for 2001:48e8:6400::/44 with origin AS1929 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1929 in the RIR database for the space.4 of 636
ROA: none69.16.44.0/23No ROA covers it. Add a ROA for AS1929, maxLength 23.673 of 673
ROA: none198.22.255.0/24No ROA covers it. Add a ROA for AS1929, maxLength 24.673 of 673
ROA: none2001:48e8:6400::/44No ROA covers it. Add a ROA for AS1929, maxLength 44.636 of 636

Route objects not announced

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