AS214500 MULTICL-KZ-AS CLOUD PLATFORM LLP
🇰🇿Org handle: ORG-CPL36-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)0
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 93.180.129.0/24 | 🇰🇿 KZ | RIPENCC | allocated |
| 93.180.131.0/24 | 🇰🇿 KZ | RIPENCC | allocated |
| 2a14:7c40::/32 | 🇰🇿 KZ | RIPENCC | allocated |
All 2 announced prefixes of AS214500 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS214500 hands its own prefixes to: transit providers, or peers at an exchange.
- AS43370OBIT KZ OBIT Telecommunications2
ASPA
No ASPA
Abuse Contact
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS214500 should publish an ASPA object
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/214500Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/214500" | jq