asn.dev

Observed topology

AS37228 KT RWANDA NETWORK Ltd - KT RWANDA NETWORK Ltd

Unclassified AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS37228: 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
AS37619Broadband Systems CorporationUnclassifiedIPv43,984
AS327707Airtel Rwanda LtdUnclassifiedIPv41,926
AS30844Liquid Telecommunications LtdUnclassifiedIPv4 IPv61,779
AS37273Bandwidth and Cloud Services Group LtdResidentialIPv4 IPv6880

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS328344STE Techplus SARLUnclassifiedIPv4133
AS328864DEVELOPMENT BANK OF RWANDA (B.R.D) PlcUnclassifiedIPv465
AS329104AOS LTDUnclassifiedIPv461
AS328618Ets OliverSoftUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS37619Broadband Systems CorporationUnclassifiedIPv44,082
AS30844Liquid Telecommunications LtdUnclassifiedIPv4 IPv62,003
AS327707Airtel Rwanda LtdUnclassifiedIPv41,926
AS37273Bandwidth and Cloud Services Group LtdResidentialIPv4 IPv6910
AS328344STE Techplus SARLUnclassifiedIPv4133
AS328864DEVELOPMENT BANK OF RWANDA (B.R.D) PlcUnclassifiedIPv465
AS329104AOS LTDUnclassifiedIPv461
AS328618Ets OliverSoftUnclassifiedIPv460
AS37654Rwanda Ministry of EducationUnclassifiedIPv433

Provenance

Where this comes from

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