asn.dev

Internet exchange

KG-IX

active Bishkek, Kyrgyzstan FRU

Recorded members 34 addresses on file
Connected ports 34 across all participants
Peak traffic 120 Mbps peak, as recorded
Peering LANs 3 shared subnets

Overview

What this is

recorded

An internet exchange is shared switching where networks interconnect directly instead of paying a transit provider to carry traffic between them. Members take a port on the fabric and an address on the peering LANs below, then agree bilaterally (or through a route server) about which routes to exchange. Turning up at one is a deliberate choice about how a network wants to be reached, which is why exchange presence says something a routing table cannot.

Location
Bishkek, Kyrgyzstan
Region
Asia-Pacific
Airport code
FRU
Status
Active

Everything on this page is what Packet Clearing House had recorded when the directory was collected, not a live view of the fabric. Member counts in particular lag reality, and around 45% of the exchanges in this dataset publish no participant list at all.

Fabric

Peering LANs

3 on file

The shared subnets members take an address on. A network with an interface in one of these blocks is at this exchange by definition, which is what makes exchange presence a recorded fact rather than an inference. Most exchanges run one IPv4 and one IPv6 LAN; extra blocks are usually growth or a migration.

PrefixFamilyStatusParticipants
185.1.110.0/24IPv4Active29
2001:7f8:3c::/48IPv6Planned—
2001:7f8:3c:3e8::/64IPv6Active34

Deprecated and retired blocks are listed rather than dropped. A decommissioned LAN still records how this fabric used to be reached, and filtering it would quietly rewrite the exchange's history.

Participants

Member networks

29 networks · 34 addresses

Every network PCH records with an address on one of the peering LANs above, ordered as the source ranks them: the most-connected participants first. Each network's addresses on the fabric are listed together, IPv4 first. Typing in the box narrows the rows below; Search looks through all 34 recorded addresses.

ASNetworkAddressesrDNSPolicy
AS13335Cloudflare, Inc.185.1.110.93—Open
AS20940Akamai International B.V.185.1.110.90—Open
AS199524G-Core Labs S.A.185.1.110.99——
AS54994Meteverse Limited.185.1.110.92—Open
AS139341ACE185.1.110.91—Open
AS24429Zhejiang Taobao Network Co.,Ltd185.1.110.98——
AS42WoodyNet, Inc.185.1.110.84—Open
AS9198JSC Kazakhtelecom185.1.110.64——
AS25152Reseaux IP Europeens Network Coordination Centre (RIPE NCC)185.1.110.86—Open
AS3856Packet Clearing House, Inc.185.1.110.85—Open
AS8449"ElCat" Ltd.185.1.110.9—Open
AS51346Opened Joint Stock Company "Tojiktelecom"185.1.110.88—Selective
AS197000Reseaux IP Europeens Network Coordination Centre (RIPE NCC)185.1.110.87—Open
AS210756EdgeCenter LLC185.1.110.96—Selective
AS21030Cluster LLC185.1.110.97—Open
AS207353Ruform LLC185.1.110.222—Open
AS61010IPNET OOO185.1.110.55185.1.110.5——Selective
AS47864V-NET B.V.185.1.110.63185.1.110.62——Open
AS29061CJSC SAIMA TELECOM185.1.110.3—Selective
AS61399KG-IX LLC185.1.110.223—Open
AS47237NUR Telecom LLC185.1.110.7185.1.110.27——Open
AS215013Yandex.Cloud LLC185.1.110.81——
AS12997OJSC Kyrgyztelecom185.1.110.11—Selective
AS41750Mega-Line Ltd.185.1.110.1—Selective
AS51898Ak Bulut Soft LLC185.1.110.50—Open
AS207192Anfeya LLC185.1.110.15185.1.110.14——Open
AS207369Skynet Telecom, LLC185.1.110.8—Selective
AS42581Inform Communications Ltd.185.1.110.18—Open
AS65056INTERNET ASSIGNED NAMES AUTHORITY185.1.110.101185.1.110.102——Open

Peering policy is what the network declared to PCH, not something anyone verified, and an open policy is an invitation rather than a commitment. Absence of a network here means PCH has no record of it at this exchange, not that it is not present.

Provenance

Where this comes from

Exchange records come from the directory collected 2026-10-14 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,276 recorded member addresses, licensed CC BY-NC-SA 3.0.

This is a snapshot, not a live view. Members join and leave continuously, and the figures above are what PCH had on file on the collection date. PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.