asn.dev

Observed topology

AS36962 MTN Zambia - MTN Zambia

Hosting AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS36962: 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
AS30844Liquid Telecommunications LtdUnclassifiedIPv42,301
AS16637MTN SAMobileIPv4699

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS37185iSAT Africa Zambia LtdUnclassifiedIPv4198
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv693
AS199524G-Core Labs S.A.HostingIPv447
AS64945unnamedUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS30844Liquid Telecommunications LtdUnclassifiedIPv4 IPv62,468
AS16637MTN SAMobileIPv4933
AS37185iSAT Africa Zambia LtdUnclassifiedIPv4198
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv693
AS199524G-Core Labs S.A.HostingIPv447
AS64945unnamedUnclassifiedIPv41

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.