asn.dev

Observed topology

AS329415 Savanna Fibre Limited - Savanna Fibre Limited

Unclassified AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS329415: 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
AS37100SEACOM LimitedUnclassifiedIPv4 IPv6348
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv4126

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS37684Angani LimitedHostingIPv4 IPv699
AS329253Cheetahnet Solutions LimitedUnclassifiedIPv479
AS328939Sprint Internet LimitedUnclassifiedIPv4 IPv678

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv4552
AS37100SEACOM LimitedUnclassifiedIPv4 IPv6430
AS329253Cheetahnet Solutions LimitedUnclassifiedIPv4255
AS37684Angani LimitedHostingIPv4 IPv6165
AS328939Sprint Internet LimitedUnclassifiedIPv4 IPv678
AS328929Global Sense Pty LtdUnclassifiedIPv410

Provenance

Where this comes from

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