Observed topology

AS37075 Airtel Uganda Limited - Airtel Uganda Limited

Mobile RIPE

Upstreams 2 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS37075: 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
AS327708	Airtel Rwanda Ltd	Unclassified	IPv4 IPv6	4,181
AS37440	Airtel Malawi Ltd	Unclassified	IPv4	131

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS329253	Cheetahnet Solutions Limited	Unclassified	IPv4	69
AS36977	Airtel Uganda Limited	Unclassified	IPv4	66
AS328233	DFCU Bank Limited	Unclassified	IPv4	37

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS327708	Airtel Rwanda Ltd	Unclassified	IPv4 IPv6	4,483
AS37440	Airtel Malawi Ltd	Unclassified	IPv4	131
AS329253	Cheetahnet Solutions Limited	Unclassified	IPv4	78
AS36977	Airtel Uganda Limited	Unclassified	IPv4	66
AS37273	Bandwidth and Cloud Services Group Ltd	Residential	IPv4	58
AS328233	DFCU Bank Limited	Unclassified	IPv4	37
AS327724	National Information Technology Authority Uganda	Unclassified	IPv4	35
AS30844	Liquid Telecommunications Ltd	Unclassified	IPv4	27
AS20294	MTN Uganda	Unclassified	IPv4	5
AS36926	Airtel Networks Kenya Limited	Unclassified	IPv4	4

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.