Observed topology

AS327724 NITA

Unclassified APNIC

Upstreams 2 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS327724: 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
AS37100	SEACOM Limited	Unclassified	IPv4 IPv6	488
AS30844	Liquid Telecommunications Ltd	Unclassified	IPv4	174

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS37206	Central Bank of Uganda	Unclassified	IPv4	189
AS327786	4G Telecom	Unclassified	IPv4 IPv6	155
AS329669	National Identification and Registration Authority	Unclassified	IPv4	59
AS329679	National Information Technology Authority Uganda	Unclassified	IPv4	59
AS329694	Uganda Registration Services Bureau	Unclassified	IPv4	13

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS37100	SEACOM Limited	Unclassified	IPv4 IPv6	1,173
AS327786	4G Telecom	Unclassified	IPv4 IPv6	429
AS37206	Central Bank of Uganda	Unclassified	IPv4	189
AS30844	Liquid Telecommunications Ltd	Unclassified	IPv4	174
AS329669	National Identification and Registration Authority	Unclassified	IPv4	59
AS329679	National Information Technology Authority Uganda	Unclassified	IPv4	59
AS37075	Airtel Uganda Limited	Mobile	IPv4	34
AS20294	MTN Uganda	Unclassified	IPv4	30
AS329694	Uganda Registration Services Bureau	Unclassified	IPv4	13

Provenance

Where this comes from

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