Observed topology

AS36943 ZA-1-Grid

Hosting AFRINIC

Upstreams 5 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS36943: 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
AS37271	Workonline Communications(Pty) Ltd	Unclassified	IPv4 IPv6	220
AS37680	Cool Ideas Service Provider (Pty) Ltd	Residential	IPv4	59
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	53
AS30844	Liquid Telecommunications Ltd	Unclassified	IPv4 IPv6	50
AS37721	Virtual Technologies & Solutions	Residential	IPv4	5

Transit

Downstream networks

inferred

Networks for which AS36943 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 AS36943 in a routing path, in either direction.

AS	Network	Type	Families	Paths seen
AS37271	Workonline Communications(Pty) Ltd	Unclassified	IPv4 IPv6	220
AS37680	Cool Ideas Service Provider (Pty) Ltd	Residential	IPv4	59
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	53
AS30844	Liquid Telecommunications Ltd	Unclassified	IPv4 IPv6	50
AS37721	Virtual Technologies & Solutions	Residential	IPv4	5

Provenance

Where this comes from

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