asn.dev

Observed topology

AS56201 ZOHO-IN Zoho Corporation Pvt. Ltd

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS56201: 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
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv6984
AS140641YOTTA NETWORK SERVICES PRIVATE LIMITEDUnclassifiedIPv4 IPv6530
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4184
AS55836Reliance Jio Infocomm LimitedMobileIPv4118
AS17762Tata Teleservices Maharashtra LtdUnclassifiedIPv478
AS24309Atria Convergence Technologies Pvt. Ltd. Broadband Internet Service Provider INDIAResidentialIPv460
AS45820Tata Teleservices ISP ASResidentialIPv460
AS18229CtrlSHostingIPv453

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS397849ZOHOHostingIPv4 IPv6106

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv61,090
AS140641YOTTA NETWORK SERVICES PRIVATE LIMITEDUnclassifiedIPv4 IPv6530
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4184
AS55836Reliance Jio Infocomm LimitedMobileIPv4118
AS397849ZOHOHostingIPv4 IPv6106
AS17762Tata Teleservices Maharashtra LtdUnclassifiedIPv478
AS24309Atria Convergence Technologies Pvt. Ltd. Broadband Internet Service Provider INDIAResidentialIPv460
AS45820Tata Teleservices ISP ASResidentialIPv460
AS18229CtrlSHostingIPv453

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.