Observed topology

AS327935 iSPACE (PTY) LTD - iSPACE (PTY) LTD

Unclassified AFRINIC

Upstreams 6 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 0

Upstream graph Who carries AS327935, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS327935 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS327935: 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.

AS	Network	Type	Families	Paths seen
AS60171	AFR-IX TELECOM S.A.	Unclassified	IPv4	467
AS5713	Telkom SA Ltd.	Unclassified	IPv4	336
AS174	Cogent Communications, LLC	Transit	IPv4	76
AS23764	CTGNet	Unclassified	IPv4	65
AS3741	Dimension Data	Unclassified	IPv4	14
AS37721	Virtual Technologies & Solutions	Residential	IPv4	14

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS11157	-	Unclassified	IPv4	65
AS328483	Comput8 IT (Pty) Ltd	Unclassified	IPv4	34

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS60171	AFR-IX TELECOM S.A.	Unclassified	IPv4	528
AS5713	Telkom SA Ltd.	Unclassified	IPv4	358
AS174	Cogent Communications, LLC	Transit	IPv4	90
AS11157	-	Unclassified	IPv4	65
AS23764	CTGNet	Unclassified	IPv4	65
AS328483	Comput8 IT (Pty) Ltd	Unclassified	IPv4	34
AS3741	Dimension Data	Unclassified	IPv4	15
AS37721	Virtual Technologies & Solutions	Residential	IPv4	15

Provenance

Where this comes from

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