Telefónica Chile IP Ranges
Telefónica Chile is the Chilean arm of the Telefónica group, and AS7418 is the number its Movistar internet service announces from. LACNIC holds the aut-num as a direct allocation registered on 6 March 2000 and last changed on 2 May 2011, under the handle CL-TCSA41-LACNIC for TELEFÓNICA CHILE S.A. at Avenida Providencia in Santiago. The number itself comes out of the 6912-7466 range IANA still lists as assigned by ARIN, from an era before LACNIC existed, and some of the address blocks under it are older still: the inetnum covering 200.29.32.0/19 was created on 10 October 1995. PeeringDB files the same number as Movistar ISP, aka Movistar Chile, with a selective peering policy and the AS-SET AS7418:AS-TEFCHILE.
- Provider
- Telefónica Chile
- Primary ASN
- AS7418
- Category
- ISP
- Headquarters
- Santiago, Chile
- Announced IPv4 prefixes
- 122
- Registry
- LACNIC
Known IP ranges
These prefixes are currently announced to the global routing table by AS7418 (AS7418 - TELEFONICA CHILE S.A.). Prefix sets change over time - use WHOIS Lookup for the authoritative record on any specific address.
191.112.0.0/14
179.8.0.0/15
186.106.0.0/15
181.172.0.0/15
181.160.0.0/15
186.104.0.0/15
181.162.0.0/15
201.188.0.0/15
186.78.0.0/15
191.127.0.0/16
What does a Telefónica Chile IP mean in a privacy test?
An address on AS7418 is a Chilean Movistar line, and the reverse name usually says which kind before any geolocation database does. 186.104.10.20 answers as 186-104-10-20.fo.baf.movistar.cl, 179.8.200.30 as 179-8-200-30.baf.movistar.cl, 191.127.60.70 as 191-127-60-70.bam.movistar.cl, 200.42.189.100 as 200-42-189-100.static.tie.cl, 190.82.0.100 as 190-82-0-100.adsl.tie.cl and 200.90.160.100 as 200-90-160-100.dialup.tie.cl - the address written out with hyphens in front of one of at least six suffixes. These are access pools rather than hosting ranges, so a proxy or exit node found on one of them is somebody reselling a consumer or business line, not a rented server. Location is where to be careful: every LACNIC record behind these blocks states country CL and nothing finer, and not one of them links a geofeed, so a city attached to a Movistar address is a commercial database's estimate rather than the operator's statement.
Where the records for AS7418 live, and who writes them
Telefónica Chile publishes no IP list of its own and no geofeed, so everything checkable sits at LACNIC and it is thinner than the network is. RDAP on 191.112.0.0/14 returns status ALLOCATED and active with the registrant CL-TCSA41-LACNIC, one remark reading Network: 191.112.0.0/14, and no country field at all; the whois form of the same object does state country: CL, and that is the finest location this operator publishes anywhere. Every block checked points all three contact roles at one handle, TCS5, registered as Technical Contact Telefonica Chile in May 2011 and last updated in April 2024, whose published address is a free Gmail account rather than a corporate abuse mailbox. PeeringDB adds a selective policy, the AS-SET AS7418:AS-TEFCHILE and a 5-10Tbps traffic band, but carries no policy URL, no looking glass and no route server, and its prefix figures - 500 IPv4 and 5 IPv6 - are self-declared filter maxima rather than an inventory, which is why the IPv6 one describes a network that does not exist.
The route objects are all second-hand, which matters if you are validating an announcement. Every LACNIC IRR object over this space is registry-generated, reading descr: LACNIC generated route for whichever company holds the block, with a maintainer to match: MNT-CL-TCSA41-LACNIC and MNT-CL-TEEM-LACNIC each cover about fifty of the announced prefixes, MNT-CL-TMCS-LACNIC twenty and MNT-CL-CCST-LACNIC two, so no single maintainer speaks for the space. Each object carries a maxLength 24 remark matching an RPKI ROA that authorises AS7418 with the same max length of 24. Most were written in one bulk pass stamped last-modified 26 April 2025, but that stamp is not universal - the objects over 152.172.0.0/16 read 16 June 2026, 191.125.0.0/16 5 May 2026, 191.126.0.0/16 and 191.127.0.0/16 9 April 2026, the 200.29 /24s 10 November 2025 and 186.41.0.0/18 23 October 2025. Outside LACNIC, other people's registries cover this space twice over: Proxy-registered route object entries under LEVEL3-MNT sit over roughly ninety of the announced prefixes, from 190.20.0.0/16 and 200.28.0.0/16 through to 201.246.192.0/18, created by a transit provider rather than by the address holder; and RADB carries a 200.90.192.0/18 route object under MAINT-AS18678 with origin AS8048 and the description ITX-CUSTOMER-VIGINET, overlapping the 200.90.192.0/20, 200.90.208.0/20 and 200.90.224.0/19 that AS7418 announces. Reverse DNS is delegated to the operator's own servers - NSAUT.TIE.CL on most blocks, plus NS1 and NS2.REDIP.CL and QIP1 and QIP2.REDIP.CL - and LACNIC flags a lot of that delegation broken: NS1.REDIP.CL is marked lame on every one of the twenty-six blocks it is listed on, the largest being 191.112.0.0/14, last answering authoritatively in January 2026; MOISES.CTC.CL, still carrying the pre-Telefónica CTC name, is lame and unreachable on thirteen blocks including a 200.29 reverse zone whose last authoritative answer was in September 2022; and NS.CTCINTERNET.CL, NS3 and NS4.CTCINTERNET.CL and NS2.TERRA.CL are each flagged lame as well.
Eight registrants, six suffixes, one number
On this network the ASN does not identify one company. The inetnums under AS7418 do not even agree on which aut-nums they name: most list 7418 and 16629, a large minority add 15311, a few pair 7418 with 27680, one names only 16629, and around eighteen of the covering blocks carry no aut-num field at all. LACNIC has generated route objects for five origins over this space - 7418, 16629, 15311, 7004 and 27680 - with the AS7004 objects sitting on parts of 200.28.0.0/16 but also on 200.29.34.0/24 and 200.50.32.0/19. The registrant underneath changes as well, and there are eight of them rather than one: 191.112.0.0/14 and the 200.28 space are held by TELEFÓNICA CHILE S.A. under CL-TCSA41-LACNIC, 181.172.0.0/15, 191.124.0.0/14 and 152.174.0.0/16 by TELEFONICA MOVIL DE CHILE S.A. under CL-TMCS-LACNIC, 200.42.176.0/20 and 200.113.96.0/19 by TELEFONICA EMPRESAS CHILE SA under CL-TEEM-LACNIC, and smaller pieces by Telefonica Internet Empresas Adsl (CL-TIEA1-LACNIC), Telefonica Internet Empresas Conmutados (CL-TIEC2-LACNIC), CTC. CORP S.A. (TELEFONICA EMPRESAS) (CL-CCST-LACNIC), ADSL Dinamico (CL-ADDI-LACNIC) and Terra Networks (CL-TENE-LACNIC). It runs the other way too, so an address that is plainly Movistar yet is not on AS7418 is unremarkable: RIPEstat gives AS7004 the same holder string, TELEFONICA CHILE S.A., and PeeringDB files it under the same organisation. The cleanest split is IPv6, because AS7418 announces none - not one of the several hundred IPv6 peers in RIPE RIS sees a prefix from it - while AS7004 and AS16629 both do, so an IPv6 address from this operator will never carry this number.
What separates the products is reverse DNS, and sampling two addresses in each announced prefix turns up six suffixes rather than four: baf.movistar.cl and fo.baf.movistar.cl on fixed lines, bam.movistar.cl on mobile broadband, and static.tie.cl, adsl.tie.cl and dialup.tie.cl on the business and legacy access blocks - those last three under the same tie.cl domain the authoritative reverse server NSAUT.TIE.CL sits under. The tie.cl labels track the registrant loosely at best: 190.82.0.0/18 is registered to Telefonica Empresas yet answers adsl.tie.cl, while 200.90.180.0/22 sits under Telefonica Internet Empresas Conmutados and answers dialup.tie.cl. The baf and bam labels line up with Movistar's Spanish product naming, banda ancha fija and banda ancha movil, but that expansion is a reading of the label rather than anything the registry states, and it is not airtight either: 152.174.0.0/16 is registered to the mobile company yet its addresses answer with the fixed baf name. Whole announced blocks publish no PTR at all - sampled addresses in 190.21.0.0/16, 190.22.0.0/16, 200.29.45.0/24, 200.29.46.0/24 and 200.54.147.0/24 return NXDOMAIN while 190.20.0.0/16 answers normally - so a missing movistar.cl name is not evidence against. And none of it names anybody: the hostnames are generated from the address, so they carry no subscriber, no city and no product tier, the registry stops at the allocation with a corporate registrant and one shared contact handle, and there is no object for a household anywhere beneath it. The single inference these pools do support is direction - they are access ranges handed to customer equipment, so a service answering on one belongs to a subscriber's own device rather than to anything Telefónica Chile hosts.
Related tools
Frequently asked questions
What IP ranges does Telefónica Chile announce on AS7418?
The largest are listed above, running from a single /14 down to a long tail of /24s, and the live count is in the table at the top of this page. There is no operator-published list to compare them against: the checkable artefacts are the LACNIC allocations, route objects that LACNIC generates itself rather than the operator maintaining them, proxy route objects that transit providers filed in the LEVEL3 and RADB registries, and the AS-SET AS7418:AS-TEFCHILE named in PeeringDB. Every one of those prefixes is IPv4; AS7418 announces no IPv6 space at all.
Why does a Movistar Chile IP show up in my privacy or leak test?
Because the request reached the site over a Movistar connection with nothing tunnelling it. Chilean subscribers see AS7418 as their normal result; if it appears while a VPN is running, the tunnel is not carrying that traffic. The same holds in a DNS leak test, where a resolver on AS7418 means the queries went to Telefónica Chile rather than through the VPN.
What do baf, bam, static.tie.cl and the other suffixes mean in a Movistar hostname?
They are the suffixes Telefónica Chile puts on reverse DNS, with the address itself written out in hyphens in front of them. Sampling the announced space turns up six: baf and fo.baf on fixed lines, bam on mobile broadband, and static.tie.cl, adsl.tie.cl and dialup.tie.cl on business and legacy access blocks. The baf and bam labels match Movistar's own Spanish product naming for fixed and mobile broadband, but that reading is not published in the registry, and the labels do not track the registrant reliably: 152.174.0.0/16 is registered to the mobile company while answering with the fixed name.
How do I check whether an address really belongs to AS7418?
Query the address rather than trusting a list. A WHOIS or RDAP lookup at LACNIC returns the inetnum, its registrant handle and the aut-nums it is tied to, and a reverse DNS lookup returns the movistar.cl or tie.cl suffix if the block publishes one. MyIPScan's WHOIS Lookup and IP Geolocation Lookup do both from the browser, and the ASN Lookup tool resolves AS7418 itself. Check the origin ASN in the routing table too, since Telefónica Chile also announces from AS7004 and AS16629.
What does an AS7418 match not prove?
It does not prove a location beyond the country. Every LACNIC record behind this space states country CL and nothing finer, and none of them links a geofeed, so a city shown for a Movistar address comes from a commercial database rather than from Telefónica. It does not prove which company holds the block, because at least eight separate LACNIC registrants - the fixed, mobile, business, ADSL, dial-up and Terra Networks entities among them - hold space announced under this one origin. And it does not identify a subscriber: the registry stops at the allocation, and the reverse names are generated from the address.