bgpreport

Network · data from 2026-11-12

AS18 UTEXAS

Registry name: UTEXAS - University of Texas at Austin, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18, 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.
198.214.250.0/23 No ROA None 673 100% 68
128.62.0.0/16 No ROA Other IRR onlyRADB 673 100% 68
128.83.0.0/16 No ROA Other IRR onlyRADB 673 100% 68
129.116.0.0/16 No ROA Other IRR onlyRADB 673 100% 68
146.6.0.0/16 No ROA Other IRR onlyRADB 673 100% 68
198.214.80.0/20 No ROA Other IRR onlyRADB 673 100% 67
198.213.192.0/18 No ROA RIR databaseARIN 673 100% 68
206.76.64.0/18 Valid RIR databaseARIN, RADB 673 100% 68

AS-SET

AS18's PeeringDB record names no 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 15 are in fix.csv.

  • ROA: none7
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none198.214.250.0/23No ROA covers it. Add a ROA for AS18, maxLength 23.673 of 673
Route object: none198.214.250.0/23No route object for it. Add a route object with origin AS18 in the RIR database for the space.673 of 673
ROA: none128.62.0.0/16No ROA covers it. Add a ROA for AS18, maxLength 16.673 of 673
Route object: RIR128.62.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none128.83.0.0/16No ROA covers it. Add a ROA for AS18, maxLength 16.673 of 673
Route object: RIR128.83.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none129.116.0.0/16No ROA covers it. Add a ROA for AS18, maxLength 16.673 of 673
Route object: RIR129.116.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none146.6.0.0/16No ROA covers it. Add a ROA for AS18, maxLength 16.673 of 673
Route object: RIR146.6.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none198.214.80.0/20No ROA covers it. Add a ROA for AS18, maxLength 20.673 of 673
Route object: RIR198.214.80.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none198.213.192.0/18No ROA covers it. Add a ROA for AS18, maxLength 18.673 of 673

Route objects not announced

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

192.67.11.0/24RADBNo ROA
192.195.222.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.