Observed topology

AS328797 BL26-AS

Unclassified AFRINIC NSP

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS328797: 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
AS37721	Virtual Technologies & Solutions	Residential	IPv4	160
AS37613	DOLPHIN TELECOMMUNICATION LIMITED	Unclassified	IPv4	71
AS37468	Angola Cables	Unclassified	IPv4	36

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS328984	Revabit Limited	Unclassified	IPv4	300
AS329624	MONINET	Unclassified	IPv4	37
AS328185	Consolidated Bank Ghana Limited	Unclassified	IPv4	32

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS328984	Revabit Limited	Unclassified	IPv4	300
AS37721	Virtual Technologies & Solutions	Residential	IPv4	299
AS37468	Angola Cables	Unclassified	IPv4	266
AS37613	DOLPHIN TELECOMMUNICATION LIMITED	Unclassified	IPv4	71
AS329624	MONINET	Unclassified	IPv4	37
AS328185	Consolidated Bank Ghana Limited	Unclassified	IPv4	32

Provenance

Where this comes from

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