AS39512 NKTV-AS Mykolaivske Kabelne Telebachennia TOV
🇺🇦Org handle: ORG-NL62-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)5,120
Announced (BGP)4,096
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 81.24.208.0/20 | 🇺🇦 UA | RIPENCC | allocated |
| 194.35.60.0/22 | 🇺🇦 UA | RIPENCC | allocated |
| 2a00:c200::/32 | 🇺🇦 UA | RIPENCC | allocated |
All 2 announced prefixes of AS39512 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS39512 hands its own prefixes to: transit providers, or peers at an exchange.
- AS35297DATALINE2
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 AS39512 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/39512Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/39512" | jq