Vivo (Telefonica Brasil) IP Ranges
Vivo is the consumer brand of Telefonica Brasil, and AS27699 is the number its fixed broadband runs on. The record is held at registro.br, which serves LACNIC for Brazilian resources: a direct allocation registered on 25 August 2003 to TELEFONICA BRASIL S.A under CNPJ 02.558.157/0001-62, with the administrative handle ARITE, which expands to Administracao Rede IP Telesp, and a separate technical handle TEBSA15 answering at roteamento.br at telefonica.com. PeeringDB files the same number as TELEFONICA BRASIL AS27699, aka Vivo, with an open policy and the AS-TBSA macro.
- Provider
- Vivo (Telefonica Brasil)
- Primary ASN
- AS27699
- Category
- ISP
- Headquarters
- Sao Paulo, Brazil
- Announced IPv4 prefixes
- 139
- Registry
- LACNIC
Known IP ranges
These prefixes are currently announced to the global routing table by AS27699 (AS27699 - TELEFONICA BRASIL S.A). Prefix sets change over time - use WHOIS Lookup for the authoritative record on any specific address.
189.46.0.0/15
177.138.0.0/15
177.102.0.0/15
189.110.0.0/15
187.10.0.0/15
201.42.0.0/15
201.92.0.0/15
189.68.0.0/15
189.78.0.0/15
179.110.0.0/15
2804:431:8800::/37
2804:431:9000::/37
2804:431:a800::/37 (IPv6)
What does a Vivo (Telefonica Brasil) IP mean in a privacy test?
An address on AS27699 is a Brazilian fixed line, and the reverse name says so before any database does: 189.46.10.20 answers as 189-46-10-20.dsl.telesp.net.br, and the pools in 177.102, 179.110 and 201.42 space follow the same form. That is an access pool rather than a hosting range, so a proxy or exit node found on one of these blocks is somebody reselling a home connection, not a rented server. Location is where care is needed: the registro.br object for 189.46.0.0/15 records country BR and nothing finer, links no geofeed, and covers a network with a national footprint, so a city attached to a Vivo address is a database's guess and not the operator's statement. And because the same PeeringDB organisation runs eight other ASNs, an address that is obviously Vivo yet is not on AS27699 is unremarkable.
Where Vivo's routing records are kept, and by whom
Telefonica Brasil publishes no geofeed and no peering policy page - the PeeringDB entry has an empty policy URL, an empty looking glass, an open general policy and AS-TBSA as its IRR macro. The address records live at registro.br: RDAP on 189.46.0.0/15 returns status ALLOCATED and active, country BR, autnum 27699, registered on 22 June 2007, with TELEFONICA BRASIL S.A as registrant, ARITE as administrative and technical contact and CSIRT TELEFONICA BR in the abuse role. The only other thing it links is reverse DNS: the zones 46.189.in-addr.arpa and 47.189.in-addr.arpa, delegated to four nameservers under the retail brand - orion, lynx, hercules and aquarius.vivo.com.br - even though the names those servers hand back end in telesp.net.br.
The route objects are scattered, which matters if you are validating an announcement. 177.102.0.0/15 with origin: AS27699 is registered in RADB under the maintainer MAINT-AS10429 - the handle of a different Telefonica Brasil ASN - carrying the description TELEFONICA BRASIL S/A. 189.46.0.0/15 with the same origin appears instead in Level 3's routing registry under LEVEL3-MNT, and its description says outright what it is: Proxy-registered route object, created by the transit provider rather than by the address holder. Neither object is maintained under a handle tied to AS27699 itself, so an IRR check against a single database will find part of this space and miss the rest.
Nine numbers, one macro, one reverse zone
Start by accepting that the ASN is not the unit of identity here. A single PeeringDB organisation covers AS10429, AS11419, AS16885, AS16911, AS18881, AS19182, AS22092 and AS26599 alongside AS27699, and seven of those records - this one included - publish the same AS-TBSA macro, so the AS-SET cannot separate them either. The reverse zone can: dsl.telesp.net.br is applied uniformly across the fixed-access pools, with the dotted quad rewritten with hyphens, as in 189-46-10-20.dsl.telesp.net.br.
What that name cannot do is identify anybody. It is generated from the address, so it carries no subscriber, no city and no product tier, and the registry stops at the /15 with a corporate registrant and a CSIRT abuse role - there is no sub-allocation object for a household anywhere beneath it. That leaves one usable inference about direction: these are access pools handed to customer equipment, so a service answering on one of these addresses belongs to a subscriber's own device rather than to anything Telefonica Brasil hosts, and a report about it goes to the CSIRT abuse address rather than to anyone identifiable from public data.
Related tools
Frequently asked questions
Which ranges does Vivo announce on AS27699?
The largest are listed above. Beyond them there is no operator-published list: the registered artefacts are the registro.br allocations plus route objects in RADB and in Level 3's routing registry, and the AS-TBSA macro is shared with six other Telefonica Brasil numbers rather than being specific to this one.
What does dsl.telesp.net.br in a hostname mean?
It is the reverse-DNS zone Telefonica Brasil uses for its fixed access pools, and the hyphenated digits in front of it are the address itself. Seeing it confirms a Brazilian fixed broadband line on Telefonica Brasil's network. It says nothing about the city or the subscriber.
Does Telefonica Brasil publish a geofeed for Vivo addresses?
Not for this space. The registro.br RDAP record for 189.46.0.0/15 carries no geofeed link, only the two in-addr.arpa zones for the block, and the PeeringDB entry lists no policy URL. Country BR is the finest granularity the operator states, so any city shown for a Vivo address comes from a commercial database.
Why do some Vivo addresses show a different ASN?
Because Telefonica Brasil holds nine networks under one PeeringDB organisation, including AS10429, AS18881 and AS26599. AS27699 is the fixed-broadband number whose pools carry the dsl.telesp.net.br naming; other Vivo services sit on the other numbers.
A leak test named Vivo - what does that tell me?
An address on AS27699 is a Brazilian fixed line, and the reverse name says so before any database does: 189.46.10.20 answers as 189-46-10-20.dsl.telesp.net.br, and the pools in 177.102, 179.110 and 201.42 space follow the same form. That is an access pool rather than a hosting range, so a proxy or exit node found on one of these blocks is somebody reselling a home connection, not a rented server. Location is where care is needed: the registro.br object for 189.46.0.0/15 records country BR and nothing finer, links no geofeed, and covers a network with a national footprint, so a city attached to a Vivo address is a database's guess and not the operator's statement. And because the same PeeringDB organisation runs eight other ASNs, an address that is obviously Vivo yet is not on AS27699 is unremarkable.