Observed topology

AS17644 IOT-AS-AP IoT Techsmart Pte. Ltd.

Unclassified ARIN

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17644: 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
AS134371	CIRCLE NETWORK BANGLADESH	Residential	IPv4 IPv6	146
AS63969	Race Online Limited	Residential	IPv4 IPv6	137
AS139009	Windstream Communication Limited	Unclassified	IPv4	61
AS23470	ReliableSite.Net LLC	Hosting	IPv4	59
AS55492	Dhaka Fiber Net Limited	Unclassified	IPv4 IPv6	58
AS58826	ping by ICOM Bangladesh Ltd	Unclassified	IPv4 IPv6	43

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS197537	WISDOM CLOUD INTERNET TECHNOLOGY PTE. LTD.	Hosting	IPv4	390

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS139009	Windstream Communication Limited	Unclassified	IPv4	451
AS197537	WISDOM CLOUD INTERNET TECHNOLOGY PTE. LTD.	Hosting	IPv4	390
AS134371	CIRCLE NETWORK BANGLADESH	Residential	IPv4 IPv6	146
AS63969	Race Online Limited	Residential	IPv4 IPv6	137
AS23470	ReliableSite.Net LLC	Hosting	IPv4	59
AS55492	Dhaka Fiber Net Limited	Unclassified	IPv4 IPv6	58
AS58826	ping by ICOM Bangladesh Ltd	Unclassified	IPv4 IPv6	43

Provenance

Where this comes from

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