Network · data from 2026-11-12
AS7004 CTC Transmisiones Regionales S.A.
Registry name: AS7004 - TELEFONICA CHILE S.A., CL · PeeringDB
43IPv4 routes
88.4% RPKI valid · 37.2% with a route object
6IPv6 routes
0.0% RPKI valid · 0.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
11No ROA
33 with no route object for this origin
7Low visibility
seen by under 10% of full-table peers
10Route objects not announced
registered with origin AS7004, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS7004, 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.
| 45.176.166.0/23 | No ROA | None | 672 100% |
| 200.12.23.0/24 | No ROA | None | 671 100% |
| 200.12.25.0/24 | No ROA | Other origin only | 671 100% |
| 200.12.26.0/24 | No ROA | None | 671 100% |
| 200.12.18.0/24 | No ROA | None | 666 99% |
| 2800:550::/32 | No ROA | None | 636 100% |
| 2800:550:4::/48 | No ROA | None | 636 100% |
| 2800:4d0::/32 | No ROA | None | 635 100% |
| 2800:550:fe::/48 | No ROA | None | 635 100% |
| 2800:550:ff::/48 | No ROA | None | 635 100% |
| 2800:550:ae::/48 | No ROA | None | 634 100% |
| 164.77.28.0/24 | Valid | Other origin onlycovered by 164.77.28.0/23 | 672 100% |
| 186.148.7.0/24 | Valid | Nonecovered by 186.148.0.0/18 | 672 100% |
| 186.148.34.0/24 | Valid | Nonecovered by 186.148.0.0/18 | 672 100% |
| 186.148.40.0/24 | Valid | Nonecovered by 186.148.0.0/18 | 672 100% |
| 186.148.41.0/24 | Valid | Nonecovered by 186.148.0.0/18 | 672 100% |
| 186.148.46.0/24 | Valid | Nonecovered by 186.148.0.0/18 | 672 100% |
| 186.148.38.0/24 | Valid | Nonecovered by 186.148.0.0/18 | 671 100% |
| 200.91.15.0/24 | Valid | Nonecovered by 200.91.0.0/19 | 671 100% |
| 200.91.21.0/24 | Valid | Nonecovered by 200.91.0.0/19 | 671 100% |
| 200.91.27.0/24 | Valid | Nonecovered by 200.91.0.0/19 | 671 100% |
| 200.91.31.0/24 | Valid | Nonecovered by 200.91.0.0/19 | 671 100% |
| 200.91.2.0/24 | Valid | Nonecovered by 200.91.0.0/19 | 666 99% |
| 200.91.8.0/24 | Valid | Nonecovered by 200.91.0.0/19 | 666 99% |
| 200.91.12.0/24 | Valid | Nonecovered by 200.91.0.0/19 | 666 99% |
| 200.91.0.0/24 | Valid | Nonecovered by 200.91.0.0/19 | 125 19% |
| 200.91.13.0/24 | Valid | Nonecovered by 200.91.0.0/19 | 125 19% |
| 164.77.29.0/24 | Valid | Other origin onlycovered by 164.77.28.0/23 | 30 4%low visibility |
| 200.91.10.0/24 | Valid | Nonecovered by 200.91.0.0/19 | 30 4%low visibility |
| 200.91.11.0/24 | Valid | Nonecovered by 200.91.0.0/19 | 30 4%low visibility |
| 200.91.20.0/24 | Valid | Nonecovered by 200.91.0.0/19 | 30 4%low visibility |
| 200.91.22.0/24 | Valid | Nonecovered by 200.91.0.0/19 | 30 4%low visibility |
| 200.91.29.0/24 | Valid | Nonecovered by 200.91.0.0/19 | 30 4%low visibility |
| 186.148.0.0/18 | Valid | RIR databaseLACNIC | 669 99% |
| 200.91.0.0/19 | Valid | RIR databaseLACNIC | 668 99% |
| 164.77.27.0/24 | Valid | RIR databaseLACNIC | 667 99% |
| 186.103.155.0/24 | Valid | RIR databaseLACNIC | 667 99% |
| 186.103.156.0/23 | Valid | RIR databaseLACNIC | 667 99% |
| 186.103.158.0/23 | Valid | RIR databaseLACNIC | 667 99% |
| 190.82.114.0/23 | Valid | RIR databaseLACNIC | 666 99% |
| 200.10.224.0/24 | Valid | RIR databaseLACNIC | 666 99% |
| 200.28.14.0/24 | Valid | RIR databaseLACNIC | 666 99% |
| 200.29.42.0/24 | Valid | RIR databaseLACNIC | 666 99% |
| 200.50.42.0/24 | Valid | RIR databaseLACNIC | 666 99% |
| 200.113.166.0/24 | Valid | RIR databaseLACNIC | 666 99% |
| 200.29.34.0/24 | Valid | RIR databaseLACNIC | 599 89% |
| 200.54.109.0/24 | Valid | RIR databaseLACNIC | 125 19% |
| 200.54.110.0/24 | Valid | RIR databaseLACNIC | 125 19% |
| 186.103.240.0/20 | Valid | RIR databaseLACNIC | 3 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS7004: LACNIC::AS7004:AS-TEFCHILE2. 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 (AS7004 isn't in the set, or no route object for AS7004 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 | AS7004 in it | Not covered |
|---|---|---|---|---|---|
| LACNIC::AS7004:AS-TEFCHILE2 | LACNIC | 75 | 1 | Yes | 11 |
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 54 are in fix.csv.
- ROA: none11
- Route object: none33
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.176.166.0/23 | No ROA covers it. Add a ROA for AS7004, maxLength 23. |
| Route object: none | 45.176.166.0/23 | No route object for it. Add a route object with origin AS7004 in the RIR database for the space. |
| ROA: none | 200.12.23.0/24 | No ROA covers it. Add a ROA for AS7004, maxLength 24. |
| Route object: none | 200.12.23.0/24 | No route object for it. Add a route object with origin AS7004 in the RIR database for the space. |
| ROA: none | 200.12.25.0/24 | No ROA covers it. Add a ROA for AS7004, maxLength 24. |
| Route object: none | 200.12.25.0/24 | Route objects for it name AS27651. Add a route object with origin AS7004 in the RIR database for the space. |
| ROA: none | 200.12.26.0/24 | No ROA covers it. Add a ROA for AS7004, maxLength 24. |
| Route object: none | 200.12.26.0/24 | No route object for it. Add a route object with origin AS7004 in the RIR database for the space. |
| ROA: none | 200.12.18.0/24 | No ROA covers it. Add a ROA for AS7004, maxLength 24. |
| Route object: none | 200.12.18.0/24 | No route object for it. Add a route object with origin AS7004 in the RIR database for the space. |
| ROA: none | 2800:550::/32 | No ROA covers it. Add a ROA for AS7004, maxLength 32. |
| Route object: none | 2800:550::/32 | No route object for it. Add a route object with origin AS7004 in the RIR database for the space. |
| ROA: none | 2800:550:4::/48 | No ROA covers it. Add a ROA for AS7004, maxLength 48. |
| Route object: none | 2800:550:4::/48 | No route object for it. Add a route object with origin AS7004 in the RIR database for the space. |
| ROA: none | 2800:4d0::/32 | No ROA covers it. Add a ROA for AS7004, maxLength 32. |
| Route object: none | 2800:4d0::/32 | No route object for it. Add a route object with origin AS7004 in the RIR database for the space. |
| ROA: none | 2800:550:fe::/48 | No ROA covers it. Add a ROA for AS7004, maxLength 48. |
| Route object: none | 2800:550:fe::/48 | No route object for it. Add a route object with origin AS7004 in the RIR database for the space. |
| ROA: none | 2800:550:ff::/48 | No ROA covers it. Add a ROA for AS7004, maxLength 48. |
| Route object: none | 2800:550:ff::/48 | No route object for it. Add a route object with origin AS7004 in the RIR database for the space. |
| ROA: none | 2800:550:ae::/48 | No ROA covers it. Add a ROA for AS7004, maxLength 48. |
| Route object: none | 2800:550:ae::/48 | No route object for it. Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 164.77.28.0/24 | Route objects for it name AS209242. A route object for 164.77.28.0/23 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 186.148.7.0/24 | No route object for it. A route object for 186.148.0.0/18 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 186.148.34.0/24 | No route object for it. A route object for 186.148.0.0/18 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 186.148.40.0/24 | No route object for it. A route object for 186.148.0.0/18 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 186.148.41.0/24 | No route object for it. A route object for 186.148.0.0/18 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 186.148.46.0/24 | No route object for it. A route object for 186.148.0.0/18 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 186.148.38.0/24 | No route object for it. A route object for 186.148.0.0/18 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 200.91.15.0/24 | No route object for it. A route object for 200.91.0.0/19 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 200.91.21.0/24 | No route object for it. A route object for 200.91.0.0/19 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 200.91.27.0/24 | No route object for it. A route object for 200.91.0.0/19 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 200.91.31.0/24 | No route object for it. A route object for 200.91.0.0/19 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 200.91.2.0/24 | No route object for it. A route object for 200.91.0.0/19 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 200.91.8.0/24 | No route object for it. A route object for 200.91.0.0/19 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 200.91.12.0/24 | No route object for it. A route object for 200.91.0.0/19 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 200.91.0.0/24 | No route object for it. A route object for 200.91.0.0/19 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 200.91.13.0/24 | No route object for it. A route object for 200.91.0.0/19 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 164.77.29.0/24 | Route objects for it name AS209242. A route object for 164.77.28.0/23 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 200.91.10.0/24 | No route object for it. A route object for 200.91.0.0/19 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 200.91.11.0/24 | No route object for it. A route object for 200.91.0.0/19 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 200.91.20.0/24 | No route object for it. A route object for 200.91.0.0/19 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 200.91.22.0/24 | No route object for it. A route object for 200.91.0.0/19 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
| Route object: none | 200.91.29.0/24 | No route object for it. A route object for 200.91.0.0/19 with origin AS7004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7004 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS7004 whose prefix no peer sees AS7004 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 152.156.0.0/16 | LACNIC | Valid |
| 164.77.28.0/23 | LACNIC | Valid |
| 186.8.0.0/17 | LACNIC | Valid |
| 186.8.128.0/18 | LACNIC | Valid |
| 186.8.192.0/19 | LACNIC | Valid |
| 186.8.224.0/20 | LACNIC | Valid |
| 186.8.240.0/21 | LACNIC | Valid |
| 186.8.248.0/22 | LACNIC | Valid |
| 200.28.0.0/20 | LACNIC | Valid |
| 200.58.128.0/19 | 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.