asn.dev

Observed topology

AS328608 Africa-on-Cloud-AS

Hosting DROP-listed space AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS328608: 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.UnclassifiedIPv415,717
AS37497Network-PlatformsUnclassifiedIPv4275
AS6939Hurricane Electric LLCTransitIPv4 IPv6240
AS37315CipherWaveUnclassifiedIPv4163
AS13335Cloudflare, Inc.HostingIPv464
AS37721Virtual-Technologies-Solutions-SAResidentialIPv47

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS36898CurrantUnclassifiedIPv43,909
AS328693IFOWUNI-PTYUnclassifiedIPv487
AS17561LARUS LimitedUnclassifiedIPv443
AS327794CLEAR-ACCESSUnclassifiedIPv46

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv419,731
AS36898CurrantUnclassifiedIPv43,909
AS37497Network-PlatformsUnclassifiedIPv4306
AS6939Hurricane Electric LLCTransitIPv4 IPv6240
AS37315CipherWaveUnclassifiedIPv4163
AS328693IFOWUNI-PTYUnclassifiedIPv487
AS13335Cloudflare, Inc.HostingIPv464
AS17561LARUS LimitedUnclassifiedIPv443
AS37721Virtual-Technologies-Solutions-SAResidentialIPv47
AS327794CLEAR-ACCESSUnclassifiedIPv46

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.