Tata Communications IP Ranges
Tata Communications runs two separate autonomous systems under one brand, and AS4755 is the Indian one. It descends from VSNL, and the PeeringDB record Tata maintains for it dates the first publicly available internet service in India to 14 August 1995 and describes the network as serving over 5,000 enterprise customers and more than 100 ISP or carrier customers in India. The blocks are registered with APNIC under the organisation handle ORG-TCL6-AP with netname TATACOMM-IN and status ALLOCATED PORTABLE, and the 14.140.0.0/14 allocation was recorded on 7 September 2010. The backbone that carries Tata traffic between continents is AS6453, a separate record whose declared scope is Global where this one declares Asia Pacific.
- Provider
- Tata Communications
- Primary ASN
- AS4755
- Category
- Transit
- Headquarters
- Mumbai, India
- Announced IPv4 prefixes
- 2310
- Registry
- APNIC
Known IP ranges
These prefixes are currently announced to the global routing table by AS4755 (TATACOMM-AS - TATA Communications formerly VSNL is Leading ISP). Prefix sets change over time - use WHOIS Lookup for the authoritative record on any specific address.
14.140.0.0/14
59.160.0.0/16
203.200.0.0/16
202.54.0.0/16
121.241.0.0/16
121.240.0.0/16
115.113.0.0/16
121.242.0.0/16
115.119.0.0/16
203.197.0.0/16
2400:a240::/32
2403::/32
2604:a140:1502::/47 (IPv6)
What does a Tata Communications IP mean in a privacy test?
An address on AS4755 puts the connection in India and on the domestic side of the company rather than the intercontinental one. Tata's own PeeringDB entry describes the customer base as thousands of enterprises and around a hundred ISP or carrier customers, which is why an exit found here is far more often a leased circuit or a hosted machine than a household line. The reverse-DNS name usually states the city the circuit terminates in, and for Indian space that is a better locator than most commercial databases manage. What no public record will tell you is who is behind the address, because a single assignment out of TATACOMM-IN can front an enterprise, a smaller provider reselling capacity or a hosting customer, and none of those names reach APNIC. Anything worth reporting goes to the abuse mailbox APNIC lists for the block, which has the AS number written into it.
What Tata publishes for AS4755, and where it lives
Tata publishes no geolocation file for this space: there is no geofeed attribute on the APNIC objects, and no allowlist a firewall could load. The registry record is what there is, and it is consistent across the network - netname TATACOMM-IN, organisation ORG-TCL6-AP, status ALLOCATED PORTABLE, and an incident response team object IRT-TATACOMM-IN whose abuse address is 4755abuse@tatacommunications.com, with technical contact ip.admin@tatacommunications.com and a Bandra Kurla Complex address in Mumbai. The AS-SET the company names in its own PeeringDB entry is AS-VSNL-IN, and the scope it declares there is Asia Pacific, which is the cleanest single confirmation that this is not the worldwide network.
The one substantive routing document Tata does publish is its customer BGP filter policy, served from the looking-glass domain of the other ASN at lg.as6453.net/doc/cust-routing-policy.html and written for Tata Communications customers generally rather than for a single AS number. It requires route and route6 objects in the authoritative registry for the resource - AfriNIC, APNIC, ARIN, LACNIC, RIPE, NIC.br or IDNIC - and states that objects created in non-authoritative registries after 15 August 2023 will not be processed; it wants an AS-SET in the form ASNNN:AS-YYYYY from anyone reselling transit; it says filters are rebuilt from the registries and pushed to the routers within 24 hours; it accepts nothing longer than a /24 in IPv4 or a /48 in IPv6 except blackhole announcements, which must be a /32 or a /128; and it gives ROA objects higher precedence than route objects where the two disagree. None of that describes where an address is or who is using it, so for those questions the APNIC object and the reverse-DNS name are still the only sources.
Telling a Tata circuit from the customer behind it
Reverse DNS on this network still runs under the old carrier's domain. A name looks like 121.241.10.5.mumbai-static.vsnl.net.in or 14.140.10.5.static-Hyderabad.vsnl.net.in: the dotted address repeated as a label, then a pool name that usually contains a city and the word static, then vsnl.net.in, a zone delegated to nameservers under tatacommunications.com. Word order and capitalisation inside the pool label differ from block to block - Hyderabad is capitalised where mumbai is not, and the city sits before the word static in one and after it in the other - and some space carries no name at all, so matching should be done on the vsnl.net.in suffix with the city treated as a hint rather than a field.
The word static in those names is the name of the pool, not a statement that one customer holds the address, and the record is generated across the block whether or not anything is using it, so a name that resolves is no evidence a host is there. Neither does the name say whose host it is. Tata assigns out of TATACOMM-IN to enterprises, to hosting customers and to smaller providers reselling its capacity, and none of them appear in whois, which names Tata Communications for the whole allocation. Routing is the only public place a downstream operator identifies itself: if the address falls inside a more specific prefix originated by some other AS number, that network is the one to pursue, and if the covering Tata prefix is the only route, the circuit terminates on Tata's own edge.
Related tools
Frequently asked questions
Is AS4755 the same as the Tata backbone people call tier one?
No. AS4755 is the India network, formerly VSNL, and declares an Asia Pacific scope in its own PeeringDB record. The worldwide Tata backbone is AS6453, a separate registration with a different IRR AS-SET, AS-GLOBEINTERNET against this one's AS-VSNL-IN, and a Global scope. Same company, different networks and different address space.
What does an AS4755 result mean for a VPN check?
An address on AS4755 puts the connection in India and on the domestic side of the company rather than the intercontinental one. Tata's own PeeringDB entry describes the customer base as thousands of enterprises and around a hundred ISP or carrier customers, which is why an exit found here is far more often a leased circuit or a hosted machine than a household line. The reverse-DNS name usually states the city the circuit terminates in, and for Indian space that is a better locator than most commercial databases manage. What no public record will tell you is who is behind the address, because a single assignment out of TATACOMM-IN can front an enterprise, a smaller provider reselling capacity or a hosting customer, and none of those names reach APNIC. Anything worth reporting goes to the abuse mailbox APNIC lists for the block, which has the AS number written into it.
Why do Tata addresses still resolve under vsnl.net.in?
Because the reverse zone was never renamed after VSNL became Tata Communications. Names take the form 59.160.10.5.static.vsnl.net.in, and the vsnl.net.in zone is delegated to nameservers inside tatacommunications.com, so the old domain is still the authoritative one for this space.
Does Tata Communications publish a geofeed for these ranges?
It does not. The APNIC objects for TATACOMM-IN carry no geofeed attribute and there is no published per-block location file, so a lookup that places one of these addresses in a particular Indian city is relying on the reverse-DNS pool name or on a commercial database rather than on anything Tata states.
Where do I report abuse coming from an AS4755 address?
APNIC registers an incident response team object for this space, IRT-TATACOMM-IN, and the address it lists is 4755abuse@tatacommunications.com. If the address sits inside a more specific prefix announced by a different AS number, report it to that network instead, because the host is behind a customer of Tata rather than on Tata's own edge.