bgpreport

Network · data from 2026-11-12

AS265696 AS265696 - Asociacion Red Universitaria de Alta Velocidad del Valle del Cauca

Registry name: AS265696 - Asociacion Red Universitaria de Alta Velocidad del Valle del Cauca, CO · not in PeeringDB

21IPv4 routes 85.7% RPKI valid · 47.6% with a route object
1IPv6 routes 100.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 12 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS265696, seen from no peer

Announced routes

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

45.5.162.0/24 No ROA Nonecovered by 45.5.160.0/22 671 100% 67
45.5.163.0/24 No ROA Nonecovered by 45.5.160.0/22 669 99% 67
45.183.198.0/24 No ROA Other IRR onlyRADB 670 100% 67
45.5.164.0/23 Valid Nonecovered by 45.5.164.0/22 672 100% 67
45.5.186.0/23 Valid None 672 100% 67
45.5.188.0/23 Valid Nonecovered by 45.5.188.0/22 672 100% 67
131.196.212.0/23 Valid Nonecovered by 131.196.212.0/22 672 100% 67
131.196.208.0/23 Valid Nonecovered by 131.196.208.0/22 670 100% 67
131.196.214.0/24 Valid Nonecovered by 131.196.214.0/23 670 100% 67
131.196.215.0/24 Valid Nonecovered by 131.196.214.0/23 670 100% 67
200.3.192.0/24 Valid None 669 99% 67
2801:17:d000::/48 Valid None 636 100% 67
45.5.164.0/24 Valid Nonecovered by 45.5.164.0/22 12 2%low visibility 9
45.5.172.0/23 Valid Other IRR onlyRADB 672 100% 67
45.5.174.0/23 Valid Other IRR onlyRADB 672 100% 66
45.5.166.0/23 Valid Other IRR onlyRADB 670 100% 67
45.5.184.0/23 Valid Other IRR onlyRADB 670 100% 67
45.183.197.0/24 Valid Other IRR onlyRADB 670 100% 67
45.5.160.0/23 Valid RIR databaseLACNIC 672 100% 67
45.5.190.0/23 Valid RIR databaseLACNIC, RADB 670 100% 67
131.196.210.0/24 Valid RIR databaseLACNIC, RADB 670 100% 67
131.196.211.0/24 Valid RIR databaseLACNIC, RADB 670 100% 67

AS-SET

AS265696 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 35 are in fix.csv.

  • ROA: none3
  • Route object: none12
  • Route object: RIR6
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none45.5.162.0/24No ROA covers it. Add a ROA for AS265696, maxLength 24.671 of 673
Route object: none45.5.162.0/24No route object for it. A route object for 45.5.160.0/22 with origin AS265696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265696 in the RIR database for the space.671 of 673
ROA: none45.5.163.0/24No ROA covers it. Add a ROA for AS265696, maxLength 24.669 of 673
Route object: none45.5.163.0/24No route object for it. A route object for 45.5.160.0/22 with origin AS265696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265696 in the RIR database for the space.669 of 673
ROA: none45.183.198.0/24No ROA covers it. Add a ROA for AS265696, maxLength 24.670 of 673
Route object: RIR45.183.198.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: none45.5.164.0/23No route object for it. A route object for 45.5.164.0/22 with origin AS265696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265696 in the RIR database for the space.672 of 673
Route object: none45.5.186.0/23No route object for it. Add a route object with origin AS265696 in the RIR database for the space.672 of 673
Route object: none45.5.188.0/23No route object for it. A route object for 45.5.188.0/22 with origin AS265696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265696 in the RIR database for the space.672 of 673
Route object: none131.196.212.0/23No route object for it. A route object for 131.196.212.0/22 with origin AS265696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265696 in the RIR database for the space.672 of 673
Route object: none131.196.208.0/23No route object for it. A route object for 131.196.208.0/22 with origin AS265696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265696 in the RIR database for the space.670 of 673
Route object: none131.196.214.0/24No route object for it. A route object for 131.196.214.0/23 with origin AS265696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265696 in the RIR database for the space.670 of 673
Route object: none131.196.215.0/24No route object for it. A route object for 131.196.214.0/23 with origin AS265696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265696 in the RIR database for the space.670 of 673
Route object: none200.3.192.0/24No route object for it. Add a route object with origin AS265696 in the RIR database for the space.669 of 673
Route object: none2801:17:d000::/48No route object for it. Add a route object with origin AS265696 in the RIR database for the space.636 of 636
Route object: none45.5.164.0/24No route object for it. A route object for 45.5.164.0/22 with origin AS265696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265696 in the RIR database for the space.12 of 673
Route object: RIR45.5.172.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.5.174.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.5.166.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.5.184.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.183.197.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 AS265696 whose prefix no peer sees AS265696 announce. Many are kept on purpose (backup routes, space announced only in some places).

45.5.160.0/22RADBNo ROA
45.5.164.0/22RADBValid
45.5.180.0/22RADBNo ROA
45.5.188.0/22LACNICValid
45.183.196.0/24RADBNo ROA
131.196.208.0/22LACNICValid
131.196.210.0/23LACNICValid
131.196.212.0/22LACNICValid
131.196.214.0/23LACNICValid
2801:15:3000::/48LACNICValid
2801:19:3000::/48LACNICValid
2801:1b:d000::/48LACNICValid
2801:1f:d000::/48RADBNo ROA
2803:3d60::/32RADBNo 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.