asn.dev

Observed topology

AS37294 TELEKOM NETWORKS MALAWI LTD - TELEKOM NETWORKS MALAWI LTD

Unclassified AFRINIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS37294: 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
AS16637MTN SAMobileIPv4 IPv63,039
AS30844Liquid Telecommunications LtdUnclassifiedIPv4 IPv62,210
AS20459Telecom NamibiaUnclassifiedIPv42,002
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv4 IPv61,583
AS3491PCCW Global (HK) Ltd.TransitIPv4240

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS36913TELEKOM NETWORKS MALAWI LTDUnclassifiedIPv4 IPv62,048
AS37098globe internet limitedResidentialIPv4462
AS328919Open Connect LimitedUnclassifiedIPv4120

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS16637MTN SAMobileIPv4 IPv63,642
AS30844Liquid Telecommunications LtdUnclassifiedIPv4 IPv63,149
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv4 IPv62,746
AS36913TELEKOM NETWORKS MALAWI LTDUnclassifiedIPv4 IPv62,116
AS20459Telecom NamibiaUnclassifiedIPv42,067
AS37098globe internet limitedResidentialIPv4532
AS3491PCCW Global (HK) Ltd.TransitIPv4240
AS328919Open Connect LimitedUnclassifiedIPv4120

Provenance

Where this comes from

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