bgpreport

Network · data from 2026-11-12

AS17055 UTAH - University of Utah

Registry name: UTAH - University of Utah, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17055, 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.110.216.0/21 No ROA Nonecovered by 128.110.0.0/16 671 100% 68
128.110.0.0/16 No ROA Other IRR onlyRADB 672 100% 68
155.97.0.0/16 No ROA Other IRR onlyRADB 672 100% 68
155.98.0.0/16 No ROA Other IRR onlyRADB 672 100% 68
155.99.0.0/16 No ROA Other IRR onlyRADB 672 100% 68
155.100.0.0/16 No ROA Other IRR onlyRADB 672 100% 68
155.101.0.0/16 No ROA Other IRR onlyRADB 672 100% 68
192.5.12.0/24 No ROA Other IRR onlyRADB 672 100% 68
128.110.96.0/22 No ROA Other IRR onlyRADB 671 100% 68
128.110.100.0/24 No ROA Other IRR onlyRADB 671 100% 68
128.110.152.0/22 No ROA Other IRR onlyRADB 671 100% 68
128.110.156.0/24 No ROA Other IRR onlyRADB 671 100% 68
155.98.32.0/20 No ROA Other IRR onlyRADB 671 100% 68
155.99.144.0/24 No ROA Other IRR onlyRADB 671 100% 68
155.101.66.0/24 No ROA Other IRR onlyRADB 671 100% 68
2604:c340::/32 No ROA Other IRR onlyRADB 635 100% 69
204.99.128.0/24 Valid Other IRR onlyRADB 673 100% 68
199.104.93.0/24 Valid Other IRR onlyRADB 672 100% 68

AS-SET

AS17055 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 42 are in fix.csv.

  • ROA: none16
  • Route object: none1
  • Route object: RIR17
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none128.110.216.0/21No ROA covers it. Add a ROA for AS17055, maxLength 21.671 of 673
Route object: none128.110.216.0/21No route object for it. A route object for 128.110.0.0/16 with origin AS17055 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17055 in the RIR database for the space.671 of 673
ROA: none128.110.0.0/16No ROA covers it. Add a ROA for AS17055, maxLength 16.672 of 673
Route object: RIR128.110.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none155.97.0.0/16No ROA covers it. Add a ROA for AS17055, maxLength 16.672 of 673
Route object: RIR155.97.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none155.98.0.0/16No ROA covers it. Add a ROA for AS17055, maxLength 16.672 of 673
Route object: RIR155.98.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none155.99.0.0/16No ROA covers it. Add a ROA for AS17055, maxLength 16.672 of 673
Route object: RIR155.99.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none155.100.0.0/16No ROA covers it. Add a ROA for AS17055, maxLength 16.672 of 673
Route object: RIR155.100.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none155.101.0.0/16No ROA covers it. Add a ROA for AS17055, maxLength 16.672 of 673
Route object: RIR155.101.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none192.5.12.0/24No ROA covers it. Add a ROA for AS17055, maxLength 24.672 of 673
Route object: RIR192.5.12.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none128.110.96.0/22No ROA covers it. Add a ROA for AS17055, maxLength 22.671 of 673
Route object: RIR128.110.96.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none128.110.100.0/24No ROA covers it. Add a ROA for AS17055, maxLength 24.671 of 673
Route object: RIR128.110.100.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none128.110.152.0/22No ROA covers it. Add a ROA for AS17055, maxLength 22.671 of 673
Route object: RIR128.110.152.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none128.110.156.0/24No ROA covers it. Add a ROA for AS17055, maxLength 24.671 of 673
Route object: RIR128.110.156.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none155.98.32.0/20No ROA covers it. Add a ROA for AS17055, maxLength 20.671 of 673
Route object: RIR155.98.32.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none155.99.144.0/24No ROA covers it. Add a ROA for AS17055, maxLength 24.671 of 673
Route object: RIR155.99.144.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none155.101.66.0/24No ROA covers it. Add a ROA for AS17055, maxLength 24.671 of 673
Route object: RIR155.101.66.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2604:c340::/32No ROA covers it. Add a ROA for AS17055, maxLength 32.635 of 636
Route object: RIR2604:c340::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR204.99.128.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR199.104.93.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

155.100.7.0/24RADBNo ROA
155.100.8.0/24RADBNo ROA
155.100.110.0/24RADBNo ROA
155.100.145.0/24RADBNo ROA
155.100.194.0/23RADBNo ROA
155.100.207.0/24RADBNo ROA
198.60.30.0/23RADBValid
204.99.160.0/20RADBValid

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.