Autonomous system
AS41124 BTCOM
Unclassified RIPE
Summary
BTcom
telecom residential business kzt
The AS handle BTCOM is held by BTcom Infocommunications Ltd.
What it's used for
- The address space carries netnames such as
BAZIS-TELECOM-NETandKZ-BAZIS-TELECOM-20060426, indicating a telecommunications infrastructure estate. - The AS announces 13,824 IPv4 addresses across 12 prefixes with 4 observed neighbours, a ratio consistent with an access network serving local subscribers rather than a transit provider.
- As a leading communication service provider in Kazakhstan, the traffic consists of subscriber eyeballs and business connectivity for local enterprises.
Notable
- All registrants align with the announcer, listing
BTcom Infocommunications Ltd.and its Astana Branch NOC. - The inventory is composed of multiple /22 and /21 blocks, reflecting a segmented corporate estate for different service regions or customer segments.
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 12 prefixes · 13.82K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| KZ | Kazakhstan | 12 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS41124- Registry name
- BTCOM
- Registrant
- BTcom Infocommunications Ltd.
- Abuse contact
- abuse@btcom.kz
- Registered
- 2006-06-16
- Last changed
- 2023-08-17
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- BTcom Infocommunications
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
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
- 100% valid · 54 valid, 0 with no ROA
- ROAs
- 22 authorising AS41124
- ASPA
- no ASPA record
- IRR
- 100% registered · 54 of 54 announcements
- Route objects
- 47 naming AS41124
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: 431 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