Observed topology

AS329788 C Squared Ghana Limited - C Squared Ghana Limited

Unclassified LACNIC

Upstreams 1 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS329788: 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
AS327727	C-Squared Limited	Unclassified	IPv4	57

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS33786	K-Net	Unclassified	IPv4	250
AS328182	Digital Arena Limited	Unclassified	IPv4	57
AS329687	G2 Telecommunications Group Ltd	Unclassified	IPv4	57
AS329617	C-Squared Limited	Unclassified	IPv4	56

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS327727	C-Squared Limited	Unclassified	IPv4	477
AS33786	K-Net	Unclassified	IPv4	250
AS328182	Digital Arena Limited	Unclassified	IPv4	57
AS329687	G2 Telecommunications Group Ltd	Unclassified	IPv4	57
AS329617	C-Squared Limited	Unclassified	IPv4	56

Provenance

Where this comes from

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