AS21282 KAZNIC-AS KazNIC Organization
🇰🇿Org handle: ORG-KO2-RIPE
Internet Service Provider
RIPE NCCallocated
Announced Prefixes (BGP)
6total
4 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)4,352
Announced (BGP)4,864
IPv6 Addresses
Allocated (RIR)1.2×10²⁷
Announced (BGP)1.2×10²⁷
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-08 | |
| Valid | - | 2026-10-08 | |
| Valid | RIPE | 2026-10-08 | |
| Valid | RIPE | 2026-10-08 | |
| Valid | RIPE | 2026-10-08 | |
| Valid | RIPE | 2026-10-08 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 80.241.0.0/20 | 🇰🇿 KZ | RIPENCC | allocated |
| 80.241.3.0/24 | 🇰🇿 KZ | RIPE | assigned |
| 2a01:7640::/38 | 🇰🇿 KZ | RIPE | assigned |
All 6 announced prefixes of AS21282 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS21282 hands its own prefixes to: transit providers, or peers at an exchange.
- AS9198KAZTELECOM JSC Kazakhtelecom3
Downstreams (4)
Networks whose own prefixes AS21282 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS21282 in the transit part of AS paths: peers, providers or customers.
- AS35168TNS Plus Core TNS Plus LLP8
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 AS21282 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/21282Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/21282" | jq