AS39199 RADIONET Private Enterprise RadioNet
🇺🇦Org handle: ORG-PER1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
10total
10 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)2,048
Announced (BGP)4,096
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)10|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.218.88.0/22 | 🇺🇦 UA | RIPENCC | assigned |
| 195.34.204.0/22 | 🇺🇦 UA | RIPENCC | assigned |
All 10 announced prefixes of AS39199 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS39199 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (7)
Networks whose own prefixes AS39199 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS39199 in the transit part of AS paths: peers, providers or customers.
- AS9002RETN Limited2
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 AS39199 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/39199Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/39199" | jq