asn.dev

Observed topology

AS24432 AXIATA-ROBI-AS-AP TM International Bangladesh Ltd.Internet service Provider,Gulshan-1,Dhaka-1212

Mobile APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS24432: 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
AS58682Level3 Carrier Ltd.HostingIPv4 IPv63,319
AS17494Telecom Operator & Internet Service Provider as wellUnclassifiedIPv4 IPv62,863
AS58717Summit Communications LtdUnclassifiedIPv4 IPv6756
AS17806Tire-1 IP Transit Provider of BangladeshMobileIPv473

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv6102
AS24429Zhejiang Taobao Network Co.,LtdHostingIPv4 IPv669

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS58682Level3 Carrier Ltd.HostingIPv4 IPv63,473
AS17494Telecom Operator & Internet Service Provider as wellUnclassifiedIPv4 IPv62,863
AS58717Summit Communications LtdUnclassifiedIPv4 IPv6773
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv6102
AS17806Tire-1 IP Transit Provider of BangladeshMobileIPv473
AS24429Zhejiang Taobao Network Co.,LtdHostingIPv4 IPv669

Provenance

Where this comes from

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