Observed topology

AS36937 Neotel-AS

Residential AFRINIC

Upstreams 1 carry this network

Downstreams 8 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS36937: 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
AS30844	Liquid Telecommunications Ltd	Unclassified	IPv4 IPv6	1,301

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS11179	Aryaka Networks, Inc.	Hosting	IPv4	66
AS328312	Deloitte & Touche South Africa	Unclassified	IPv4	65
AS37145	Umoya Networks	Unclassified	IPv4	59
AS37180	South African Airways	Unclassified	IPv4	59
AS37312	Clickatell PTY(LTD)	Unclassified	IPv4	59
AS37351	AFDB - African Development Bank - AFDB	Unclassified	IPv4	59
AS37302	Dube TradePort	Unclassified	IPv6	18
AS37314	Inq Digital South Africa (Pty) Ltd	Unclassified	IPv4 IPv6	3

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS30844	Liquid Telecommunications Ltd	Unclassified	IPv4 IPv6	1,689
AS11179	Aryaka Networks, Inc.	Hosting	IPv4	66
AS328312	Deloitte & Touche South Africa	Unclassified	IPv4	65
AS37145	Umoya Networks	Unclassified	IPv4	59
AS37180	South African Airways	Unclassified	IPv4	59
AS37312	Clickatell PTY(LTD)	Unclassified	IPv4	59
AS37351	AFDB - African Development Bank - AFDB	Unclassified	IPv4	59
AS37302	Dube TradePort	Unclassified	IPv6	18
AS37314	Inq Digital South Africa (Pty) Ltd	Unclassified	IPv4 IPv6	3

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-18 10: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.