asn.dev

Observed topology

AS134034 BUDANTA-AS-IN - BUDANTA NETWORKS PRIVATE LIMITED

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS134034: 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 IPv6831
AS24309Atria Convergence Technologies Pvt. Ltd. Broadband Internet Service Provider INDIAResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS134887Aristo Telenet Private LimitedUnclassifiedIPv4120
AS142493Sri Ramachandra Institute Of Higher Education And ResearchUnclassifiedIPv439

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv61,077
AS134887Aristo Telenet Private LimitedUnclassifiedIPv4120
AS18002AS Number for Interdomain RoutingUnclassifiedIPv460
AS142493Sri Ramachandra Institute Of Higher Education And ResearchUnclassifiedIPv439
AS56272Pulse Telesystems Pvt LtdResidentialIPv427
AS24309Atria Convergence Technologies Pvt. Ltd. Broadband Internet Service Provider INDIAResidentialIPv41

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.