bgpreport

Network · data from 2026-11-12

AS27680 AS27680 - TELEFONICA MOVIL DE CHILE S.A.

Registry name: AS27680 - TELEFONICA MOVIL DE CHILE S.A., CL · not in PeeringDB

15IPv4 routes 40.0% RPKI valid · 26.7% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
9No ROA 11 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS27680, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS27680, 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.220.224.0/21 No ROA None 671 100% 67
201.220.232.0/24 No ROA None 671 100% 67
201.220.233.0/24 No ROA None 671 100% 67
201.220.241.0/24 No ROA None 671 100% 67
201.220.242.0/24 No ROA None 671 100% 67
201.220.244.0/22 No ROA None 671 100% 67
206.31.176.0/24 No ROA None 671 100% 67
206.31.177.0/24 No ROA None 671 100% 67
201.220.243.0/24 No ROA None 2 0%low visibility 2
190.108.128.0/19 Valid Nonecovered by 190.108.128.0/18 670 100% 67
190.108.160.0/19 Valid Nonecovered by 190.108.128.0/18 670 100% 67
186.40.0.0/16 Valid RIR databaseLACNIC 671 100% 67
190.108.128.0/18 Valid RIR databaseLACNIC 670 100% 67
200.91.1.0/24 Valid RIR databaseLACNIC 670 100% 67
200.54.123.0/24 Valid RIR databaseLACNIC 2 0%low visibility 2

AS-SET

AS27680 isn't in PeeringDB, where networks name their 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 21 are in fix.csv.

  • ROA: none9
  • Route object: none11
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none201.220.224.0/21No ROA covers it. Add a ROA for AS27680, maxLength 21.671 of 673
Route object: none201.220.224.0/21No route object for it. Add a route object with origin AS27680 in the RIR database for the space.671 of 673
ROA: none201.220.232.0/24No ROA covers it. Add a ROA for AS27680, maxLength 24.671 of 673
Route object: none201.220.232.0/24No route object for it. Add a route object with origin AS27680 in the RIR database for the space.671 of 673
ROA: none201.220.233.0/24No ROA covers it. Add a ROA for AS27680, maxLength 24.671 of 673
Route object: none201.220.233.0/24No route object for it. Add a route object with origin AS27680 in the RIR database for the space.671 of 673
ROA: none201.220.241.0/24No ROA covers it. Add a ROA for AS27680, maxLength 24.671 of 673
Route object: none201.220.241.0/24No route object for it. Add a route object with origin AS27680 in the RIR database for the space.671 of 673
ROA: none201.220.242.0/24No ROA covers it. Add a ROA for AS27680, maxLength 24.671 of 673
Route object: none201.220.242.0/24No route object for it. Add a route object with origin AS27680 in the RIR database for the space.671 of 673
ROA: none201.220.244.0/22No ROA covers it. Add a ROA for AS27680, maxLength 22.671 of 673
Route object: none201.220.244.0/22No route object for it. Add a route object with origin AS27680 in the RIR database for the space.671 of 673
ROA: none206.31.176.0/24No ROA covers it. Add a ROA for AS27680, maxLength 24.671 of 673
Route object: none206.31.176.0/24No route object for it. Add a route object with origin AS27680 in the RIR database for the space.671 of 673
ROA: none206.31.177.0/24No ROA covers it. Add a ROA for AS27680, maxLength 24.671 of 673
Route object: none206.31.177.0/24No route object for it. Add a route object with origin AS27680 in the RIR database for the space.671 of 673
ROA: none201.220.243.0/24No ROA covers it. Add a ROA for AS27680, maxLength 24.2 of 673
Route object: none201.220.243.0/24No route object for it. Add a route object with origin AS27680 in the RIR database for the space.2 of 673
Route object: none190.108.128.0/19No route object for it. A route object for 190.108.128.0/18 with origin AS27680 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27680 in the RIR database for the space.670 of 673
Route object: none190.108.160.0/19No route object for it. A route object for 190.108.128.0/18 with origin AS27680 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27680 in the RIR database for the space.670 of 673

Route objects not announced

Route objects with origin AS27680 whose prefix no peer sees AS27680 announce. Many are kept on purpose (backup routes, space announced only in some places).

186.41.0.0/16LACNICValid

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.