bgpreport

Network · data from 2026-11-12

AS269993 AS269993 - COMPANIA CHILENA DE COMUNICACIONES PARALLEL S.A.

Registry name: AS269993 - COMPANIA CHILENA DE COMUNICACIONES PARALLEL S.A., CL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269993, 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.
138.121.108.0/22 Valid Other IRR onlyRADB 673 100% 66
168.90.220.0/22 Valid Other IRR onlyRADB 673 100% 66
181.177.220.0/22 Valid Other IRR onlyRADB 673 100% 66
2803:4d00::/32 Valid Other IRR onlyRADB 634 100% 67
138.121.108.0/24 Valid Other IRR onlyRADB 12 2%low visibility 8
168.90.220.0/24 Valid Other IRR onlyRADB 12 2%low visibility 8
181.177.220.0/24 Valid Other IRR onlyRADB 12 2%low visibility 8

AS-SET

AS269993 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 22 are in fix.csv.

  • Route object: RIR7
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
Route object: RIR138.121.108.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR168.90.220.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR181.177.220.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2803:4d00::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR138.121.108.0/24Route object only in RADB. Add it in the RIR database for the space.12 of 673
Route object: RIR168.90.220.0/24Route object only in RADB. Add it in the RIR database for the space.12 of 673
Route object: RIR181.177.220.0/24Route object only in RADB. Add it in the RIR database for the space.12 of 673

Route objects not announced

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

138.121.108.0/23RADBValid
138.121.109.0/24RADBValid
138.121.110.0/23RADBValid
138.121.110.0/24RADBValid
138.121.111.0/24RADBValid
168.90.220.0/23RADBValid
168.90.221.0/24RADBValid
168.90.222.0/23RADBValid
168.90.222.0/24RADBValid
168.90.223.0/24RADBValid
181.177.220.0/23RADBValid
181.177.221.0/24RADBValid
181.177.222.0/23RADBValid
181.177.222.0/24RADBValid
181.177.223.0/24RADBValid

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.