Autonomous system
AS59583 ASNETKAZAHSTAN
Unclassified APNIC
Summary
Network Kazakhstan
voip isp business
ASNETKAZAHSTAN is operated by Network Kazakhstan LLC.
What it's used for
- The address space carries VoIP and client services, evidenced by netnames
KZ-VOIP-20120615,KZ-VOIP-20140220,KZ-VOIP-20170221,KZ-VOIP-20060705,NETKZ_ALMATY_CLIENTS, andNETKZ_NUR-SULTAN_CLIENTS. - The AS announces 5888 IPv4 addresses across 8 prefixes with 7 observed neighbours, a ratio consistent with an access or service provider role rather than a transit backbone.
- Traffic from this AS consists of VoIP media and signalling, as well as client connectivity for businesses and individuals in Almaty and Nur-Sultan.
Notable
- Registrants for all prefixes are
Network Kazakhstan LLC Network Operations CenterorNetwork Kazakhstan LLC, aligning with the AS holder. - The inventory includes a mix of VoIP-specific blocks and general client blocks, with one prefix (
195.88.2.0/23) also listingTelService Ltd.as a registrant. - The address inventory is composed of eight distinct IPv4 prefixes, all located in Kazakhstan, with no IPv6 prefixes in the inventory.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-11, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 8 prefixes · 5.89K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| KZ | Kazakhstan | 8 |
Registry
Allocation record
- Registry
- APNIC
- Handle
AS59583- Registry name
- ASNETKAZAHSTAN
- Registrant
- NETKZ-MNT
- Abuse contact
- abuse@voip.kz
- Registered
- 2012-08-14
- Last changed
- 2022-12-14
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Network Kazakhstan
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- IRR as-set
AS-NETKAZ-PEERS
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 0% valid · 0 valid, 23 with no ROA
- ROAs
- 0 authorising AS59583
- ASPA
- no ASPA record
- IRR
- 100% registered · 23 of 23 announcements
- Route objects
- 26 naming AS59583
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 432 networks and 1,768 prefixes, as published 2026-10-12. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere