asn.dev

Observed topology

AS151704 BHARATDC-AS BHARAT DATACENTER

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS151704: 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
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv61,685
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv6266

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS154317VyomCloudUnclassifiedIPv4244
AS213535YottaSrcHostingIPv4 IPv6157
AS152485Hosterdaddy Private LimitedUnclassifiedIPv461
AS214441LHY TECHNOLOGIES PRIVATE LIMITEDHostingIPv461
AS214485HEROXHOST NETWORKS PRIVATE LIMITEDUnclassifiedIPv635
AS214832METAMONIX GLOBAL PRIVATE LIMITEDUnclassifiedIPv635

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv62,132
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv6412
AS154317VyomCloudUnclassifiedIPv4244
AS213535YottaSrcHostingIPv4 IPv6157
AS152485Hosterdaddy Private LimitedUnclassifiedIPv461
AS214441LHY TECHNOLOGIES PRIVATE LIMITEDHostingIPv461
AS214485HEROXHOST NETWORKS PRIVATE LIMITEDUnclassifiedIPv635
AS214832METAMONIX GLOBAL PRIVATE LIMITEDUnclassifiedIPv635

Provenance

Where this comes from

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