Observed topology

AS38017 GLOBAL-TRANSIT-AS-SILBD Route object of Square InformatiX Ltd

Unclassified APNIC

Upstreams 2 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38017: 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	541
AS58656	bdHUB Limited	Unclassified	IPv4	479

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS139674	Square InformatiX Ltd	Unclassified	IPv4	180
AS58581	Standard Bank LIMITED	Unclassified	IPv4	120
AS55344	Head Office	Unclassified	IPv4	82
AS142159	Bangladesh Public Administration Training Centre	Unclassified	IPv4	47

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS58682	Level3 Carrier Ltd.	Hosting	IPv4	970
AS58656	bdHUB Limited	Unclassified	IPv4	479
AS139674	Square InformatiX Ltd	Unclassified	IPv4	180
AS58581	Standard Bank LIMITED	Unclassified	IPv4	120
AS55344	Head Office	Unclassified	IPv4	82
AS142159	Bangladesh Public Administration Training Centre	Unclassified	IPv4	47

Provenance

Where this comes from

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