asn.dev

Observed topology

AS134674 TATAPLAYBROADBAND-AS-AP TATA PLAY BROADBAND PRIVATE LIMITED

Upstreams 3 carry this network
Downstreams 5 this network carries
Adjacent (IPv4) 7
Adjacent (IPv6) 7

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS134674: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv618,424
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv65,915
AS35280F5 Networks SARLHostingIPv623

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you.

Transit

Downstream networks

inferred

Networks for which AS134674 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS154678ASIA GIGA FIBERNET PRIVATE LIMITEDUnclassifiedIPv4 IPv6260
AS151729SWIFTIFY PRIVATE LIMITEDUnclassifiedIPv4 IPv6157
AS153241APLEIXA TECHNOLOGIES PVT LTDUnclassifiedIPv4122
AS141519Yuvaa Communications Private LimitedResidentialIPv4 IPv696
AS141865N4U BROADBAND PRIVATE LIMITEDResidentialIPv4 IPv696

Adjacency

Adjacent networks

15 shown

Every AS seen directly next to AS134674 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv619,478
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv66,175
AS141519Yuvaa Communications Private LimitedResidentialIPv4 IPv6375
AS154678ASIA GIGA FIBERNET PRIVATE LIMITEDUnclassifiedIPv4 IPv6260
AS151729SWIFTIFY PRIVATE LIMITEDUnclassifiedIPv4 IPv6157
AS153241APLEIXA TECHNOLOGIES PVT LTDUnclassifiedIPv4122
AS141865N4U BROADBAND PRIVATE LIMITEDResidentialIPv4 IPv696
AS35280F5 Networks SARLHostingIPv623

Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS134674, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 6 exchanges across 1 country and 1 region.

ExchangeLocationTheir addressMember ports
Extreme IX MumbaiMumbai, India103.77.108.106246
Extreme IX New DelhiNew Delhi, India45.120.248.136174
Extreme IX ChennaiChennai, India45.120.251.5895
AMS-IX MumbaiMumbai, India223.31.200.13085
Extreme IX BangaloreBangalore, India38.10.0.3039
Extreme IX KolkataKolkata, India45.120.249.3425

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Provenance

Where this comes from

Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

Exchange presence comes from a separate dataset: the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.