asn.dev

Observed topology

AS397849 ZOHO-STREAMING-CONTENT-NETWORK - ZOHO

Hosting ARIN

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS397849: 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
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4 IPv6279
AS174Cogent Communications, LLCTransitIPv4 IPv6272
AS3356Level 3 Parent, LLCTransitIPv4 IPv6191
AS56201Zoho Corporation Pvt. Ltd,UnclassifiedIPv4 IPv689
AS20473The Constant Company, LLCHostingIPv4 IPv685
AS6939Hurricane Electric LLCTransitIPv454
AS27224Equinix, Inc.UnclassifiedIPv448
AS205111ZOHO Corporation B.VUnclassifiedIPv4 IPv636
AS20055Wholesail networks LLCResidentialIPv416
AS24482SG.GSHostingIPv4 IPv69

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4 IPv6279
AS174Cogent Communications, LLCTransitIPv4 IPv6272
AS3356Level 3 Parent, LLCTransitIPv4 IPv6191
AS56201Zoho Corporation Pvt. Ltd,UnclassifiedIPv4 IPv689
AS20473The Constant Company, LLCHostingIPv4 IPv685
AS6939Hurricane Electric LLCTransitIPv454
AS27224Equinix, Inc.UnclassifiedIPv448
AS205111ZOHO Corporation B.VUnclassifiedIPv4 IPv636
AS20055Wholesail networks LLCResidentialIPv416
AS24482SG.GSHostingIPv4 IPv69

Provenance

Where this comes from

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