asn.dev

Observed topology

AS329097 SI Futures (Pty) Ltd - SI Futures (Pty) Ltd

Unclassified AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS329097: 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
AS37468Angola CablesUnclassifiedIPv4145
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv4130
AS37239ICTGlobe Management (Pty) LtdUnclassifiedIPv4120
AS37100SEACOM LimitedUnclassifiedIPv495
AS3741Dimension DataUnclassifiedIPv461
AS327782Metro Fibre Networx (Pty) LtdResidentialIPv460
AS37721Virtual Technologies & SolutionsResidentialIPv42

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS37468Angola CablesUnclassifiedIPv4145
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv4130
AS37239ICTGlobe Management (Pty) LtdUnclassifiedIPv4120
AS37100SEACOM LimitedUnclassifiedIPv495
AS3741Dimension DataUnclassifiedIPv461
AS327782Metro Fibre Networx (Pty) LtdResidentialIPv460
AS37721Virtual Technologies & SolutionsResidentialIPv42

Provenance

Where this comes from

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