bgpreport

Network · data from 2026-11-12

AS64120 NOCPERU-LATIN TECHNOLOGIES

Registry name: AS64120 - NOCPERU-LATIN TECHNOLOGIES, PE · PeeringDB

9IPv4 routes 77.8% RPKI valid · 77.8% with a route object
25IPv6 routes 100.0% RPKI valid · 68.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 10 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
31Route objects not announced registered with origin AS64120, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS64120, 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.
190.119.162.248/29 No ROA None 2 0%low visibility 2
190.119.208.104/29 No ROA None 2 0%low visibility 2
2803:f080:2e50::/44 Valid Nonecovered by 2803:f080:2e40::/43 636 100% 67
2803:f080:2e4c::/46 Valid Nonecovered by 2803:f080:2e40::/43 635 100% 67
2803:f080:2e50::/46 Valid Nonecovered by 2803:f080:2e40::/43 635 100% 67
2803:f080:2e58::/46 Valid Nonecovered by 2803:f080:2e40::/43 635 100% 67
2803:f080:2e5c::/46 Valid Nonecovered by 2803:f080:2e40::/43 635 100% 67
2803:f080:2e98::/45 Valid Nonecovered by 2803:f080:2e80::/43 635 100% 67
2803:e4d0:8000::/35 Valid None 1 0%low visibility 1
2803:e4d0:a000::/35 Valid None 1 0%low visibility 1
2803:8a10::/35 Valid Other IRR onlyRADB 635 100% 67
2803:e4d0::/35 Valid Other IRR onlyRADB 635 100% 67
200.49.242.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
200.49.243.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
179.60.204.0/24 Valid RIR databaseLACNIC, RADB 671 100% 67
179.60.205.0/24 Valid RIR databaseLACNIC, RADB 671 100% 67
179.60.206.0/24 Valid RIR databaseLACNIC, RADB 671 100% 67
200.49.240.0/24 Valid RIR databaseLACNIC, RADB 670 100% 67
200.49.241.0/24 Valid RIR databaseLACNIC, RADB 670 100% 67
2803:f080:2180::/43 Valid RIR databaseLACNIC, RADB 636 100% 67
2803:f080:22e0::/43 Valid RIR databaseLACNIC 636 100% 67
2803:f080:2300::/43 Valid RIR databaseLACNIC, RADB 636 100% 67
2803:f080:2320::/43 Valid RIR databaseLACNIC 636 100% 67
2803:f080:2340::/43 Valid RIR databaseLACNIC 636 100% 67
2803:f080:2e40::/43 Valid RIR databaseLACNIC 636 100% 67
2803:f080:c000::/35 Valid RIR databaseLACNIC 636 100% 67
2803:f080::/35 Valid RIR databaseLACNIC, RADB 635 100% 67
2803:f080:2080::/43 Valid RIR databaseLACNIC 635 100% 69
2803:f080:21a0::/43 Valid RIR databaseLACNIC, RADB 635 100% 67
2803:f080:2280::/43 Valid RIR databaseLACNIC, RADB 635 100% 67
2803:f080:2360::/43 Valid RIR databaseLACNIC, RADB 635 100% 67
2803:f080:2e80::/43 Valid RIR databaseLACNIC 635 100% 67
2803:f080:21e0::/43 Valid RIR databaseLACNIC, RADB 633 100% 67
2803:f080:2120::/43 Valid RIR databaseLACNIC 1 0%low visibility 1

AS-SET

AS64120'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 45 are in fix.csv.

  • ROA: none2
  • Route object: none10
  • Route object: RIR2
  • Route object: not announced31
ChangePrefix or setDetailFull-table peers
ROA: none190.119.162.248/29No ROA covers it. Add a ROA for AS64120, maxLength 29.2 of 673
Route object: none190.119.162.248/29No route object for it. Add a route object with origin AS64120 in the RIR database for the space.2 of 673
ROA: none190.119.208.104/29No ROA covers it. Add a ROA for AS64120, maxLength 29.2 of 673
Route object: none190.119.208.104/29No route object for it. Add a route object with origin AS64120 in the RIR database for the space.2 of 673
Route object: none2803:f080:2e50::/44No route object for it. A route object for 2803:f080:2e40::/43 with origin AS64120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64120 in the RIR database for the space.636 of 636
Route object: none2803:f080:2e4c::/46No route object for it. A route object for 2803:f080:2e40::/43 with origin AS64120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64120 in the RIR database for the space.635 of 636
Route object: none2803:f080:2e50::/46No route object for it. A route object for 2803:f080:2e40::/43 with origin AS64120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64120 in the RIR database for the space.635 of 636
Route object: none2803:f080:2e58::/46No route object for it. A route object for 2803:f080:2e40::/43 with origin AS64120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64120 in the RIR database for the space.635 of 636
Route object: none2803:f080:2e5c::/46No route object for it. A route object for 2803:f080:2e40::/43 with origin AS64120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64120 in the RIR database for the space.635 of 636
Route object: none2803:f080:2e98::/45No route object for it. A route object for 2803:f080:2e80::/43 with origin AS64120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64120 in the RIR database for the space.635 of 636
Route object: none2803:e4d0:8000::/35No route object for it. Add a route object with origin AS64120 in the RIR database for the space.1 of 636
Route object: none2803:e4d0:a000::/35No route object for it. Add a route object with origin AS64120 in the RIR database for the space.1 of 636
Route object: RIR2803:8a10::/35Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2803:e4d0::/35Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

179.60.207.0/24LACNIC, RADBValid
206.62.108.0/22ARINValid
2803:8a10::/32LACNICValid
2803:f080:2020::/43LACNICValid
2803:f080:20a0::/43LACNIC, RADBValid
2803:f080:20e0::/43LACNICValid
2803:f080:2160::/43LACNICValid
2803:f080:21c0::/43LACNIC, RADBValid
2803:f080:2200::/43LACNICValid
2803:f080:2220::/43LACNIC, RADBValid
2803:f080:2240::/43LACNICValid
2803:f080:2260::/43RADBNo ROA
2803:f080:2a00::/39LACNICValid
2803:f080:2c00::/39LACNICValid
2803:f080:2c00::/43LACNICValid
2803:f080:2c20::/43LACNICValid
2803:f080:2c40::/43LACNICValid
2803:f080:2c60::/43LACNICValid
2803:f080:4000::/35LACNICValid
2803:f080:6000::/35LACNICValid
2803:f080:8000::/35LACNICValid
2803:f080:80a0::/43LACNICValid
2803:f080:80c0::/43LACNICValid
2803:f080:80e0::/43LACNICValid
2803:f080:8100::/43LACNICValid
2803:f080:8120::/43LACNICValid
2803:f080:8140::/43LACNICValid
2803:f080:8800::/43LACNICValid
2803:f080:a000::/35LACNICValid
2803:f080:e000::/35LACNICValid
2803:f880:2080::/43RADBNo 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.