Observed topology

AS58689 ICCNET-DHK-BD - ICC Communication

Residential APNIC Cable/DSL/ISP

Upstreams 1 carry this network

Downstreams 7 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58689: 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
AS137491	PEEREX NETWORKS LTD./IIG	Residential	IPv4 IPv6	1,988

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS138567	The Computer Systems	Unclassified	IPv4	240
AS154439	Techabyte Solutions	Unclassified	IPv4 IPv6	94
AS135628	PC-Net	Unclassified	IPv6	66
AS63840	Live Network & System	Unclassified	IPv4	59
AS137020	Fast Cyber Network	Unclassified	IPv4	59
AS136450	Kastech Computer Valley	Unclassified	IPv4 IPv6	34
AS154109	Hosting Oxygen	Unclassified	IPv4	8

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS137491	PEEREX NETWORKS LTD./IIG	Residential	IPv4 IPv6	2,548
AS138567	The Computer Systems	Unclassified	IPv4	240
AS154439	Techabyte Solutions	Unclassified	IPv4 IPv6	94
AS135628	PC-Net	Unclassified	IPv6	66
AS63840	Live Network & System	Unclassified	IPv4	59
AS137020	Fast Cyber Network	Unclassified	IPv4	59
AS136450	Kastech Computer Valley	Unclassified	IPv4 IPv6	34
AS154109	Hosting Oxygen	Unclassified	IPv4	8

Provenance

Where this comes from

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