asn.dev

Observed topology

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

Unclassified ARIN

Upstreams 6 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 8
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.

ASNetworkTypeFamiliesPaths seen
AS134371CIRCLE NETWORK BANGLADESHResidentialIPv4 IPv6145
AS63969Race Online LimitedResidentialIPv4 IPv6138
AS139009Windstream Communication LimitedUnclassifiedIPv461
AS23470ReliableSite.Net LLCHostingIPv459
AS55492Dhaka Fiber Net LimitedUnclassifiedIPv4 IPv658
AS58826ping by ICOM Bangladesh LtdUnclassifiedIPv4 IPv643

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS197537WISDOM CLOUD INTERNET TECHNOLOGY PTE. LTD.HostingIPv4390
AS153947FAST ZONE ITUnclassifiedIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS139009Windstream Communication LimitedUnclassifiedIPv4451
AS197537WISDOM CLOUD INTERNET TECHNOLOGY PTE. LTD.HostingIPv4390
AS63969Race Online LimitedResidentialIPv4 IPv6196
AS134371CIRCLE NETWORK BANGLADESHResidentialIPv4 IPv6145
AS23470ReliableSite.Net LLCHostingIPv459
AS55492Dhaka Fiber Net LimitedUnclassifiedIPv4 IPv658
AS153947FAST ZONE ITUnclassifiedIPv458
AS58826ping by ICOM Bangladesh LtdUnclassifiedIPv4 IPv643

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-25 12: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.