Observed topology

AS328658 De-Choicetech-Integrated

Unclassified LACNIC

Upstreams 2 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS328658: 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
AS37662	West Indian Ocean Cable Company	Unclassified	IPv4 IPv6	419
AS37721	Virtual Technologies & Solutions	Residential	IPv4	4

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS328171	TREFOIL NETWORKS LTD	Unclassified	IPv4	130
AS329487	Fibernet Broadband Ltd	Unclassified	IPv4	65
AS329659	Lineserve Limited	Unclassified	IPv4	65
AS329716	DMK Telecommunication Nig LTD	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS37662	West Indian Ocean Cable Company	Unclassified	IPv4 IPv6	738
AS328171	TREFOIL NETWORKS LTD	Unclassified	IPv4	130
AS329487	Fibernet Broadband Ltd	Unclassified	IPv4	65
AS329659	Lineserve Limited	Unclassified	IPv4	65
AS329716	DMK Telecommunication Nig LTD	Unclassified	IPv4	59
AS37721	Virtual Technologies & Solutions	Residential	IPv4	4

Provenance

Where this comes from

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