Observed topology

AS9832 ISN-AS-AP ISN, Internet Service Provider

Residential APNIC

Upstreams 3 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 1

Upstream graph Who carries AS9832, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS9832 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS9832: 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.

AS	Network	Type	Families	Paths seen
AS58682	Level3 Carrier Ltd.	Hosting	IPv4	1,764
AS58656	bdHUB Limited	Unclassified	IPv4 IPv6	1,049
AS58715	EARTH TELECOMMUNICATION (Pvt) LTD.	Unclassified	IPv4	65

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS136808	One Bank Limited	Unclassified	IPv4	105
AS153491	Pubali Bank Securities Limited	Unclassified	IPv4	66
AS150152	Agrani Bank Limited	Unclassified	IPv4	60
AS64046	Pubali Bank Limited	Unclassified	IPv4	43

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS58682	Level3 Carrier Ltd.	Hosting	IPv4	1,979
AS58656	bdHUB Limited	Unclassified	IPv4 IPv6	1,108
AS136808	One Bank Limited	Unclassified	IPv4	105
AS153491	Pubali Bank Securities Limited	Unclassified	IPv4	66
AS58715	EARTH TELECOMMUNICATION (Pvt) LTD.	Unclassified	IPv4	65
AS150152	Agrani Bank Limited	Unclassified	IPv4	60
AS64046	Pubali Bank Limited	Unclassified	IPv4	43

Provenance

Where this comes from

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