bgpreport

Network · data from 2026-11-12

AS131 UCSB-NET-AS - University of California, Santa Barbara

Registry name: UCSB-NET-AS - University of California, Santa Barbara, US · not in PeeringDB

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

Announced routes

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

137.164.23.8/31 No ROA None 1 0%low visibility 1
137.164.23.90/31 No ROA None 1 0%low visibility 1
2607:f380:1::118:9a41:7080/123 No ROA None 1 0%low visibility 1
2607:f380:1::118:9a41:75a0/123 No ROA None 1 0%low visibility 1
128.111.0.0/16 No ROA Other IRR onlyRADB 669 99% 68
169.231.0.0/16 No ROA Other IRR onlyRADB 669 99% 68
192.35.222.0/24 No ROA Other IRR onlyRADB 669 99% 68
192.150.216.0/23 No ROA Other IRR onlyRADB 669 99% 68
199.120.153.0/24 No ROA Other IRR onlyRADB 669 99% 68
2607:f378::/32 No ROA Other IRR onlyRADB 633 100% 68

AS-SET

AS131 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 22 are in fix.csv.

  • ROA: none10
  • Route object: none4
  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none137.164.23.8/31No ROA covers it. Add a ROA for AS131, maxLength 31.1 of 673
Route object: none137.164.23.8/31No route object for it. Add a route object with origin AS131 in the RIR database for the space.1 of 673
ROA: none137.164.23.90/31No ROA covers it. Add a ROA for AS131, maxLength 31.1 of 673
Route object: none137.164.23.90/31No route object for it. Add a route object with origin AS131 in the RIR database for the space.1 of 673
ROA: none2607:f380:1::118:9a41:7080/123No ROA covers it. Add a ROA for AS131, maxLength 123.1 of 636
Route object: none2607:f380:1::118:9a41:7080/123No route object for it. Add a route object with origin AS131 in the RIR database for the space.1 of 636
ROA: none2607:f380:1::118:9a41:75a0/123No ROA covers it. Add a ROA for AS131, maxLength 123.1 of 636
Route object: none2607:f380:1::118:9a41:75a0/123No route object for it. Add a route object with origin AS131 in the RIR database for the space.1 of 636
ROA: none128.111.0.0/16No ROA covers it. Add a ROA for AS131, maxLength 16.669 of 673
Route object: RIR128.111.0.0/16Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none169.231.0.0/16No ROA covers it. Add a ROA for AS131, maxLength 16.669 of 673
Route object: RIR169.231.0.0/16Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none192.35.222.0/24No ROA covers it. Add a ROA for AS131, maxLength 24.669 of 673
Route object: RIR192.35.222.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none192.150.216.0/23No ROA covers it. Add a ROA for AS131, maxLength 23.669 of 673
Route object: RIR192.150.216.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none199.120.153.0/24No ROA covers it. Add a ROA for AS131, maxLength 24.669 of 673
Route object: RIR199.120.153.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2607:f378::/32No ROA covers it. Add a ROA for AS131, maxLength 32.633 of 636
Route object: RIR2607:f378::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

192.150.216.0/24RADBNo ROA
192.150.217.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.