bgpreport

Network · data from 2026-11-12

AS3354 THENET-AS-3354 - University of Texas System

Registry name: THENET-AS-3354 - University of Texas System, US · not in PeeringDB

14IPv4 routes 14.3% RPKI valid · 57.1% with a route object
2IPv6 routes 0.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
14No ROA 8 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS3354, seen from no peer

Announced routes

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

192.138.168.0/24 No ROA None 671 100% 67
2605:2800:100::/40 No ROA None 635 100% 69
2605:2800:101::/48 No ROA None 635 100% 69
198.214.2.0/24 No ROA Nonecovered by 198.214.0.0/16 141 21% 48
198.214.4.0/24 No ROA Nonecovered by 198.214.0.0/16 141 21% 48
198.214.6.0/24 No ROA Nonecovered by 198.214.0.0/16 141 21% 48
206.77.62.0/24 No ROA Nonecovered by 206.77.0.0/16 141 21% 48
206.77.63.0/24 No ROA Nonecovered by 206.77.0.0/16 141 21% 48
198.213.0.0/16 No ROA Other IRR onlyRADB 670 100% 67
198.214.0.0/16 No ROA Other IRR onlyRADB 670 100% 67
206.77.0.0/16 No ROA Other IRR onlyRADB 670 100% 67
207.64.0.0/16 No ROA Other IRR onlyRADB 670 100% 67
207.80.0.0/16 No ROA Other IRR onlyRADB 670 100% 67
198.153.169.0/24 No ROA Other IRR onlyRADB 668 99% 67
129.117.0.0/16 Valid RIR databaseARIN, RADB 670 100% 67
206.254.231.0/24 Valid RIR databaseARIN, RADB 554 82% 66

AS-SET

AS3354 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 36 are in fix.csv.

  • ROA: none14
  • Route object: none8
  • Route object: RIR6
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none192.138.168.0/24No ROA covers it. Add a ROA for AS3354, maxLength 24.671 of 673
Route object: none192.138.168.0/24No route object for it. Add a route object with origin AS3354 in the RIR database for the space.671 of 673
ROA: none2605:2800:100::/40No ROA covers it. Add a ROA for AS3354, maxLength 40.635 of 636
Route object: none2605:2800:100::/40No route object for it. Add a route object with origin AS3354 in the RIR database for the space.635 of 636
ROA: none2605:2800:101::/48No ROA covers it. Add a ROA for AS3354, maxLength 48.635 of 636
Route object: none2605:2800:101::/48No route object for it. Add a route object with origin AS3354 in the RIR database for the space.635 of 636
ROA: none198.214.2.0/24No ROA covers it. Add a ROA for AS3354, maxLength 24.141 of 673
Route object: none198.214.2.0/24No route object for it. A route object for 198.214.0.0/16 with origin AS3354 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3354 in the RIR database for the space.141 of 673
ROA: none198.214.4.0/24No ROA covers it. Add a ROA for AS3354, maxLength 24.141 of 673
Route object: none198.214.4.0/24No route object for it. A route object for 198.214.0.0/16 with origin AS3354 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3354 in the RIR database for the space.141 of 673
ROA: none198.214.6.0/24No ROA covers it. Add a ROA for AS3354, maxLength 24.141 of 673
Route object: none198.214.6.0/24No route object for it. A route object for 198.214.0.0/16 with origin AS3354 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3354 in the RIR database for the space.141 of 673
ROA: none206.77.62.0/24No ROA covers it. Add a ROA for AS3354, maxLength 24.141 of 673
Route object: none206.77.62.0/24No route object for it. A route object for 206.77.0.0/16 with origin AS3354 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3354 in the RIR database for the space.141 of 673
ROA: none206.77.63.0/24No ROA covers it. Add a ROA for AS3354, maxLength 24.141 of 673
Route object: none206.77.63.0/24No route object for it. A route object for 206.77.0.0/16 with origin AS3354 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3354 in the RIR database for the space.141 of 673
ROA: none198.213.0.0/16No ROA covers it. Add a ROA for AS3354, maxLength 16.670 of 673
Route object: RIR198.213.0.0/16Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none198.214.0.0/16No ROA covers it. Add a ROA for AS3354, maxLength 16.670 of 673
Route object: RIR198.214.0.0/16Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none206.77.0.0/16No ROA covers it. Add a ROA for AS3354, maxLength 16.670 of 673
Route object: RIR206.77.0.0/16Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none207.64.0.0/16No ROA covers it. Add a ROA for AS3354, maxLength 16.670 of 673
Route object: RIR207.64.0.0/16Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none207.80.0.0/16No ROA covers it. Add a ROA for AS3354, maxLength 16.670 of 673
Route object: RIR207.80.0.0/16Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none198.153.169.0/24No ROA covers it. Add a ROA for AS3354, maxLength 24.668 of 673
Route object: RIR198.153.169.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

162.89.0.0/16RADBNo ROA
162.89.0.0/20RADBNo ROA
162.89.16.0/22RADBNo ROA
162.89.24.0/21RADBNo ROA
162.89.32.0/19RADBNo ROA
162.89.64.0/18RADBNo ROA
162.89.128.0/17RADBNo ROA
198.97.62.0/24RADBNo ROA

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.