bgpreport

Network · data from 2026-11-12

AS22323 UNIVERSITY-OF-CALIFORNIA-MERCED - University of California, Merced

Registry name: UNIVERSITY-OF-CALIFORNIA-MERCED - University of California, Merced, US · not in PeeringDB

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

Announced routes

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

169.236.28.0/24 No ROA Nonecovered by 169.236.0.0/16 20 3%low visibility 18
137.164.23.82/31 No ROA None 1 0%low visibility 1
137.164.23.136/29 No ROA None 1 0%low visibility 1
204.102.225.40/31 No ROA None 1 0%low visibility 1
169.236.0.0/16 No ROA Other IRR onlyRADB 669 99% 68

AS-SET

AS22323 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 13 are in fix.csv.

  • ROA: none5
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none169.236.28.0/24No ROA covers it. Add a ROA for AS22323, maxLength 24.20 of 673
Route object: none169.236.28.0/24No route object for it. A route object for 169.236.0.0/16 with origin AS22323 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22323 in the RIR database for the space.20 of 673
ROA: none137.164.23.82/31No ROA covers it. Add a ROA for AS22323, maxLength 31.1 of 673
Route object: none137.164.23.82/31No route object for it. Add a route object with origin AS22323 in the RIR database for the space.1 of 673
ROA: none137.164.23.136/29No ROA covers it. Add a ROA for AS22323, maxLength 29.1 of 673
Route object: none137.164.23.136/29No route object for it. Add a route object with origin AS22323 in the RIR database for the space.1 of 673
ROA: none204.102.225.40/31No ROA covers it. Add a ROA for AS22323, maxLength 31.1 of 673
Route object: none204.102.225.40/31No route object for it. Add a route object with origin AS22323 in the RIR database for the space.1 of 673
ROA: none169.236.0.0/16No ROA covers it. Add a ROA for AS22323, maxLength 16.669 of 673
Route object: RIR169.236.0.0/16Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

192.35.212.0/23RADBNo ROA
192.35.214.0/24RADBNo ROA
198.175.158.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.