asn.dev

Observed topology

AS138277 RADINET-AS-IN Radinet Info Solutions Private Limited

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS138277: 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 IPv61,510
AS55410Vodafone Idea LtdMobileIPv4602

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS151772Sky Fi Broadband Services Private LimitedUnclassifiedIPv4 IPv6277
AS138772Mahrth Internet Service Private LimitedUnclassifiedIPv4 IPv6155
AS134945Blue Sky Broadband Pvt. Ltd.ResidentialIPv4120

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv61,568
AS55410Vodafone Idea LtdMobileIPv4 IPv61,096
AS151772Sky Fi Broadband Services Private LimitedUnclassifiedIPv4 IPv6277
AS138772Mahrth Internet Service Private LimitedUnclassifiedIPv4 IPv6155
AS134945Blue Sky Broadband Pvt. Ltd.ResidentialIPv4120

Provenance

Where this comes from

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