Network · data from 2026-11-12
AS27866 Compañía Paraguaya de Comunicaciones S.A. - 2
Registry name: AS27866 - COMPANIA PARAGUAYA DE COMUNICACIONES S.A. (COPACO S.A.), PY · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS27866, 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.23.0.0/16 | Invalid: origin | Other origin only | 1 0%low visibility |
| 201.217.36.0/24 | Valid | Nonecovered by 201.217.36.0/22 | 670 100% |
| 201.217.37.0/24 | Valid | Nonecovered by 201.217.36.0/22 | 670 100% |
| 201.217.38.0/24 | Valid | Nonecovered by 201.217.36.0/22 | 670 100% |
| 201.217.39.0/24 | Valid | Nonecovered by 201.217.36.0/22 | 670 100% |
| 201.217.54.0/24 | Valid | Nonecovered by 201.217.54.0/23 | 670 100% |
| 201.217.55.0/24 | Valid | Nonecovered by 201.217.54.0/23 | 670 100% |
| 201.217.56.0/24 | Valid | Nonecovered by 201.217.56.0/23 | 670 100% |
| 201.217.57.0/24 | Valid | Nonecovered by 201.217.56.0/23 | 670 100% |
| 201.217.60.0/24 | Valid | Nonecovered by 201.217.60.0/23 | 670 100% |
| 201.217.61.0/24 | Valid | Nonecovered by 201.217.60.0/23 | 670 100% |
| 177.250.252.0/22 | Valid | RIR databaseLACNIC | 670 100% |
| 201.217.12.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 201.217.28.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 201.217.48.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 201.217.51.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 190.52.128.0/18 | Valid | RIR databaseLACNIC | 669 99% |
AS-SET
AS27866'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 44 are in fix.csv.
- ROA: origin1
- Route object: none11
- Route object: not announced32
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 190.23.0.0/16 | ROAs covering it name AS27768, not AS27866. If AS27866 should announce it, add a ROA for AS27866. |
| Route object: none | 190.23.0.0/16 | Route objects for it name AS27768. Add a route object with origin AS27866 in the RIR database for the space. |
| Route object: none | 201.217.36.0/24 | No route object for it. A route object for 201.217.36.0/22 with origin AS27866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27866 in the RIR database for the space. |
| Route object: none | 201.217.37.0/24 | No route object for it. A route object for 201.217.36.0/22 with origin AS27866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27866 in the RIR database for the space. |
| Route object: none | 201.217.38.0/24 | No route object for it. A route object for 201.217.36.0/22 with origin AS27866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27866 in the RIR database for the space. |
| Route object: none | 201.217.39.0/24 | No route object for it. A route object for 201.217.36.0/22 with origin AS27866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27866 in the RIR database for the space. |
| Route object: none | 201.217.54.0/24 | No route object for it. A route object for 201.217.54.0/23 with origin AS27866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27866 in the RIR database for the space. |
| Route object: none | 201.217.55.0/24 | No route object for it. A route object for 201.217.54.0/23 with origin AS27866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27866 in the RIR database for the space. |
| Route object: none | 201.217.56.0/24 | No route object for it. A route object for 201.217.56.0/23 with origin AS27866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27866 in the RIR database for the space. |
| Route object: none | 201.217.57.0/24 | No route object for it. A route object for 201.217.56.0/23 with origin AS27866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27866 in the RIR database for the space. |
| Route object: none | 201.217.60.0/24 | No route object for it. A route object for 201.217.60.0/23 with origin AS27866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27866 in the RIR database for the space. |
| Route object: none | 201.217.61.0/24 | No route object for it. A route object for 201.217.60.0/23 with origin AS27866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27866 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS27866 whose prefix no peer sees AS27866 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.250.0.0/15 | RADB | No ROA |
| 177.250.192.0/21 | RADB | No ROA |
| 177.250.200.0/21 | RADB | No ROA |
| 177.250.208.0/21 | RADB | No ROA |
| 177.250.216.0/21 | RADB | No ROA |
| 177.250.224.0/21 | RADB | No ROA |
| 177.250.232.0/21 | RADB | No ROA |
| 177.250.240.0/21 | RADB | No ROA |
| 177.250.248.0/21 | RADB | No ROA |
| 177.251.0.0/21 | RADB | No ROA |
| 177.251.8.0/21 | RADB | No ROA |
| 177.251.16.0/21 | RADB | No ROA |
| 177.251.128.0/21 | RADB | No ROA |
| 177.251.136.0/21 | RADB | No ROA |
| 177.251.144.0/21 | RADB | No ROA |
| 177.251.152.0/21 | RADB | No ROA |
| 177.251.160.0/21 | RADB | No ROA |
| 177.251.168.0/21 | RADB | No ROA |
| 177.251.176.0/21 | RADB | No ROA |
| 177.251.184.0/21 | RADB | No ROA |
| 177.251.192.0/21 | RADB | No ROA |
| 177.251.200.0/21 | RADB | No ROA |
| 177.251.208.0/21 | RADB | No ROA |
| 177.251.216.0/21 | RADB | No ROA |
| 177.251.224.0/21 | RADB | No ROA |
| 177.251.232.0/21 | RADB | No ROA |
| 177.251.240.0/21 | RADB | No ROA |
| 177.251.248.0/21 | RADB | No ROA |
| 201.217.36.0/22 | LACNIC | Valid |
| 201.217.54.0/23 | LACNIC | Valid |
| 201.217.56.0/23 | LACNIC | Valid |
| 201.217.60.0/23 | LACNIC | Valid |
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.