asn.dev

Observed topology

AS12997 KTNET OJSC Kyrgyztelecom

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12997: 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
AS8449"ElCat" Ltd.UnclassifiedIPv4 IPv62,175

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39659State institution "Kyzmat" under the Office of the President of the Kyrgyz RepublicUnclassifiedIPv4126
AS44836Institution "State Tax Service under the Cabinet of Ministers of the Kyrgyz Republic"UnclassifiedIPv463

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8449"ElCat" Ltd.UnclassifiedIPv4 IPv62,364
AS39659State institution "Kyzmat" under the Office of the President of the Kyrgyz RepublicUnclassifiedIPv4126
AS44836Institution "State Tax Service under the Cabinet of Ministers of the Kyrgyz Republic"UnclassifiedIPv463

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.