asn.dev

Internet exchange

National Internet Exchange of Afghanistan

active Kabul, Afghanistan KBL

Recorded members 30 addresses on file
Connected ports 20 across all participants
Peak traffic 920 kbps peak, as recorded
Peering LANs 1 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
Kabul, Afghanistan
Region
Asia-Pacific
Airport code
KBL
Status
Active
PCH record updated
2022-02-28

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

1 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
103.104.146.0/24IPv4Active20

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

30 shown

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. One row per recorded address, so a network running dual-stack appears once for its IPv4 interface and once for its IPv6 one.

ASNetworkAddressrDNSPolicy
AS42WoodyNet, Inc.103.104.146.41Open
AS3856Packet Clearing House, Inc.103.104.146.42Open
AS55330AFGHANTELECOM GOVERNMENT COMMUNICATION NETWORK103.104.146.40
AS138322Afghan Wireless Communication Company103.104.146.43Open
AS131284Etisalat Afghan103.104.146.39
AS45178Main Street, House No. 13 Wazir Akbar Khan103.104.146.45
AS136400Asia Consultancy Group103.104.146.22Open
AS135298Ankabut Internet Service Provider103.104.146.47Open
AS58469Ministry of Communication & IT103.104.146.30
AS58469Ministry of Communication & IT103.104.146.50
AS132471ATOMA103.104.146.44
AS134134Western ICT Solutions Services103.104.146.34Open
AS17411Io Global Services Pvt. Limited103.104.146.48
AS55424Instatelecom Limited103.104.146.64
AS55424Instatelecom Limited103.104.146.25Open
AS59317Afghan Cyber ISP103.104.146.56
AS132222Sanzar F Kakar T/A Afghanistan Holding Group103.104.146.55
AS133202AFSAT103.104.146.58
AS136479Cyber Telecom ISP103.104.146.52Open
AS142541Optix Wave Internet Services103.104.146.61
AS58427Global Entourage Services103.104.146.29Open
AS133066Ariana Network Services Co103.104.146.23Open
AS135376Rahanet Internet Service Provider103.104.146.33Open
AS136454Fiber-SAT ISP Ltd.103.104.146.26Open
AS137824View Net Technology103.104.146.32Open
AS137975Stark Telecom103.104.146.63Open
AS141447Sky Wave Technologies Internet Service103.104.146.62
AS55745NEDA TELECOM103.104.146.24Open
AS137246MINISTRY OF COMM & IT103.104.146.2Open
AS137246MINISTRY OF COMM & IT103.104.146.1Open

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-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 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.