asn.dev

Observed topology

AS134371 CIRCLENETWORK-BD CIRCLE NETWORK BANGLADESH

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS134371: 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
AS139009Windstream Communication LimitedUnclassifiedIPv4 IPv62,753

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS141030CIRCLE NETWORKUnclassifiedIPv4 IPv61,814
AS17644IoT Techsmart Pte. Ltd.UnclassifiedIPv4 IPv6239
AS136909MJL Bangladesh PLCUnclassifiedIPv4227
AS142605YetFix LimitedUnclassifiedIPv4195
AS152661ALZAF LIMITEDUnclassifiedIPv4130
AS134068Rajshahi Krishi Unnayan BankUnclassifiedIPv4123

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS139009Windstream Communication LimitedUnclassifiedIPv4 IPv65,481
AS141030CIRCLE NETWORKUnclassifiedIPv4 IPv61,814
AS17644IoT Techsmart Pte. Ltd.UnclassifiedIPv4 IPv6239
AS136909MJL Bangladesh PLCUnclassifiedIPv4227
AS142605YetFix LimitedUnclassifiedIPv4195
AS152661ALZAF LIMITEDUnclassifiedIPv4130
AS134068Rajshahi Krishi Unnayan BankUnclassifiedIPv4123
AS9441Next Online Limited.ResidentialIPv43
AS136215SB NETWORKUnclassifiedIPv43

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.