asn.dev

Observed topology

AS9129 KE-NET2000

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS9129: 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
AS16637MTN SAMobileIPv4 IPv64,101

Transit

Downstream networks

All 29

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

ASNetworkTypeFamiliesPaths seen
AS329272Servercore Africa LtdUnclassifiedIPv4582
AS329600Elegant Telekom LimitedUnclassifiedIPv4 IPv6465
AS329622KONNEKT Smart Life LTDUnclassifiedIPv4462
AS328490Unwired Communications LimitedUnclassifiedIPv4 IPv6401
AS3277864G TelecomUnclassifiedIPv4399
AS328753Zeplin Investments LtdResidentialIPv4330
AS329621Gawia LtdUnclassifiedIPv4 IPv6231
AS328987Lime Emerging Solutions LimitedUnclassifiedIPv4 IPv6169
AS37129RasmilinkResidentialIPv4159
AS37406RCS-CommunicationUnclassifiedIPv4151

All 29 downstreams →

Adjacency

Adjacent networks

All 30

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

ASNetworkTypeFamiliesPaths seen
AS16637MTN SAMobileIPv4 IPv69,831
AS3277864G TelecomUnclassifiedIPv4727
AS328490Unwired Communications LimitedUnclassifiedIPv4 IPv6635
AS329621Gawia LtdUnclassifiedIPv4 IPv6622
AS329272Servercore Africa LtdUnclassifiedIPv4582
AS329600Elegant Telekom LimitedUnclassifiedIPv4 IPv6465
AS329622KONNEKT Smart Life LTDUnclassifiedIPv4462
AS328753Zeplin Investments LtdResidentialIPv4330
AS328987Lime Emerging Solutions LimitedUnclassifiedIPv4 IPv6169
AS37129RasmilinkResidentialIPv4159

All 30 adjacent →

Provenance

Where this comes from

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