asn.dev

Observed topology

AS20294 MTN-

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20294: 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 IPv64,495

Transit

Downstream networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS37063Roke Investments International LtdUnclassifiedIPv44,105
AS12491Gilat Telecom Ltd.UnclassifiedIPv4872
AS328015Sombha Solutions Store LimitedUnclassifiedIPv4546
AS29039IDDQD-ASUnclassifiedIPv4414
AS329684HYDE INNOVATIONS LTDUnclassifiedIPv4313
AS36901DATANET.COM LLCUnclassifiedIPv4 IPv6271
AS328939Sprint Internet LimitedUnclassifiedIPv4247
AS329780NITRO NET SYSTEMS LIMITEDUnclassifiedIPv4198
AS10798The Standard Bank of South Africa (Proprietary) LimitedUnclassifiedIPv4127
AS328408HAMILTON TELECOM LIMITEDUnclassifiedIPv4119

Adjacency

Adjacent networks

All 27

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

ASNetworkTypeFamiliesPaths seen
AS16637MTN SAMobileIPv4 IPv613,135
AS37063Roke Investments International LtdUnclassifiedIPv44,257
AS12491Gilat Telecom Ltd.UnclassifiedIPv4872
AS328015Sombha Solutions Store LimitedUnclassifiedIPv4741
AS30844Liquid Telecommunications LtdUnclassifiedIPv4469
AS29039IDDQD-ASUnclassifiedIPv4414
AS329684HYDE INNOVATIONS LTDUnclassifiedIPv4313
AS36901DATANET.COM LLCUnclassifiedIPv4 IPv6271
AS328939Sprint Internet LimitedUnclassifiedIPv4247
AS329780NITRO NET SYSTEMS LIMITEDUnclassifiedIPv4198

Provenance

Where this comes from

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