Observed topology

AS55406 HRCTECH-01-AS-AP 26 Shyamoli, Bir Uttam A. W. Chowdhury Road

Unclassified APNIC

Upstreams 3 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS55406: 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
AS10075	Fiber@Home Global Limited	Residential	IPv4	469
AS58682	Level3 Carrier Ltd.	Hosting	IPv4 IPv6	446
AS58717	Summit Communications Ltd	Unclassified	IPv4	393

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS140524	PEOPLENTECHDNS-AS-AP People N Tech Limited	Unclassified	IPv4	118
AS137221	Standard Group Limited	Unclassified	IPv4	59
AS153980	BRAC-Aarong	Unclassified	IPv4	59
AS139913	First Security Islami Bank Limited	Unclassified	IPv4	57

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS58717	Summit Communications Ltd	Unclassified	IPv4	627
AS58682	Level3 Carrier Ltd.	Hosting	IPv4 IPv6	505
AS10075	Fiber@Home Global Limited	Residential	IPv4	469
AS140524	PEOPLENTECHDNS-AS-AP People N Tech Limited	Unclassified	IPv4	118
AS137221	Standard Group Limited	Unclassified	IPv4	59
AS153980	BRAC-Aarong	Unclassified	IPv4	59
AS139913	First Security Islami Bank Limited	Unclassified	IPv4	57

Provenance

Where this comes from

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