bgpreport

Network · data from 2026-11-12

AS299 UCI

Registry name: UCINET-AS - University of California, Irvine, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS299, 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.200.132.248/32 No ROA Nonecovered by 128.200.0.0/16 1 0%low visibility 1
137.164.23.92/31 No ROA None 1 0%low visibility 1
137.164.24.120/31 No ROA None 1 0%low visibility 1
2607:f380:1::118:9a41:75c0/123 No ROA None 1 0%low visibility 1
2607:f380:1::118:9a41:8780/123 No ROA None 1 0%low visibility 1
128.195.0.0/16 No ROA Other IRR onlyRADB 669 99% 68
128.200.0.0/16 No ROA Other IRR onlyRADB 669 99% 68
160.87.0.0/16 No ROA Other IRR onlyRADB 669 99% 68
169.234.0.0/16 No ROA Other IRR onlyRADB 669 99% 68
192.5.19.0/24 No ROA Other IRR onlyRADB 669 99% 68
2607:f538::/32 No ROA Other IRR onlyRADB 631 99% 69

AS-SET

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

  • ROA: none11
  • Route object: none5
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none128.200.132.248/32No ROA covers it. Add a ROA for AS299, maxLength 32.1 of 673
Route object: none128.200.132.248/32No route object for it. A route object for 128.200.0.0/16 with origin AS299 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS299 in the RIR database for the space.1 of 673
ROA: none137.164.23.92/31No ROA covers it. Add a ROA for AS299, maxLength 31.1 of 673
Route object: none137.164.23.92/31No route object for it. Add a route object with origin AS299 in the RIR database for the space.1 of 673
ROA: none137.164.24.120/31No ROA covers it. Add a ROA for AS299, maxLength 31.1 of 673
Route object: none137.164.24.120/31No route object for it. Add a route object with origin AS299 in the RIR database for the space.1 of 673
ROA: none2607:f380:1::118:9a41:75c0/123No ROA covers it. Add a ROA for AS299, maxLength 123.1 of 636
Route object: none2607:f380:1::118:9a41:75c0/123No route object for it. Add a route object with origin AS299 in the RIR database for the space.1 of 636
ROA: none2607:f380:1::118:9a41:8780/123No ROA covers it. Add a ROA for AS299, maxLength 123.1 of 636
Route object: none2607:f380:1::118:9a41:8780/123No route object for it. Add a route object with origin AS299 in the RIR database for the space.1 of 636
ROA: none128.195.0.0/16No ROA covers it. Add a ROA for AS299, maxLength 16.669 of 673
Route object: RIR128.195.0.0/16Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none128.200.0.0/16No ROA covers it. Add a ROA for AS299, maxLength 16.669 of 673
Route object: RIR128.200.0.0/16Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none160.87.0.0/16No ROA covers it. Add a ROA for AS299, maxLength 16.669 of 673
Route object: RIR160.87.0.0/16Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none169.234.0.0/16No ROA covers it. Add a ROA for AS299, maxLength 16.669 of 673
Route object: RIR169.234.0.0/16Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none192.5.19.0/24No ROA covers it. Add a ROA for AS299, maxLength 24.669 of 673
Route object: RIR192.5.19.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2607:f538::/32No ROA covers it. Add a ROA for AS299, maxLength 32.631 of 636
Route object: RIR2607:f538::/32Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

Every route object with origin AS299 is announced.

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.