Observed topology

AS37063 RTL-AS

Unclassified AFRINIC NSP

Upstreams 2 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS37063: 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
AS20294	MTN Uganda	Unclassified	IPv4	4,071
AS37027	Simbanet (T) Limited	Residential	IPv4	148

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS37610	New Frontiers Technology Consult Limited	Unclassified	IPv4	65
AS328998	Uganda Internet eXchange Point	Unclassified	IPv4	65
AS327721	Interswitch Limited	Unclassified	IPv4	30
AS63293	Facebook, Inc.	Hosting	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS20294	MTN Uganda	Unclassified	IPv4	4,223
AS37027	Simbanet (T) Limited	Residential	IPv4	157
AS37610	New Frontiers Technology Consult Limited	Unclassified	IPv4	65
AS328998	Uganda Internet eXchange Point	Unclassified	IPv4	65
AS327721	Interswitch Limited	Unclassified	IPv4	30
AS63293	Facebook, Inc.	Hosting	IPv4	1

Provenance

Where this comes from

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