Autonomous system
AS39221 ITOOLABS Cloud PBX Solutions TOO
Unclassified RIPE
Summary
Cloud PBX Solutions
voip cloud pbx business
ITOOLABS is operated by Cloud PBX Solutions TOO.
What it's used for
- The address space carries VoIP and unified communications traffic, evidenced by the netname
CPSand registrantCloud PBX Solution NOCon both announced IPv4 prefixes. - The AS announces 1280 IPv4 addresses across 2 prefixes and 2 IPv6 prefixes, with only 3 observed neighbours, indicating a small-scale service provider or internal corporate estate rather than a transit hub.
- Traffic from this AS consists of VoIP media and signalling for cloud-based PBX systems, supporting enterprise telephony, call routing, and unified communications services.
Notable
- Registrants for both IPv4 prefixes are
Cloud PBX Solution NOC, which aligns with the AS holderCloud PBX Solutions TOOand the AS handleITOOLABS. - The address inventory is compact, consisting of one /22 and one /24 block in IPv4, and two /48 blocks in IPv6, all located in Kazakhstan.
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-11-07, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 2 prefixes · 1.28K addresses IPv6 2 prefixes
| Country | Name | Prefixes |
|---|---|---|
| KZ | Kazakhstan | 4 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS39221- Registry name
- ITOOLABS
- Registrant
- CPS-MNT
- Abuse contact
- info@cloud-pbx.io
- Registered
- 2009-10-16
- Last changed
- 2022-08-18
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Itoolabs AS 39221
- Scope
- Regional
- Traffic ratio
- Balanced
- Peering policy
- Open
- IRR as-set
AS-ITOOLABS- Facilities
- 1 facilities
- Website
- http://www.itoolabs.com
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, 4 with no ROA
- ROAs
- 0 authorising AS39221
- ASPA
- no ASPA record
- IRR
- 100% registered · 4 of 4 announcements
- Route objects
- 6 naming AS39221
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: 454 networks and 1,852 prefixes, as published 2026-11-08. 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