asn.dev

Observed topology

AS136306 TEXES-AS Texes Connect Private Limited

Residential APNIC

Upstreams 5 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 8
Adjacent (IPv6) 3
Upstream graph Who carries AS136306, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS136306 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS136306: 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 ISPHostingIPv4194
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv6157
AS174Cogent Communications, LLCTransitIPv4 IPv6137
AS55410Vodafone Idea LtdMobileIPv450
AS24482SG.GSHostingIPv4 IPv610

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS140114Techcellence Services Pvt LtdUnclassifiedIPv4118
AS147306VINCENTIO TECH SOLUTIONS PRIVATE LIMITEDUnclassifiedIPv4115
AS137160BHARAT DATA SERVICES PVT LTDUnclassifiedIPv437

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv6307
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4247
AS174Cogent Communications, LLCTransitIPv4 IPv6137
AS140114Techcellence Services Pvt LtdUnclassifiedIPv4118
AS55410Vodafone Idea LtdMobileIPv4115
AS147306VINCENTIO TECH SOLUTIONS PRIVATE LIMITEDUnclassifiedIPv4115
AS137160BHARAT DATA SERVICES PVT LTDUnclassifiedIPv437
AS24482SG.GSHostingIPv4 IPv612

Provenance

Where this comes from

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

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. 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.

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