Who's on KazNIX, by source
11 of 17 match: 11 in every source1 in PeeringDB, but on only one of the IX-F list and the website list5 published by the exchange, not in PeeringDB
IX-F export: https://ixp.kaznix.kz/api/v4/member-export/ixf/, read 2026-11-19 12:22 UTC.
Members list on the website: http://kaznix.kz/ru/clients, read 2026-11-19 12:22 UTC.
Ports and fees
| Port | Price | Billed | In use |
|---|---|---|---|
| 1G | – | – | 6 |
| 10G | – | – | 12 |
Every port speed KazNIX lists (we haven't found its price list), plus every speed members are connected at (from its IX-F export).
We couldn't find KazNIX's port fees on its website.
How members connect
- In its IX-F export
- 0 by tunnel, 0 on a physical port, 17 not given
- Facilities it lists
- 1 in PeeringDB
- Members with a building in Kazakhstan
- 5 of the 10 members that list any building in PeeringDB (17 members in all)
- Members' countries
- 4 (where their organizations are, in PeeringDB)
Members over time
Show as a table
| Date | IX-F | Website | PeeringDB |
|---|---|---|---|
| Nov 19, 2026 | 17 | 15 | 12 |
| Nov 18, 2026 | 17 | 15 | 12 |
| Nov 17, 2026 | 17 | 15 | 12 |
| Nov 16, 2026 | 17 | 15 | 12 |
| Nov 15, 2026 | 17 | 15 | 12 |
| Nov 14, 2026 | 17 | 15 | 12 |
| Nov 13, 2026 | 17 | 15 | 12 |
| Nov 12, 2026 | 17 | 15 | 12 |
| Nov 11, 2026 | 17 | 15 | 12 |
| Nov 10, 2026 | 17 | 15 | 12 |
| Nov 9, 2026 | 17 | 15 | 12 |
| Nov 8, 2026 | 17 | 15 | 12 |
| Nov 7, 2026 | 17 | 15 | 12 |
| Nov 6, 2026 | 17 | 15 | 12 |
| Nov 5, 2026 | 17 | 15 | 12 |
| Nov 4, 2026 | 17 | 15 | 12 |
| Nov 3, 2026 | 17 | 15 | 12 |
| Nov 2, 2026 | 17 | 15 | 12 |
| Nov 1, 2026 | 17 | 15 | 12 |
| Oct 31, 2026 | 17 | 15 | 12 |
| Oct 30, 2026 | 17 | 15 | 12 |
| Oct 29, 2026 | 17 | 15 | 12 |
| Oct 28, 2026 | 17 | 15 | 12 |
| Oct 27, 2026 | 17 | 15 | 12 |
| Oct 26, 2026 | 17 | 15 | 12 |
| Oct 25, 2026 | 17 | 15 | 12 |
| Oct 24, 2026 | 17 | 15 | 12 |
| Oct 23, 2026 | 17 | 15 | 12 |
| Oct 22, 2026 | 17 | 15 | 12 |
| Oct 21, 2026 | 17 | 15 | 12 |
| Oct 20, 2026 | 17 | 15 | 12 |
| Oct 19, 2026 | 17 | 15 | 12 |
| Oct 18, 2026 | 17 | 15 | 12 |
| Oct 17, 2026 | 17 | 15 | 12 |
| Oct 16, 2026 | 17 | 15 | 12 |
| Oct 15, 2026 | 17 | 15 | 12 |
| Oct 14, 2026 | 17 | 15 | 12 |
| Oct 13, 2026 | 17 | 15 | 12 |
| Oct 12, 2026 | 17 | 15 | 12 |
| Oct 11, 2026 | 17 | 15 | 12 |
| Oct 10, 2026 | 17 | 15 | 12 |
| Oct 9, 2026 | 17 | 15 | 12 |
| Oct 8, 2026 | 17 | 15 | 12 |
| Oct 7, 2026 | 17 | 15 | 12 |
| Oct 6, 2026 | 17 | 15 | 12 |
| Oct 5, 2026 | 17 | 15 | 12 |
| Oct 4, 2026 | 17 | 15 | 12 |
| Oct 3, 2026 | 17 | 15 | 12 |
| Oct 2, 2026 | – | – | 12 |
Traffic, last week
Show as a table
| Time | Traffic |
|---|---|
| Thu Nov 19, 11:00 UTC | 2.71 Gbps |
| Thu Nov 19, 05:00 UTC | 2.11 Gbps |
| Wed Nov 18, 23:00 UTC | 867 Mbps |
| Wed Nov 18, 17:00 UTC | 3.74 Gbps |
| Wed Nov 18, 11:00 UTC | 2.71 Gbps |
| Wed Nov 18, 05:00 UTC | 2.02 Gbps |
| Tue Nov 17, 23:00 UTC | 755 Mbps |
| Tue Nov 17, 17:00 UTC | 3.9 Gbps |
| Tue Nov 17, 11:00 UTC | 2.59 Gbps |
| Tue Nov 17, 05:00 UTC | 2.26 Gbps |
| Mon Nov 16, 23:00 UTC | 803 Mbps |
| Mon Nov 16, 17:00 UTC | 3.96 Gbps |
| Mon Nov 16, 11:00 UTC | 2.77 Gbps |
| Mon Nov 16, 05:00 UTC | 2.05 Gbps |
| Sun Nov 15, 23:00 UTC | 749 Mbps |
| Sun Nov 15, 17:00 UTC | 3.49 Gbps |
| Sun Nov 15, 11:00 UTC | 3.61 Gbps |
| Sun Nov 15, 05:00 UTC | 2.08 Gbps |
| Sat Nov 14, 23:00 UTC | 1.1 Gbps |
| Sat Nov 14, 17:00 UTC | 3.77 Gbps |
| Sat Nov 14, 11:00 UTC | 2.91 Gbps |
| Sat Nov 14, 05:00 UTC | 2.49 Gbps |
| Fri Nov 13, 23:00 UTC | 941 Mbps |
| Fri Nov 13, 17:00 UTC | 3.92 Gbps |
| Fri Nov 13, 11:00 UTC | 2.84 Gbps |
| Fri Nov 13, 05:00 UTC | 1.95 Gbps |
| Thu Nov 12, 23:00 UTC | 878 Mbps |
| Thu Nov 12, 17:00 UTC | 3.85 Gbps |
Daily peak over time
The highest point each day on the traffic graph KazNIX publishes, for every complete day read.
Show as a table
| Date | Daily peak |
|---|---|
| Nov 18, 2026 | 3.87 Gbps |
| Nov 17, 2026 | 4.22 Gbps |
| Nov 16, 2026 | 4.32 Gbps |
| Nov 15, 2026 | 3.85 Gbps |
| Nov 14, 2026 | 4.02 Gbps |
| Nov 13, 2026 | 4.1 Gbps |
| Nov 12, 2026 | 3.85 Gbps |
| Nov 11, 2026 | 3.94 Gbps |
| Nov 10, 2026 | 3.8 Gbps |
| Nov 9, 2026 | 3.63 Gbps |
| Nov 8, 2026 | 3.53 Gbps |
| Nov 7, 2026 | 3.76 Gbps |
| Nov 6, 2026 | 3.76 Gbps |
| Nov 5, 2026 | 4.08 Gbps |
| Nov 4, 2026 | 4.12 Gbps |
| Nov 3, 2026 | 4.45 Gbps |
| Nov 2, 2026 | 3.95 Gbps |
| Nov 1, 2026 | 4.02 Gbps |
| Oct 31, 2026 | 3.86 Gbps |
| Oct 30, 2026 | 3.66 Gbps |
| Oct 29, 2026 | 3.89 Gbps |
| Oct 28, 2026 | 4.03 Gbps |
| Oct 27, 2026 | 3.72 Gbps |
| Oct 26, 2026 | 3.81 Gbps |
| Oct 25, 2026 | 3.6 Gbps |
| Oct 24, 2026 | 3.97 Gbps |
| Oct 23, 2026 | 3.93 Gbps |
| Oct 22, 2026 | 3.61 Gbps |
| Oct 21, 2026 | 3.9 Gbps |
| Oct 20, 2026 | 3.89 Gbps |
| Oct 19, 2026 | 3.57 Gbps |
| Oct 18, 2026 | 3.56 Gbps |
| Oct 17, 2026 | 3.87 Gbps |
| Oct 16, 2026 | 3.62 Gbps |
| Oct 15, 2026 | 3.33 Gbps |
| Oct 14, 2026 | 3.85 Gbps |
| Oct 13, 2026 | 3.52 Gbps |
| Oct 12, 2026 | 3.56 Gbps |
| Oct 11, 2026 | 3.78 Gbps |
| Oct 10, 2026 | 3.74 Gbps |
| Oct 9, 2026 | 3.69 Gbps |
| Oct 8, 2026 | 3.51 Gbps |
| Oct 7, 2026 | 3.37 Gbps |
| Oct 6, 2026 | 3.64 Gbps |
| Oct 5, 2026 | 3.61 Gbps |
| Oct 4, 2026 | 3.7 Gbps |
| Oct 3, 2026 | 3.52 Gbps |
| Oct 2, 2026 | 3.41 Gbps |
Published by KazNIX: source, read 2026-11-19 12:23 UTC.
Exchange details
- Media
- Ethernet
- Protocols
- Unicast IPv4, IPv6
- MTU
- 1500
- Service level
- 24/7 Support
- Terms
- No Commercial Terms
- Traffic stats
- kaznix.kz/ru/monitoring
- Technical
- noc@nic.kz
- Policy
- ixp-request@nic.kz
- PeeringDB record
- Updated 2022-04-06
Peering LAN prefixes
- 185.79.213.0/24IPv4
- 2a01:7640:9400::/64IPv6
Facilities (1)
- KazNICSemey
Route servers
15 networks have a session up with KazNIX's route servers, and 15 of them send routes: evidence they're really connected and peering, not just listed. Networks that only peer directly (bilaterally) don't show here. The routes column in the table below has each network's count.
From the public looking glass at ixp.kaznix.kz/lg (rs1-lan1-ipv4, rs1-lan1-ipv6), read 2026-11-18 18:37 UTC; one route server per address family, IPv4 and IPv6 counted together. How this is read
Data status
What the last update (every 6 hours) found for KazNIX, step by step.
- IX-F export in PeeringDB The exchange hasn't published an IX-F export URL in PeeringDB.
- IX-F database (IXPDB) https://ixp.kaznix.kz/api/v4/member-export/ixf/
- Website search Members page already known (checked 2026-11-17).
- Member list Read 2026-11-19 12:22 UTC from the IX-F export.
- Member page 15 networks on http://kaznix.kz/ru/clients (its AS-number column), read 2026-11-19.
- Port fees No fees page found on the exchange's website yet (searched weekly).
- Route server looking glass 15 sessions up on rs1-lan1-ipv4, rs1-lan1-ipv6, read 2026-11-18 18:37 UTC from https://ixp.kaznix.kz/lg.
Fix list
Networks where PeeringDB and what KazNIX publishes (its IX-F export and its website's members list) disagree. Download CSV Operator report with contacts
Published by the exchange, missing from PeeringDB (5)
These networks could add KazNIX to their PeeringDB record.
Only in PeeringDB (0)
Either the exchange's lists are missing them, or their PeeringDB record is out of date.
- None
Addresses and port speeds
Each network's IP addresses and port speed in PeeringDB, against KazNIX's IX-F export, for the 12 networks in both. 1 has differences. Download CSV Operator report with contacts
PeeringDB's IX-F import is on for KazNIX. PeeringDB suggests these corrections to the networks (and makes them for networks that allow it).
Port speed differs (1)
| AS42909 CommunityDNS Ltd | 10G | 1G |
| AS42 | PCH AS42Exchange lists it as “Packet Clearing House AS42” | 185.79.213.38 | 10G | PeeringDB IX-FWebsite |
| AS3856 | PCH AS3856Exchange lists it as “Packet Clearing House” | 185.79.213.37 | 1G | PeeringDB IX-FWebsite |
| AS8393 | ASTEL JSC | 185.79.213.6 | 10G | PeeringDB IX-FWebsiteNot in PeeringDB |
| AS8674 | Netnod | 185.79.213.15 | 10G | PeeringDB IX-FWebsite |
| AS21282 | KazNIC SemeyExchange lists it as “KazNIC Organization” | 185.79.213.2 | 20G | PeeringDB IX-FWebsite |
| AS25152 | RIPE NCC K-Root Operations | 185.79.213.9 | 1G | PeeringDB IX-FWebsite |
| AS35168 | TNS-Plus Core | 185.79.213.14 | 10G | PeeringDB IX-FWebsite |
| AS39824 | JSC Alma Telecommunications | 185.79.213.4 185.79.213.18 |
1G | PeeringDB IX-FWebsiteNot in PeeringDB |
| AS41798 | Transtelecom Kazakhstan | 185.79.213.3 | 10G | PeeringDB IX-FWebsite |
| AS42385 | IXDNS | 185.79.213.8 | 10G | PeeringDB IX-FWebsite |
| AS42909 | CommunityDNS Ltd | 185.79.213.68 | 10G | PeeringDB IX-FWebsite |
| AS48503 | Tele2 KazakhstanExchange lists it as “Mobile Telecom Service LLP” | 185.79.213.5 | 10G | PeeringDB IX-FWebsite |
| AS51833 | KazNIC anycast 1Exchange lists it as “Anycast ccTLD DNS” | 185.79.213.12 | 1G | PeeringDB IX-FWebsite |
| AS58172 | Freedom Telecom AS58172Exchange lists it as “Freedom Telecom” | 185.79.213.16 | 10G | PeeringDB IX-FWebsiteNot in PeeringDB |
| AS203530 | 7sat | 185.79.213.17 185.79.213.117 |
10G | PeeringDB IX-FWebsiteNot in PeeringDB |
| AS203911 | Kazakh Home Networks LLP | 10G | PeeringDB IX-FWebsiteNot in PeeringDB | |
| AS206768 | KazNIC anycast 2Exchange lists it as “Anycast2 ccTLD DNS” | 185.79.213.11 | 1G | PeeringDB IX-FWebsite |