bgpreport

Network · data from 2026-11-12

AS18777 TEXAS-STATE-UNIVERSITY - Texas State University

Registry name: TEXAS-STATE-UNIVERSITY - Texas State University, US · not in PeeringDB

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

Announced routes

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

147.26.255.0/24 No ROA Nonecovered by 147.26.0.0/16 670 100% 68
147.26.5.0/24 No ROA Nonecovered by 147.26.0.0/16 20 3%low visibility 18
147.26.0.0/16 No ROA Other IRR onlyRADB 673 100% 68
192.92.115.0/24 No ROA Other IRR onlyRADB 670 100% 68
74.200.138.0/24 Valid RIR databaseARIN, RADB 669 99% 68

AS-SET

AS18777 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 15 are in fix.csv.

  • ROA: none4
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none147.26.255.0/24No ROA covers it. Add a ROA for AS18777, maxLength 24.670 of 673
Route object: none147.26.255.0/24No route object for it. A route object for 147.26.0.0/16 with origin AS18777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18777 in the RIR database for the space.670 of 673
ROA: none147.26.5.0/24No ROA covers it. Add a ROA for AS18777, maxLength 24.20 of 673
Route object: none147.26.5.0/24No route object for it. A route object for 147.26.0.0/16 with origin AS18777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18777 in the RIR database for the space.20 of 673
ROA: none147.26.0.0/16No ROA covers it. Add a ROA for AS18777, maxLength 16.673 of 673
Route object: RIR147.26.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none192.92.115.0/24No ROA covers it. Add a ROA for AS18777, maxLength 24.670 of 673
Route object: RIR192.92.115.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

74.200.136.0/24ARIN, RADBValid
134.114.0.0/16RADBNo ROA
147.26.208.0/23RADBNo ROA
147.26.212.0/24RADBNo ROA
147.26.220.0/22RADBNo ROA
147.26.224.0/24RADBNo ROA
199.83.218.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.