AS39608 LANETUA-AS Lanet Network Ltd
🇺🇦Org handle: ORG-LNL15-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
16total
16 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)200,448
Announced (BGP)204,032
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Listed on the threat map (2026-10-09)
Large hosting providers appear because attackers rent their servers, not necessarily because of the operator.
Announced Prefixes
(BGP)16|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 |
1-10 of 16
1 / 2
Allocated Prefixes
(RIR)11Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.216.165.0/24 | 🇺🇦 UA | RIPENCC | assigned |
| 176.36.0.0/16 | 🇺🇦 UA | RIPE | assigned |
| 176.37.0.0/16 | 🇺🇦 UA | RIPE | assigned |
| 176.38.0.0/16 | 🇺🇦 UA | RIPE | assigned |
| 185.53.76.0/23 | 🇺🇦 UA | RIPENCC | allocated |
| 185.53.78.0/24 | 🇺🇦 UA | RIPENCC | allocated |
| 193.93.160.0/22 | 🇺🇦 UA | RIPENCC | assigned |
| 193.107.224.0/22 | 🇺🇦 UA | RIPENCC | assigned |
| 194.33.189.0/24 | 🇺🇦 UA | RIPENCC | assigned |
| 194.50.85.0/24 | 🇺🇦 UA | RIPENCC | assigned |
1-10 of 11
1 / 2
All 16 announced prefixes of AS39608 →
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS39608 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (12)
Networks whose own prefixes AS39608 passes on: usually its customers.
- AS49332MKC Lanet Network25
- AS41911LANET SD Lanet Network13
- AS202103LANET RV Lanet Network11
- AS33817TELEGROUPUA Lanet4
- AS205673UATEL Lanet Network4
- AS43120LANET VN Lanet Network3
- AS47475LANET TV Lanet Network2
- AS51180LANET KL Lanet Network2
- AS13121NAVIGATOR Lanet1
- AS29342KIYAVIA CJSC 'Kiy Avia'1
- AS41781PPNET NPS1
- AS57985NIKO UA Corporation 'Niko Management'1
Other adjacent networks (1)
Adjacent to AS39608 in the transit part of AS paths: peers, providers or customers.
- AS9002RETN Limited5
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 AS39608 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/39608Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/39608" | jq