Network · data from 2026-11-12
AS16629 CTCCORP
Registry name: AS16629 - CTC. CORP S.A. (TELEFONICA EMPRESAS), CL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS16629, 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.
| 200.0.116.0/24 | No ROA | None | 671 100% |
| 200.14.96.0/23 | No ROA | None | 671 100% |
| 201.236.168.0/21 | Valid | Nonecovered by 201.236.128.0/18 | 672 100% |
| 201.236.176.0/21 | Valid | Nonecovered by 201.236.128.0/18 | 672 100% |
| 190.171.138.0/24 | Valid | Nonecovered by 190.171.128.0/18 | 671 100% |
| 190.171.188.0/24 | Valid | Nonecovered by 190.171.128.0/18 | 671 100% |
| 200.54.96.0/24 | Valid | Nonecovered by 200.54.0.0/16 | 671 100% |
| 200.54.215.0/24 | Valid | Nonecovered by 200.54.0.0/16 | 671 100% |
| 200.113.4.0/22 | Valid | Nonecovered by 200.113.0.0/20 | 671 100% |
| 200.113.48.0/22 | Valid | Nonecovered by 200.113.48.0/20 | 671 100% |
| 200.113.60.0/22 | Valid | Nonecovered by 200.113.48.0/20 | 671 100% |
| 2800:4e0:c000::/34 | Valid | Nonecovered by 2800:4e0::/32 | 635 100% |
| 2800:4e0:c006::/48 | Valid | Nonecovered by 2800:4e0::/32 | 634 100% |
| 2800:4e0:c007::/48 | Valid | Nonecovered by 2800:4e0::/32 | 634 100% |
| 2800:4e0:c00b::/48 | Valid | Nonecovered by 2800:4e0::/32 | 23 4%low visibility |
| 152.172.64.0/19 | Valid | Nonecovered by 152.172.0.0/16 | 11 2%low visibility |
| 152.172.96.0/19 | Valid | Nonecovered by 152.172.0.0/16 | 11 2%low visibility |
| 152.172.128.0/19 | Valid | Nonecovered by 152.172.0.0/16 | 11 2%low visibility |
| 152.172.192.0/19 | Valid | Nonecovered by 152.172.0.0/16 | 11 2%low visibility |
| 152.172.224.0/19 | Valid | Nonecovered by 152.172.0.0/16 | 11 2%low visibility |
| 152.173.0.0/19 | Valid | Nonecovered by 152.173.0.0/16 | 11 2%low visibility |
| 152.173.128.0/19 | Valid | Nonecovered by 152.173.0.0/16 | 11 2%low visibility |
| 152.173.192.0/19 | Valid | Nonecovered by 152.173.0.0/16 | 11 2%low visibility |
| 152.174.0.0/19 | Valid | Nonecovered by 152.174.0.0/16 | 11 2%low visibility |
| 152.174.192.0/19 | Valid | Nonecovered by 152.174.0.0/16 | 11 2%low visibility |
| 190.82.224.0/21 | Valid | Nonecovered by 190.82.128.0/17 | 11 2%low visibility |
| 179.8.96.0/19 | Valid | Nonecovered by 179.8.0.0/15 | 2 0%low visibility |
| 201.246.64.0/19 | Valid | Nonecovered by 201.246.64.0/18 | 2 0%low visibility |
| 201.246.96.0/19 | Valid | Nonecovered by 201.246.64.0/18 | 2 0%low visibility |
| 170.84.208.0/22 | Valid | RIR databaseLACNIC | 672 100% |
| 181.212.0.0/16 | Valid | RIR databaseLACNIC | 672 100% |
| 190.4.192.0/19 | Valid | RIR databaseLACNIC | 671 100% |
| 200.68.0.0/18 | Valid | RIR databaseLACNIC | 671 100% |
| 190.171.128.0/18 | Valid | RIR databaseLACNIC | 670 100% |
| 200.54.0.0/16 | Valid | RIR databaseLACNIC | 670 100% |
| 186.40.128.0/17 | Valid | RIR databaseLACNIC | 669 99% |
| 2800:590:1000::/36 | Valid | RIR databaseLACNIC | 635 100% |
| 2800:590:2000::/36 | Valid | RIR databaseLACNIC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS16629: AS16629:AS-TEFCHILE3. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS16629 isn't in the set, or no route object for AS16629 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS16629 in it | Not covered |
|---|---|---|---|---|---|
| AS16629:AS-TEFCHILE3 | LACNIC | 30 | 1 | No | 38 |
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 102 are in fix.csv.
- ROA: none2
- Route object: none29
- AS-SET: own ASN1
- Route object: not announced70
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 200.0.116.0/24 | No ROA covers it. Add a ROA for AS16629, maxLength 24. |
| Route object: none | 200.0.116.0/24 | No route object for it. Add a route object with origin AS16629 in the RIR database for the space. |
| ROA: none | 200.14.96.0/23 | No ROA covers it. Add a ROA for AS16629, maxLength 23. |
| Route object: none | 200.14.96.0/23 | No route object for it. Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 201.236.168.0/21 | No route object for it. A route object for 201.236.128.0/18 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 201.236.176.0/21 | No route object for it. A route object for 201.236.128.0/18 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 190.171.138.0/24 | No route object for it. A route object for 190.171.128.0/18 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 190.171.188.0/24 | No route object for it. A route object for 190.171.128.0/18 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 200.54.96.0/24 | No route object for it. A route object for 200.54.0.0/16 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 200.54.215.0/24 | No route object for it. A route object for 200.54.0.0/16 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 200.113.4.0/22 | No route object for it. A route object for 200.113.0.0/20 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 200.113.48.0/22 | No route object for it. A route object for 200.113.48.0/20 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 200.113.60.0/22 | No route object for it. A route object for 200.113.48.0/20 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 2800:4e0:c000::/34 | No route object for it. A route object for 2800:4e0::/32 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 2800:4e0:c006::/48 | No route object for it. A route object for 2800:4e0::/32 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 2800:4e0:c007::/48 | No route object for it. A route object for 2800:4e0::/32 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 2800:4e0:c00b::/48 | No route object for it. A route object for 2800:4e0::/32 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 152.172.64.0/19 | No route object for it. A route object for 152.172.0.0/16 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 152.172.96.0/19 | No route object for it. A route object for 152.172.0.0/16 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 152.172.128.0/19 | No route object for it. A route object for 152.172.0.0/16 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 152.172.192.0/19 | No route object for it. A route object for 152.172.0.0/16 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 152.172.224.0/19 | No route object for it. A route object for 152.172.0.0/16 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 152.173.0.0/19 | No route object for it. A route object for 152.173.0.0/16 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 152.173.128.0/19 | No route object for it. A route object for 152.173.0.0/16 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 152.173.192.0/19 | No route object for it. A route object for 152.173.0.0/16 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 152.174.0.0/19 | No route object for it. A route object for 152.174.0.0/16 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 152.174.192.0/19 | No route object for it. A route object for 152.174.0.0/16 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 190.82.224.0/21 | No route object for it. A route object for 190.82.128.0/17 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 179.8.96.0/19 | No route object for it. A route object for 179.8.0.0/15 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 201.246.64.0/19 | No route object for it. A route object for 201.246.64.0/18 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| Route object: none | 201.246.96.0/19 | No route object for it. A route object for 201.246.64.0/18 with origin AS16629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16629 in the RIR database for the space. |
| AS-SET: own ASN | AS16629:AS-TEFCHILE3 | AS16629 isn't in AS16629:AS-TEFCHILE3 (LACNIC) once expanded. Add AS16629 to it. |
Route objects not announced
Route objects with origin AS16629 whose prefix no peer sees AS16629 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.162.184.0/22 | LACNIC | Valid |
| 152.172.0.0/15 | LACNIC | Valid |
| 152.172.0.0/16 | LACNIC | Valid |
| 152.173.0.0/16 | LACNIC | Valid |
| 152.174.0.0/16 | LACNIC | Valid |
| 179.8.0.0/15 | LACNIC | Valid |
| 181.160.0.0/15 | LACNIC | Valid |
| 181.162.0.0/15 | LACNIC | Valid |
| 181.172.0.0/15 | LACNIC | Valid |
| 186.78.0.0/15 | LACNIC | Valid |
| 186.104.0.0/15 | LACNIC | Valid |
| 186.106.0.0/15 | LACNIC | Valid |
| 190.20.0.0/16 | LACNIC | Valid |
| 190.21.0.0/16 | LACNIC | Valid |
| 190.22.0.0/16 | LACNIC | Valid |
| 190.82.0.0/18 | LACNIC | Valid |
| 190.82.128.0/17 | LACNIC | Valid |
| 191.112.0.0/14 | LACNIC | Valid |
| 191.125.0.0/16 | LACNIC | Valid |
| 191.126.0.0/15 | LACNIC | Valid |
| 191.126.0.0/16 | LACNIC | Valid |
| 191.127.0.0/16 | LACNIC | Valid |
| 200.10.225.0/24 | LACNIC | Valid |
| 200.10.226.0/24 | LACNIC | Valid |
| 200.28.0.0/16 | LACNIC | Valid |
| 200.28.186.0/24 | LACNIC | Valid |
| 200.29.32.0/19 | LACNIC | Valid |
| 200.29.48.0/20 | LACNIC | Valid |
| 200.42.160.0/21 | LACNIC | Valid |
| 200.42.168.0/22 | LACNIC | Valid |
| 200.42.180.0/22 | LACNIC | Valid |
| 200.42.184.0/22 | LACNIC | Valid |
| 200.42.189.0/24 | LACNIC | Valid |
| 200.50.32.0/19 | LACNIC | Valid |
| 200.50.100.0/22 | LACNIC | Valid |
| 200.50.104.0/22 | LACNIC | Valid |
| 200.50.112.0/21 | LACNIC | Valid |
| 200.50.120.0/22 | LACNIC | Valid |
| 200.54.128.0/20 | LACNIC | Valid |
| 200.54.147.0/24 | LACNIC | Valid |
| 200.89.32.0/19 | LACNIC | Valid |
| 200.90.160.0/20 | LACNIC | Valid |
| 200.90.176.0/20 | LACNIC | Valid |
| 200.90.192.0/20 | LACNIC | Valid |
| 200.90.208.0/20 | LACNIC | Valid |
| 200.90.224.0/19 | LACNIC | Valid |
| 200.112.0.0/19 | LACNIC | Valid |
| 200.112.32.0/19 | LACNIC | Valid |
| 200.112.64.0/18 | LACNIC | Valid |
| 200.113.0.0/20 | LACNIC | Valid |
| 200.113.16.0/20 | LACNIC | Valid |
| 200.113.32.0/20 | LACNIC | Valid |
| 200.113.48.0/20 | LACNIC | Valid |
| 200.113.64.0/20 | LACNIC | Valid |
| 200.113.80.0/20 | LACNIC | Valid |
| 200.113.96.0/19 | LACNIC | Valid |
| 200.113.128.0/19 | LACNIC | Valid |
| 200.113.160.0/19 | LACNIC | Valid |
| 201.188.0.0/15 | LACNIC | Valid |
| 201.222.128.0/18 | LACNIC | Valid |
| 201.222.192.0/18 | LACNIC | Valid |
| 201.223.0.0/17 | LACNIC | Valid |
| 201.223.128.0/17 | LACNIC | Valid |
| 201.236.128.0/18 | LACNIC | Valid |
| 201.246.0.0/18 | LACNIC | Valid |
| 201.246.64.0/18 | LACNIC | Valid |
| 201.246.128.0/18 | LACNIC | Valid |
| 201.246.192.0/18 | LACNIC | Valid |
| 2800:4e0::/32 | LACNIC | Valid |
| 2803:49a0::/32 | 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.