Network · data from 2026-11-12
AS27768 Compañía Paraguaya de Comunicaciones S.A.
Registry name: AS27768 - COMPANIA PARAGUAYA DE COMUNICACIONES S.A. (COPACO S.A.), PY · PeeringDB
58IPv4 routes
96.6% RPKI valid · 41.4% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
2No ROA
34 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
21Route objects not announced
registered with origin AS27768, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS27768, 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.
| 201.217.24.0/23 | No ROA | Nonecovered by 201.217.0.0/19 | 670 100% |
| 201.217.26.0/23 | No ROA | Nonecovered by 201.217.0.0/19 | 670 100% |
| 201.217.0.0/24 | Valid | Nonecovered by 201.217.0.0/21 | 670 100% |
| 201.217.1.0/24 | Valid | Nonecovered by 201.217.0.0/21 | 670 100% |
| 201.217.2.0/24 | Valid | Nonecovered by 201.217.0.0/21 | 670 100% |
| 201.217.3.0/24 | Valid | Nonecovered by 201.217.0.0/21 | 670 100% |
| 201.217.4.0/24 | Valid | Nonecovered by 201.217.0.0/21 | 670 100% |
| 201.217.5.0/24 | Valid | Nonecovered by 201.217.0.0/21 | 670 100% |
| 201.217.9.0/24 | Valid | Nonecovered by 201.217.8.0/22 | 670 100% |
| 201.217.19.0/24 | Valid | Nonecovered by 201.217.16.0/22 | 670 100% |
| 201.217.22.0/24 | Valid | Nonecovered by 201.217.22.0/23 | 670 100% |
| 201.217.23.0/24 | Valid | Nonecovered by 201.217.22.0/23 | 670 100% |
| 201.217.31.0/24 | Valid | Nonecovered by 201.217.30.0/23 | 670 100% |
| 201.217.33.0/24 | Valid | Nonecovered by 201.217.32.0/22 | 670 100% |
| 201.217.34.0/24 | Valid | Nonecovered by 201.217.32.0/22 | 670 100% |
| 201.217.35.0/24 | Valid | Nonecovered by 201.217.32.0/22 | 670 100% |
| 201.217.40.0/24 | Valid | Nonecovered by 201.217.40.0/22 | 670 100% |
| 201.217.41.0/24 | Valid | Nonecovered by 201.217.40.0/22 | 670 100% |
| 201.217.42.0/24 | Valid | Nonecovered by 201.217.40.0/22 | 670 100% |
| 201.217.43.0/24 | Valid | Nonecovered by 201.217.40.0/22 | 670 100% |
| 201.217.52.0/24 | Valid | Nonecovered by 201.217.52.0/23 | 670 100% |
| 216.184.116.0/23 | Valid | Nonecovered by 216.184.116.0/22 | 670 100% |
| 216.184.116.0/24 | Valid | Nonecovered by 216.184.116.0/22 | 670 100% |
| 190.23.0.0/17 | Valid | Nonecovered by 190.23.0.0/16 | 669 99% |
| 190.23.128.0/24 | Valid | Nonecovered by 190.23.0.0/16 | 669 99% |
| 190.23.129.0/24 | Valid | Nonecovered by 190.23.0.0/16 | 669 99% |
| 190.23.130.0/24 | Valid | Nonecovered by 190.23.0.0/16 | 669 99% |
| 190.23.131.0/24 | Valid | Nonecovered by 190.23.0.0/16 | 669 99% |
| 190.23.132.0/24 | Valid | Nonecovered by 190.23.0.0/16 | 669 99% |
| 190.23.133.0/24 | Valid | Nonecovered by 190.23.0.0/16 | 669 99% |
| 190.23.134.0/24 | Valid | Nonecovered by 190.23.0.0/16 | 669 99% |
| 190.23.135.0/24 | Valid | Nonecovered by 190.23.0.0/16 | 669 99% |
| 190.23.254.0/24 | Valid | Nonecovered by 190.23.0.0/16 | 669 99% |
| 190.23.255.0/24 | Valid | Nonecovered by 190.23.0.0/16 | 669 99% |
| 201.217.53.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 216.184.116.0/22 | Valid | Other IRR onlyRADB | 670 100% |
| 177.250.0.0/20 | Valid | RIR databaseLACNIC | 670 100% |
| 177.250.16.0/21 | Valid | RIR databaseLACNIC | 670 100% |
| 177.250.24.0/21 | Valid | RIR databaseLACNIC | 670 100% |
| 177.250.32.0/20 | Valid | RIR databaseLACNIC | 670 100% |
| 177.250.48.0/20 | Valid | RIR databaseLACNIC | 670 100% |
| 177.250.64.0/18 | Valid | RIR databaseLACNIC | 670 100% |
| 177.251.32.0/19 | Valid | RIR databaseLACNIC | 670 100% |
| 177.251.64.0/18 | Valid | RIR databaseLACNIC | 670 100% |
| 177.251.252.0/23 | Valid | RIR databaseLACNIC | 670 100% |
| 177.251.254.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 201.217.13.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 201.217.24.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 201.217.25.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 201.217.26.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 201.217.27.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 201.217.44.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 201.217.47.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 201.217.49.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 201.217.50.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 201.217.59.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 177.251.24.0/21 | Valid | RIR databaseLACNIC | 669 99% |
| 2800:960::/32 | Valid | RIR databaseLACNIC, RADB | 634 100% |
| 177.250.128.0/18 | Valid | RIR databaseLACNIC | 2 0%low visibility |
AS-SET
AS27768'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 59 are in fix.csv.
- ROA: none2
- Route object: none34
- Route object: RIR2
- Route object: not announced21
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 201.217.24.0/23 | No ROA covers it. Add a ROA for AS27768, maxLength 23. |
| Route object: none | 201.217.24.0/23 | No route object for it. A route object for 201.217.0.0/19 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| ROA: none | 201.217.26.0/23 | No ROA covers it. Add a ROA for AS27768, maxLength 23. |
| Route object: none | 201.217.26.0/23 | No route object for it. A route object for 201.217.0.0/19 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.0.0/24 | No route object for it. A route object for 201.217.0.0/21 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.1.0/24 | No route object for it. A route object for 201.217.0.0/21 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.2.0/24 | No route object for it. A route object for 201.217.0.0/21 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.3.0/24 | No route object for it. A route object for 201.217.0.0/21 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.4.0/24 | No route object for it. A route object for 201.217.0.0/21 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.5.0/24 | No route object for it. A route object for 201.217.0.0/21 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.9.0/24 | No route object for it. A route object for 201.217.8.0/22 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.19.0/24 | No route object for it. A route object for 201.217.16.0/22 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.22.0/24 | No route object for it. A route object for 201.217.22.0/23 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.23.0/24 | No route object for it. A route object for 201.217.22.0/23 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.31.0/24 | No route object for it. A route object for 201.217.30.0/23 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.33.0/24 | No route object for it. A route object for 201.217.32.0/22 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.34.0/24 | No route object for it. A route object for 201.217.32.0/22 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.35.0/24 | No route object for it. A route object for 201.217.32.0/22 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.40.0/24 | No route object for it. A route object for 201.217.40.0/22 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.41.0/24 | No route object for it. A route object for 201.217.40.0/22 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.42.0/24 | No route object for it. A route object for 201.217.40.0/22 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.43.0/24 | No route object for it. A route object for 201.217.40.0/22 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 201.217.52.0/24 | No route object for it. A route object for 201.217.52.0/23 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 216.184.116.0/23 | No route object for it. A route object for 216.184.116.0/22 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 216.184.116.0/24 | No route object for it. A route object for 216.184.116.0/22 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 190.23.0.0/17 | No route object for it. A route object for 190.23.0.0/16 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 190.23.128.0/24 | No route object for it. A route object for 190.23.0.0/16 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 190.23.129.0/24 | No route object for it. A route object for 190.23.0.0/16 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 190.23.130.0/24 | No route object for it. A route object for 190.23.0.0/16 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 190.23.131.0/24 | No route object for it. A route object for 190.23.0.0/16 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 190.23.132.0/24 | No route object for it. A route object for 190.23.0.0/16 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 190.23.133.0/24 | No route object for it. A route object for 190.23.0.0/16 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 190.23.134.0/24 | No route object for it. A route object for 190.23.0.0/16 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 190.23.135.0/24 | No route object for it. A route object for 190.23.0.0/16 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 190.23.254.0/24 | No route object for it. A route object for 190.23.0.0/16 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: none | 190.23.255.0/24 | No route object for it. A route object for 190.23.0.0/16 with origin AS27768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27768 in the RIR database for the space. |
| Route object: RIR | 201.217.53.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 216.184.116.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS27768 whose prefix no peer sees AS27768 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 168.90.176.0/22 | RADB | No ROA |
| 177.250.64.0/20 | LACNIC | Valid |
| 190.23.0.0/16 | LACNIC, RADB | Valid |
| 190.112.208.0/22 | RADB | No ROA |
| 200.108.140.0/23 | RADB | No ROA |
| 200.115.17.0/24 | RADB | No ROA |
| 201.217.0.0/18 | RADB | No ROA |
| 201.217.0.0/19 | RADB | No ROA |
| 201.217.0.0/21 | LACNIC | Valid |
| 201.217.8.0/22 | LACNIC | Valid |
| 201.217.16.0/22 | LACNIC | Valid |
| 201.217.21.0/24 | LACNIC | Valid |
| 201.217.22.0/23 | LACNIC | Valid |
| 201.217.29.0/24 | LACNIC | Valid |
| 201.217.30.0/23 | LACNIC | Valid |
| 201.217.32.0/22 | LACNIC | Valid |
| 201.217.40.0/22 | LACNIC, RADB | Valid |
| 201.217.46.0/24 | LACNIC | Valid |
| 201.217.52.0/23 | LACNIC | Valid |
| 2001:500:3::/48 | RADB | No ROA |
| 2001:500:9e::/47 | RADB | No 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.