asn.dev

Observed topology

AS329523 ECHOSP-KE

Unclassified AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS329523: 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
AS30844Liquid Telecommunications LtdUnclassifiedIPv439
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv411
AS6939Hurricane Electric LLCTransitIPv49
AS328977Wavex Internet Service Provider LTDResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS329106CCI SOUTH AFRICA (PTY) LTDUnclassifiedIPv4118

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS30844Liquid Telecommunications LtdUnclassifiedIPv4120
AS329106CCI SOUTH AFRICA (PTY) LTDUnclassifiedIPv4118
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv430
AS6939Hurricane Electric LLCTransitIPv427
AS328977Wavex Internet Service Provider LTDResidentialIPv41

Provenance

Where this comes from

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