bgpreport

Network · data from 2026-11-12

AS265642 INETAMERICAS COMUNICACIONES LIMITADA

Registry name: AS265642 - INETAMERICAS COMUNICACIONES LIMITADA, CL · PeeringDB

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

Announced routes

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

179.63.224.0/22 Valid Nonecovered by 179.63.224.0/21 672 100% 67
179.63.228.0/22 Valid Nonecovered by 179.63.224.0/21 672 100% 67
179.63.228.0/24 Valid Nonecovered by 179.63.224.0/21 672 100% 67
179.63.229.0/24 Valid Nonecovered by 179.63.224.0/21 672 100% 67
179.63.230.0/24 Valid Nonecovered by 179.63.224.0/21 672 100% 67
179.63.231.0/24 Valid Nonecovered by 179.63.224.0/21 672 100% 67
190.4.80.0/24 Valid Nonecovered by 190.4.80.0/21 671 100% 67
190.4.81.0/24 Valid Nonecovered by 190.4.80.0/21 671 100% 67
190.4.82.0/24 Valid Nonecovered by 190.4.80.0/21 671 100% 67
190.4.83.0/24 Valid Nonecovered by 190.4.80.0/21 671 100% 67
190.4.84.0/22 Valid Nonecovered by 190.4.80.0/21 671 100% 67
190.4.84.0/24 Valid Nonecovered by 190.4.80.0/21 671 100% 67
190.4.85.0/24 Valid Nonecovered by 190.4.80.0/21 671 100% 67
190.4.86.0/24 Valid Nonecovered by 190.4.80.0/21 671 100% 67
190.4.87.0/24 Valid Nonecovered by 190.4.80.0/21 671 100% 67
170.247.164.0/22 Valid RIR databaseLACNIC 672 100% 67

AS-SET

AS265642'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 19 are in fix.csv.

  • Route object: none15
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none179.63.224.0/22No route object for it. A route object for 179.63.224.0/21 with origin AS265642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265642 in the RIR database for the space.672 of 673
Route object: none179.63.228.0/22No route object for it. A route object for 179.63.224.0/21 with origin AS265642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265642 in the RIR database for the space.672 of 673
Route object: none179.63.228.0/24No route object for it. A route object for 179.63.224.0/21 with origin AS265642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265642 in the RIR database for the space.672 of 673
Route object: none179.63.229.0/24No route object for it. A route object for 179.63.224.0/21 with origin AS265642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265642 in the RIR database for the space.672 of 673
Route object: none179.63.230.0/24No route object for it. A route object for 179.63.224.0/21 with origin AS265642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265642 in the RIR database for the space.672 of 673
Route object: none179.63.231.0/24No route object for it. A route object for 179.63.224.0/21 with origin AS265642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265642 in the RIR database for the space.672 of 673
Route object: none190.4.80.0/24No route object for it. A route object for 190.4.80.0/21 with origin AS265642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265642 in the RIR database for the space.671 of 673
Route object: none190.4.81.0/24No route object for it. A route object for 190.4.80.0/21 with origin AS265642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265642 in the RIR database for the space.671 of 673
Route object: none190.4.82.0/24No route object for it. A route object for 190.4.80.0/21 with origin AS265642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265642 in the RIR database for the space.671 of 673
Route object: none190.4.83.0/24No route object for it. A route object for 190.4.80.0/21 with origin AS265642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265642 in the RIR database for the space.671 of 673
Route object: none190.4.84.0/22No route object for it. A route object for 190.4.80.0/21 with origin AS265642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265642 in the RIR database for the space.671 of 673
Route object: none190.4.84.0/24No route object for it. A route object for 190.4.80.0/21 with origin AS265642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265642 in the RIR database for the space.671 of 673
Route object: none190.4.85.0/24No route object for it. A route object for 190.4.80.0/21 with origin AS265642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265642 in the RIR database for the space.671 of 673
Route object: none190.4.86.0/24No route object for it. A route object for 190.4.80.0/21 with origin AS265642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265642 in the RIR database for the space.671 of 673
Route object: none190.4.87.0/24No route object for it. A route object for 190.4.80.0/21 with origin AS265642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265642 in the RIR database for the space.671 of 673

Route objects not announced

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

179.63.224.0/21LACNICValid
179.63.232.0/22LACNICValid
190.4.80.0/21LACNICValid
2803:7b00::/32LACNICValid

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.