asn.dev

Observed topology

AS36915 Echotel International Kenya Limited - Echotel International Kenya Limited

Unclassified AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS36915: 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
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv41,585
AS37100SEACOM LimitedUnclassifiedIPv4 IPv61,084
AS15399Wananchi Group (Kenya) LimitedResidentialIPv448
AS6939Hurricane Electric LLCTransitIPv4 IPv645
AS328977Wavex Internet Service Provider LTDResidentialIPv442

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS37684Angani LimitedHostingIPv4 IPv6135
AS329272Servercore Africa LtdUnclassifiedIPv622

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv41,677
AS37100SEACOM LimitedUnclassifiedIPv4 IPv61,084
AS37684Angani LimitedHostingIPv4 IPv6135
AS6939Hurricane Electric LLCTransitIPv4 IPv6108
AS15399Wananchi Group (Kenya) LimitedResidentialIPv450
AS328977Wavex Internet Service Provider LTDResidentialIPv442
AS329272Servercore Africa LtdUnclassifiedIPv622

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.