ixreport

KazNIX: operator report

Semey, Kazakhstan · PeeringDB 2497 · ixreport.com/ix/2497/report/

Download CSV

Members of KazNIX that PeeringDB has wrong, from its IX-F export (17 networks, read 2026-10-08 22:05 UTC) and its website members list (15 networks, read 2026-10-08 22:05 UTC), against PeeringDB as of 2026-10-08 22:13 UTC. 6 networks to follow up; 1 with a public PeeringDB contact.

Contacts are the networks' public PeeringDB contacts: the peering (policy) contact where there is one, else technical, then NOC. Networks keep these themselves on PeeringDB.

On your lists, missing from PeeringDB (5)

These networks could add KazNIX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.

NetworkOn yourAddressesContact
AS8393 ASTEL JSC PeeringDBIX-F and website 185.79.213.6
10G
Technical: email address (needs JavaScript) +77272379001
AS39824 JSC Alma Telecommunications PeeringDBIX-F and website 185.79.213.4
185.79.213.18
2a01:7640:9400::4
2a01:7640:9400::18
1G
No public contact
AS58172 Freedom Telecom AS58172 PeeringDBIX-F and website 185.79.213.16
2a01:7640:9400::16
10G
No public contact
AS203530 7satIX-F and website 185.79.213.17
185.79.213.117
2a01:7640:9400::17
2a01:7640:9400::117
10G
No PeeringDB record
AS203911 Kazakh Home Networks LLPIX-F –
10G
No PeeringDB record

Addresses or port speeds that differ (1)

PeeringDB against your IX-F export, for the 12 networks in both. Either the network's PeeringDB record or the export is out of date.

NetworkProblemPeeringDB hasYour export hasContact
AS42909 CommunityDNS Ltd PeeringDB Port speed differs10G1G No public contact

In PeeringDB, not on your lists (0)

Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.

None.