AS39728 Luganet Likhno Dmitriy trading as Luganet
🇷🇺Org handle: ORG-LD123-RIPE
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
17total
17 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)23,808
Announced (BGP)24,576
IPv6 Addresses
Allocated (RIR)1.2×10³⁰
Announced (BGP)0
Routing hygiene
Score 5/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
2
diversity 46/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 17 announced prefixes, updated daily (2026-10-25). How the score works · RPKI explained
Announced Prefixes
(BGP)17|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - |
1-10 of 17
1 / 2
Allocated Prefixes
(RIR)12Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.152.24.0/22 | 🇷🇺 RU | RIPENCC | allocated |
| 91.217.4.0/23 | 🇷🇺 RU | RIPENCC | assigned |
| 176.113.224.0/19 | 🇷🇺 RU | RIPENCC | assigned |
| 178.214.160.0/19 | 🇷🇺 RU | RIPENCC | assigned |
| 178.216.232.0/21 | 🇷🇺 RU | RIPENCC | assigned |
| 185.149.196.0/22 | 🇷🇺 RU | RIPENCC | allocated |
| 185.178.244.0/22 | 🇷🇺 RU | RIPENCC | allocated |
| 194.31.152.0/22 | 🇷🇺 RU | RIPENCC | allocated |
| 194.31.155.0/24 | 🇷🇺 RU | RIPE | assigned |
| 195.8.56.0/23 | 🇷🇺 RU | RIPENCC | assigned |
1-10 of 12
1 / 2
All 17 announced prefixes of AS39728 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS39728 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (6)
Networks whose own prefixes AS39728 passes on: usually its customers.
Transfer History
Registry transfers of AS39728 between organisations.
- AS39728Transfer ·
- AS39728Transfer ·
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/39728Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/39728" | jq