asn.dev

Observed topology

AS151734 WEBYNEDC-AS-IN WEBYNE DATA CENTRE PRIVATE LIMITED

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS151734: 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
AS13335Cloudflare, Inc.HostingIPv43,190
AS9498BHARTI Airtel Ltd.MobileIPv456
AS133676Precious netcom pvt ltdUnclassifiedIPv4 IPv638
AS45117Ishans NetworkResidentialIPv4 IPv67
AS17439NTT COMMUNICATIONS INDIA NETWORK SERVICES PRIVATE LIMITEDHostingIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS152523BLAZING BULLET PRIVATE LIMITEDUnclassifiedIPv4117

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS13335Cloudflare, Inc.HostingIPv43,190
AS152523BLAZING BULLET PRIVATE LIMITEDUnclassifiedIPv4117
AS140641YOTTA NETWORK SERVICES PRIVATE LIMITEDUnclassifiedIPv4116
AS9498BHARTI Airtel Ltd.MobileIPv456
AS133676Precious netcom pvt ltdUnclassifiedIPv4 IPv639
AS45117Ishans NetworkResidentialIPv4 IPv67
AS17439NTT COMMUNICATIONS INDIA NETWORK SERVICES PRIVATE LIMITEDHostingIPv43

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.