bgpreport

Network · data from 2026-11-12

AS27757 CORPORACION NACIONAL DE TELECOMUNICACIONES CNT EP

Registry name: AS27757 - CORPORACION NACIONAL DE TELECOMUNICACIONES - CNT EP, EC · PeeringDB

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

Announced routes

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

186.42.0.0/24 Valid Other origin onlycovered by 186.42.0.0/17 671 100% 67
186.42.128.0/22 Valid Other origin onlycovered by 186.42.128.0/17 671 100% 67
190.152.255.0/24 Valid RIR databaseLACNIC, RADB 670 100% 67
190.152.108.0/24 Valid RIR databaseLACNIC 669 99% 67
190.152.109.0/24 Valid RIR databaseLACNIC 669 99% 67
190.152.187.0/24 Valid RIR databaseLACNIC 669 99% 67
190.214.123.0/24 Valid RIR databaseLACNIC 669 99% 67

AS-SET

AS27757'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 139 are in fix.csv.

  • Route object: none2
  • Route object: not announced137
ChangePrefix or setDetailFull-table peers
Route object: none186.42.0.0/24Route objects for it name AS28006. A route object for 186.42.0.0/17 with origin AS27757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27757 in the RIR database for the space.671 of 673
Route object: none186.42.128.0/22Route objects for it name AS28006. A route object for 186.42.128.0/17 with origin AS27757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27757 in the RIR database for the space.671 of 673

Route objects not announced

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

64.76.192.0/21RADBNo ROA
64.76.216.0/21RADBNo ROA
65.172.180.0/24RADBNo ROA
181.112.0.0/16LACNIC, RADBValid
181.112.204.0/22LACNICValid
181.113.0.0/16LACNIC, RADBValid
181.113.32.0/21LACNICValid
181.113.97.0/24LACNICValid
181.113.157.0/24LACNICValid
181.188.212.0/24LACNICValid
181.196.10.0/24LACNICValid
181.196.11.0/24LACNICValid
181.196.12.0/24LACNICValid
181.196.13.0/24LACNICValid
181.196.14.0/24LACNICValid
181.196.66.0/24LACNICValid
181.196.88.0/24LACNICValid
181.196.136.0/21LACNICValid
181.196.146.0/23LACNICValid
181.211.104.0/24LACNICValid
181.211.105.0/24LACNICValid
181.211.106.0/24LACNICValid
181.211.217.0/24LACNICValid
181.211.248.0/24LACNICValid
186.42.0.0/17LACNICValid
186.42.8.0/24LACNICValid
186.42.9.0/24LACNICValid
186.42.12.0/24LACNICValid
186.42.13.0/24LACNICValid
186.42.112.0/23LACNICValid
186.42.128.0/17LACNICValid
186.42.172.0/22LACNICValid
186.42.182.0/23RADBValid
186.42.198.0/23LACNICValid
186.46.0.0/16RADBNo ROA
186.46.56.0/22LACNICValid
186.46.88.0/21LACNICValid
186.46.92.0/22LACNICValid
186.46.128.0/17LACNICValid
186.46.140.0/24LACNICValid
186.46.141.0/24LACNICValid
186.46.152.0/21LACNICValid
186.46.172.0/24LACNICValid
186.46.175.0/24LACNICValid
186.46.224.0/24LACNICValid
186.46.232.0/21LACNICValid
186.47.0.0/16LACNIC, RADBValid
186.47.137.0/24LACNICValid
186.47.138.0/24LACNICValid
186.47.182.0/24LACNICValid
186.47.183.0/24LACNICValid
186.178.0.0/16LACNIC, RADBValid
186.178.6.0/23LACNICValid
186.178.19.0/24LACNICValid
186.178.36.0/23LACNICValid
186.178.37.0/24LACNICValid
186.178.43.0/24LACNICValid
186.178.47.0/24LACNICValid
186.178.48.0/24LACNICValid
186.178.51.0/24LACNICValid
186.178.66.0/24LACNICValid
186.178.67.0/24LACNICValid
186.178.107.0/24LACNICValid
186.178.109.0/24LACNICValid
186.178.112.0/24LACNICValid
186.178.115.0/24LACNICValid
186.178.117.0/24LACNICValid
186.178.170.0/24LACNICValid
190.9.160.0/20RADBNo ROA
190.9.176.0/20RADBNo ROA
190.11.0.0/19LACNIC, RADBValid
190.11.3.0/24LACNICValid
190.11.20.0/24LACNICValid
190.11.26.0/24LACNICValid
190.152.0.0/17LACNICValid
190.152.38.0/24LACNICValid
190.152.39.0/24LACNICValid
190.152.46.0/24LACNICValid
190.152.64.0/18RADBValid
190.152.68.0/24RADBValid
190.152.74.0/24RADBValid
190.152.75.0/24RADBValid
190.152.110.0/24LACNICValid
190.152.128.0/17LACNIC, RADBValid
190.152.131.0/24LACNICValid
190.152.144.0/24LACNICValid
190.152.161.0/24LACNICValid
190.152.185.0/24LACNICValid
190.152.191.0/24LACNICValid
190.152.201.0/24LACNICValid
190.152.220.0/24LACNICValid
190.152.236.0/24LACNICValid
190.152.237.0/24LACNICValid
190.152.254.0/24LACNICValid
190.214.0.0/16RADBNo ROA
190.214.0.0/17LACNIC, RADBValid
190.216.208.0/20RADBNo ROA
200.6.80.0/21RADBNo ROA
200.29.240.0/21RADBNo ROA
200.31.0.0/24RADBNo ROA
200.31.6.0/24RADBNo ROA
200.31.8.0/23RADBNo ROA
200.31.10.0/24RADBNo ROA
200.31.24.0/21RADBNo ROA
200.32.68.0/22RADBNo ROA
200.32.72.0/23RADBNo ROA
200.41.0.0/22RADBNo ROA
200.41.10.0/23RADBNo ROA
200.41.80.0/22RADBNo ROA
200.41.89.0/24RADBNo ROA
200.41.92.0/24RADBNo ROA
200.41.114.0/24RADBNo ROA
200.107.18.0/24LACNICValid
200.107.22.0/24LACNICValid
200.107.29.0/24LACNICValid
200.107.59.0/24LACNICValid
200.125.128.0/20RADBNo ROA
200.125.144.0/20RADBNo ROA
200.125.224.0/19LACNIC, RADBValid
201.219.28.0/24LACNICValid
201.219.43.0/24LACNICValid
201.219.50.0/24LACNICValid
201.219.56.0/24LACNICValid
201.234.80.0/21RADBNo ROA
201.234.192.0/20RADBNo ROA
201.234.208.0/20RADBNo ROA
208.232.120.0/24RADBNo ROA
2800:370:c::/48LACNICValid
2800:370:14::/48LACNICValid
2800:370:26::/48LACNICValid
2800:370:2a::/48LACNICValid
2800:370:32::/48LACNICValid
2800:370:3a::/48LACNICValid
2800:370:ba::/48LACNICValid
2800:660::/31RADBNo ROA
2801:0:420::/48RADBNo ROA
2803:a400::/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.