asn.dev

Observed topology

AS329626 Oryx Fibre Infrastructure (Pty) Ltd - Oryx Fibre Infrastructure (Pty) Ltd

Unclassified AFRINIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS329626: 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
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv4 IPv691
AS37009Mobile Telecommunications, Ltd. - MTC - Mobile Telecommunications, Ltd.UnclassifiedIPv411

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS36877Africa Online (Africa) (Pty) LtdUnclassifiedIPv4159

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv4 IPv6250
AS36877Africa Online (Africa) (Pty) LtdUnclassifiedIPv4159
AS37009Mobile Telecommunications, Ltd. - MTC - Mobile Telecommunications, Ltd.UnclassifiedIPv411

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.