asn.dev

Observed topology

AS20459 Telecom Namibia - Telecom Namibia

Unclassified AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20459: 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
AS174Cogent Communications, LLCTransitIPv616
AS6939Hurricane Electric LLCTransitIPv615
AS37721Virtual Technologies & SolutionsResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS37294TELEKOM NETWORKS MALAWI LTDUnclassifiedIPv42,236
AS36996Telecom NamibiaUnclassifiedIPv42,031
AS37154Zambia Telecommunications Company Ltd aka ZAMTELUnclassifiedIPv4 IPv6990
AS36999Telecom NamibiaUnclassifiedIPv464
AS22735Government of the Republic of NamibiaUnclassifiedIPv462
AS13335Cloudflare, Inc.HostingIPv458

Adjacency

Adjacent networks

All 28

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv63,443
AS37294TELEKOM NETWORKS MALAWI LTDUnclassifiedIPv42,371
AS36996Telecom NamibiaUnclassifiedIPv42,031
AS37154Zambia Telecommunications Company Ltd aka ZAMTELUnclassifiedIPv4 IPv61,002
AS6939Hurricane Electric LLCTransitIPv4 IPv6813
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6298
AS213241TECHIT.BE SRLResidentialIPv4 IPv6123
AS8551Bezeq International Ltd.UnclassifiedIPv4122
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv6122
AS212024Marc SchmittUnclassifiedIPv4 IPv6116

All 28 adjacent →

Provenance

Where this comes from

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