asn.dev

Observed topology

AS12455 Kenyan Post & Telecommunications Company / Telkom Kenya Ltd - Kenyan Post & Telecommunications Company / Telkom Kenya Ltd

Unclassified AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12455: 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
AS37100SEACOM LimitedUnclassifiedIPv4 IPv65,282
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv42,006
AS5511Orange S.A.TransitIPv4 IPv61,781
AS6939Hurricane Electric LLCTransitIPv615

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS328847THE KONZA TECHNOPOLIS DEVELOPMENT AUTHORITYUnclassifiedIPv4363
AS328636Jambo telecoms limitedUnclassifiedIPv4182
AS37301(AfriNIC) Ltd - African Network Information Center - (AfriNIC) LtdUnclassifiedIPv432

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS37100SEACOM LimitedUnclassifiedIPv4 IPv65,420
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv42,176
AS5511Orange S.A.TransitIPv4 IPv61,858
AS328847THE KONZA TECHNOPOLIS DEVELOPMENT AUTHORITYUnclassifiedIPv4363
AS36866Jamii Telecommunications LimitedUnclassifiedIPv4192
AS328636Jambo telecoms limitedUnclassifiedIPv4182
AS37301(AfriNIC) Ltd - African Network Information Center - (AfriNIC) LtdUnclassifiedIPv432
AS6939Hurricane Electric LLCTransitIPv615

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.