asn.dev

Observed topology

AS328840 ST-Digital-AS

Hosting AFRINIC

Upstreams 5 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 6
Adjacent (IPv6) 5
Upstream graph Who carries AS328840, and who carries them, drawn as a map up to the transit-free core. 4 exchanges Where AS328840 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS328840: 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.

ASNetworkTypeFamiliesPaths seen
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv4 IPv6291
AS37282Main one Cable Company Nigeria LimitedResidentialIPv4 IPv6150
AS327727C-Squared LimitedUnclassifiedIPv4 IPv6146
AS329118AXIONE Gabon SAUnclassifiedIPv458
AS15964CAMTELHostingIPv413

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS328913ST DIGITALHostingIPv4 IPv671
AS329470Afriland First BankUnclassifiedIPv637

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS327727C-Squared LimitedUnclassifiedIPv4 IPv61,062,535
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv4 IPv6389
AS37282Main one Cable Company Nigeria LimitedResidentialIPv4 IPv6160
AS328913ST DIGITALHostingIPv4 IPv671
AS329118AXIONE Gabon SAUnclassifiedIPv458
AS329470Afriland First BankUnclassifiedIPv637
AS15964CAMTELHostingIPv413

Provenance

Where this comes from

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