bgpreport

Network · data from 2026-11-12

AS5722 AS5722 - Universidad Nacional de Colombia

Registry name: AS5722 - Universidad Nacional de Colombia, CO · not in PeeringDB

32IPv4 routes 100.0% RPKI valid · 75.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 8 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS5722, seen from no peer

Announced routes

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

168.176.177.0/24 Valid None 673 100% 67
168.176.143.0/24 Valid Nonecovered by 168.176.140.0/22 672 100% 67
168.176.197.0/24 Valid None 672 100% 67
168.176.176.0/24 Valid None 671 100% 67
168.176.189.0/24 Valid None 671 100% 67
168.176.175.0/24 Valid None 669 99% 67
168.176.0.0/16 Valid None 2 0%low visibility 2
168.176.76.0/24 Valid Nonecovered by 168.176.64.0/19 2 0%low visibility 2
168.176.183.0/24 Valid Other IRR onlyRADB 673 100% 67
168.176.184.0/24 Valid Other IRR onlyRADB 673 100% 67
168.176.185.0/24 Valid Other IRR onlyRADB 673 100% 67
168.176.188.0/24 Valid Other IRR onlyRADB 673 100% 67
168.176.190.0/24 Valid Other IRR onlyRADB 673 100% 67
168.176.191.0/24 Valid Other IRR onlyRADB 673 100% 67
168.176.192.0/24 Valid Other IRR onlyRADB 673 100% 67
168.176.196.0/24 Valid Other IRR onlyRADB 673 100% 67
168.176.198.0/24 Valid Other IRR onlyRADB 673 100% 67
168.176.205.0/24 Valid Other IRR onlyRADB 673 100% 67
168.176.224.0/24 Valid Other IRR onlyRADB 673 100% 67
168.176.96.0/19 Valid Other IRR onlyRADB 672 100% 67
168.176.128.0/20 Valid Other IRR onlyRADB 672 100% 67
168.176.193.0/24 Valid Other IRR onlyRADB 672 100% 67
168.176.243.0/24 Valid Other IRR onlyRADB 672 100% 67
168.176.0.0/18 Valid Other IRR onlyRADB 671 100% 67
168.176.64.0/19 Valid Other IRR onlyRADB 671 100% 67
168.176.207.0/24 Valid Other IRR onlyRADB 671 100% 67
168.176.232.0/21 Valid Other IRR onlyRADB 671 100% 67
168.176.241.0/24 Valid Other IRR onlyRADB 671 100% 67
168.176.250.0/24 Valid Other IRR onlyRADB 671 100% 67
168.176.144.0/20 Valid Other IRR onlyRADB 670 100% 67
168.176.195.0/24 Valid Other IRR onlyRADB 670 100% 67
168.176.212.0/24 Valid Other IRR onlyRADB 670 100% 67

AS-SET

AS5722 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 46 are in fix.csv.

  • Route object: none8
  • Route object: RIR24
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
Route object: none168.176.177.0/24No route object for it. Add a route object with origin AS5722 in the RIR database for the space.673 of 673
Route object: none168.176.143.0/24No route object for it. A route object for 168.176.140.0/22 with origin AS5722 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5722 in the RIR database for the space.672 of 673
Route object: none168.176.197.0/24No route object for it. Add a route object with origin AS5722 in the RIR database for the space.672 of 673
Route object: none168.176.176.0/24No route object for it. Add a route object with origin AS5722 in the RIR database for the space.671 of 673
Route object: none168.176.189.0/24No route object for it. Add a route object with origin AS5722 in the RIR database for the space.671 of 673
Route object: none168.176.175.0/24No route object for it. Add a route object with origin AS5722 in the RIR database for the space.669 of 673
Route object: none168.176.0.0/16No route object for it. Add a route object with origin AS5722 in the RIR database for the space.2 of 673
Route object: none168.176.76.0/24No route object for it. A route object for 168.176.64.0/19 with origin AS5722 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5722 in the RIR database for the space.2 of 673
Route object: RIR168.176.183.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR168.176.184.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR168.176.185.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR168.176.188.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR168.176.190.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR168.176.191.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR168.176.192.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR168.176.196.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR168.176.198.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR168.176.205.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR168.176.224.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR168.176.96.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.176.128.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.176.193.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.176.243.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.176.0.0/18Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR168.176.64.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR168.176.207.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR168.176.232.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR168.176.241.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR168.176.250.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR168.176.144.0/20Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR168.176.195.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR168.176.212.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 AS5722 whose prefix no peer sees AS5722 announce. Many are kept on purpose (backup routes, space announced only in some places).

168.176.128.0/22RADBValid
168.176.132.0/23RADBValid
168.176.134.0/24RADBValid
168.176.136.0/22RADBValid
168.176.140.0/22RADBValid
168.176.160.0/21RADBValid
168.176.168.0/22RADBValid
168.176.172.0/23RADBValid
168.176.174.0/24RADBValid
168.176.180.0/24RADBValid
168.176.181.0/24RADBValid
168.176.182.0/24RADBValid
200.24.8.0/24RADBNo ROA
2800:8a0::/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.