AS39130 UA-LANPLUSNET PP Merezha plus
🇺🇦Org handle: ORG-MPP6-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)2,816
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)0
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-09 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.102.36.0/22 | 🇺🇦 UA | RIPENCC | allocated |
| 195.5.124.0/23 | 🇺🇦 UA | RIPENCC | allocated |
| 195.5.124.0/24 | 🇺🇦 UA | RIPE | assigned |
| 195.222.124.0/22 | 🇺🇦 UA | RIPENCC | allocated |
| 2a10:d80::/29 | 🇺🇦 UA | RIPENCC | allocated |
All 1 announced prefix of AS39130 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS39130 hands its own prefixes to: transit providers, or peers at an exchange.
- AS3326Datagroup PRIVATE JOINT STOCK COMPANY "DATAGROUP"1
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 AS39130 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/39130Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/39130" | jq