Network · data from 2026-11-12
AS15311 Telefonica Empresas Network
Registry name: AS15311 - TELEFONICA EMPRESAS CHILE SA, CL · PeeringDB
54IPv4 routes
74.1% RPKI valid · 42.6% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
14No ROA
31 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
9Route objects not announced
registered with origin AS15311, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS15311, 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.236.20.0/22 | No ROA | None | 672 100% |
| 201.236.24.0/24 | No ROA | None | 672 100% |
| 201.236.28.0/22 | No ROA | None | 672 100% |
| 201.236.28.0/24 | No ROA | None | 672 100% |
| 201.236.52.0/22 | No ROA | None | 672 100% |
| 201.236.64.0/19 | No ROA | None | 672 100% |
| 201.236.96.0/20 | No ROA | None | 672 100% |
| 200.42.172.0/22 | No ROA | None | 671 100% |
| 200.42.190.0/23 | No ROA | None | 671 100% |
| 200.50.96.0/22 | No ROA | None | 671 100% |
| 200.50.108.0/22 | No ROA | None | 671 100% |
| 200.50.124.0/22 | No ROA | None | 671 100% |
| 201.236.24.0/22 | No ROA | None | 671 100% |
| 200.42.176.0/22 | No ROA | None | 666 99% |
| 186.103.160.0/24 | Valid | Nonecovered by 186.103.128.0/17 | 672 100% |
| 190.82.96.0/20 | Valid | Nonecovered by 190.82.64.0/18 | 671 100% |
| 190.82.112.0/20 | Valid | Nonecovered by 190.82.64.0/18 | 671 100% |
| 190.82.112.0/23 | Valid | Nonecovered by 190.82.64.0/18 | 671 100% |
| 190.82.116.0/22 | Valid | Nonecovered by 190.82.64.0/18 | 671 100% |
| 200.90.176.0/23 | Valid | Nonecovered by 200.90.176.0/20 | 671 100% |
| 200.90.179.0/24 | Valid | Nonecovered by 200.90.176.0/20 | 671 100% |
| 200.90.188.0/24 | Valid | Nonecovered by 200.90.176.0/20 | 671 100% |
| 200.90.190.0/24 | Valid | Nonecovered by 200.90.176.0/20 | 671 100% |
| 200.113.0.0/21 | Valid | Nonecovered by 200.113.0.0/20 | 671 100% |
| 200.113.8.0/21 | Valid | Nonecovered by 200.113.0.0/20 | 671 100% |
| 200.113.16.0/21 | Valid | Nonecovered by 200.113.16.0/20 | 671 100% |
| 200.113.96.0/20 | Valid | Nonecovered by 200.113.96.0/19 | 671 100% |
| 200.113.112.0/20 | Valid | Nonecovered by 200.113.96.0/19 | 671 100% |
| 200.113.144.0/20 | Valid | Nonecovered by 200.113.128.0/19 | 671 100% |
| 200.113.160.0/20 | Valid | Nonecovered by 200.113.160.0/19 | 671 100% |
| 200.113.176.0/20 | Valid | Nonecovered by 200.113.160.0/19 | 671 100% |
| 186.103.128.0/17 | Valid | RIR databaseLACNIC | 672 100% |
| 186.179.80.0/20 | Valid | RIR databaseLACNIC | 672 100% |
| 190.82.64.0/18 | Valid | RIR databaseLACNIC | 671 100% |
| 200.54.144.0/23 | Valid | RIR databaseLACNIC | 671 100% |
| 200.54.146.0/24 | Valid | RIR databaseLACNIC | 671 100% |
| 200.54.153.0/24 | Valid | RIR databaseLACNIC | 671 100% |
| 200.54.154.0/23 | Valid | RIR databaseLACNIC | 671 100% |
| 200.54.156.0/22 | Valid | RIR databaseLACNIC | 671 100% |
| 200.54.160.0/20 | Valid | RIR databaseLACNIC | 671 100% |
| 200.54.176.0/22 | Valid | RIR databaseLACNIC | 671 100% |
| 200.54.181.0/24 | Valid | RIR databaseLACNIC | 671 100% |
| 200.54.182.0/23 | Valid | RIR databaseLACNIC | 671 100% |
| 200.54.184.0/22 | Valid | RIR databaseLACNIC | 671 100% |
| 200.54.188.0/24 | Valid | RIR databaseLACNIC | 671 100% |
| 200.54.193.0/24 | Valid | RIR databaseLACNIC | 671 100% |
| 200.54.194.0/24 | Valid | RIR databaseLACNIC | 671 100% |
| 200.54.196.0/23 | Valid | RIR databaseLACNIC | 671 100% |
| 200.54.199.0/24 | Valid | RIR databaseLACNIC | 671 100% |
| 200.68.1.0/24 | Valid | RIR databaseLACNIC | 671 100% |
| 201.236.128.0/18 | Valid | RIR databaseLACNIC | 669 99% |
| 200.113.32.0/20 | Valid | RIR databaseLACNIC | 668 99% |
| 200.113.48.0/20 | Valid | RIR databaseLACNIC | 668 99% |
| 200.113.80.0/20 | Valid | RIR databaseLACNIC | 668 99% |
AS-SET
AS15311'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 54 are in fix.csv.
- ROA: none14
- Route object: none31
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 201.236.20.0/22 | No ROA covers it. Add a ROA for AS15311, maxLength 22. |
| Route object: none | 201.236.20.0/22 | No route object for it. Add a route object with origin AS15311 in the RIR database for the space. |
| ROA: none | 201.236.24.0/24 | No ROA covers it. Add a ROA for AS15311, maxLength 24. |
| Route object: none | 201.236.24.0/24 | No route object for it. Add a route object with origin AS15311 in the RIR database for the space. |
| ROA: none | 201.236.28.0/22 | No ROA covers it. Add a ROA for AS15311, maxLength 22. |
| Route object: none | 201.236.28.0/22 | No route object for it. Add a route object with origin AS15311 in the RIR database for the space. |
| ROA: none | 201.236.28.0/24 | No ROA covers it. Add a ROA for AS15311, maxLength 24. |
| Route object: none | 201.236.28.0/24 | No route object for it. Add a route object with origin AS15311 in the RIR database for the space. |
| ROA: none | 201.236.52.0/22 | No ROA covers it. Add a ROA for AS15311, maxLength 22. |
| Route object: none | 201.236.52.0/22 | No route object for it. Add a route object with origin AS15311 in the RIR database for the space. |
| ROA: none | 201.236.64.0/19 | No ROA covers it. Add a ROA for AS15311, maxLength 19. |
| Route object: none | 201.236.64.0/19 | No route object for it. Add a route object with origin AS15311 in the RIR database for the space. |
| ROA: none | 201.236.96.0/20 | No ROA covers it. Add a ROA for AS15311, maxLength 20. |
| Route object: none | 201.236.96.0/20 | No route object for it. Add a route object with origin AS15311 in the RIR database for the space. |
| ROA: none | 200.42.172.0/22 | No ROA covers it. Add a ROA for AS15311, maxLength 22. |
| Route object: none | 200.42.172.0/22 | No route object for it. Add a route object with origin AS15311 in the RIR database for the space. |
| ROA: none | 200.42.190.0/23 | No ROA covers it. Add a ROA for AS15311, maxLength 23. |
| Route object: none | 200.42.190.0/23 | No route object for it. Add a route object with origin AS15311 in the RIR database for the space. |
| ROA: none | 200.50.96.0/22 | No ROA covers it. Add a ROA for AS15311, maxLength 22. |
| Route object: none | 200.50.96.0/22 | No route object for it. Add a route object with origin AS15311 in the RIR database for the space. |
| ROA: none | 200.50.108.0/22 | No ROA covers it. Add a ROA for AS15311, maxLength 22. |
| Route object: none | 200.50.108.0/22 | No route object for it. Add a route object with origin AS15311 in the RIR database for the space. |
| ROA: none | 200.50.124.0/22 | No ROA covers it. Add a ROA for AS15311, maxLength 22. |
| Route object: none | 200.50.124.0/22 | No route object for it. Add a route object with origin AS15311 in the RIR database for the space. |
| ROA: none | 201.236.24.0/22 | No ROA covers it. Add a ROA for AS15311, maxLength 22. |
| Route object: none | 201.236.24.0/22 | No route object for it. Add a route object with origin AS15311 in the RIR database for the space. |
| ROA: none | 200.42.176.0/22 | No ROA covers it. Add a ROA for AS15311, maxLength 22. |
| Route object: none | 200.42.176.0/22 | No route object for it. Add a route object with origin AS15311 in the RIR database for the space. |
| Route object: none | 186.103.160.0/24 | No route object for it. A route object for 186.103.128.0/17 with origin AS15311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15311 in the RIR database for the space. |
| Route object: none | 190.82.96.0/20 | No route object for it. A route object for 190.82.64.0/18 with origin AS15311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15311 in the RIR database for the space. |
| Route object: none | 190.82.112.0/20 | No route object for it. A route object for 190.82.64.0/18 with origin AS15311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15311 in the RIR database for the space. |
| Route object: none | 190.82.112.0/23 | No route object for it. A route object for 190.82.64.0/18 with origin AS15311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15311 in the RIR database for the space. |
| Route object: none | 190.82.116.0/22 | No route object for it. A route object for 190.82.64.0/18 with origin AS15311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15311 in the RIR database for the space. |
| Route object: none | 200.90.176.0/23 | No route object for it. A route object for 200.90.176.0/20 with origin AS15311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15311 in the RIR database for the space. |
| Route object: none | 200.90.179.0/24 | No route object for it. A route object for 200.90.176.0/20 with origin AS15311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15311 in the RIR database for the space. |
| Route object: none | 200.90.188.0/24 | No route object for it. A route object for 200.90.176.0/20 with origin AS15311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15311 in the RIR database for the space. |
| Route object: none | 200.90.190.0/24 | No route object for it. A route object for 200.90.176.0/20 with origin AS15311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15311 in the RIR database for the space. |
| Route object: none | 200.113.0.0/21 | No route object for it. A route object for 200.113.0.0/20 with origin AS15311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15311 in the RIR database for the space. |
| Route object: none | 200.113.8.0/21 | No route object for it. A route object for 200.113.0.0/20 with origin AS15311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15311 in the RIR database for the space. |
| Route object: none | 200.113.16.0/21 | No route object for it. A route object for 200.113.16.0/20 with origin AS15311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15311 in the RIR database for the space. |
| Route object: none | 200.113.96.0/20 | No route object for it. A route object for 200.113.96.0/19 with origin AS15311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15311 in the RIR database for the space. |
| Route object: none | 200.113.112.0/20 | No route object for it. A route object for 200.113.96.0/19 with origin AS15311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15311 in the RIR database for the space. |
| Route object: none | 200.113.144.0/20 | No route object for it. A route object for 200.113.128.0/19 with origin AS15311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15311 in the RIR database for the space. |
| Route object: none | 200.113.160.0/20 | No route object for it. A route object for 200.113.160.0/19 with origin AS15311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15311 in the RIR database for the space. |
| Route object: none | 200.113.176.0/20 | No route object for it. A route object for 200.113.160.0/19 with origin AS15311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15311 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS15311 whose prefix no peer sees AS15311 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.68.58.0/24 | LACNIC | Valid |
| 200.90.160.0/20 | LACNIC | Valid |
| 200.90.176.0/20 | LACNIC | Valid |
| 200.113.0.0/20 | LACNIC | Valid |
| 200.113.16.0/20 | LACNIC | Valid |
| 200.113.64.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 |
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.