AS16125 CHERRYSERVERS1-AS UAB "Cherry Servers"
🇱🇹Org handle: ORG-UDC69-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
81total
80 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)26,624
Announced (BGP)39,168
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)4.9×10²⁷
Routing hygiene
Score 30/100 · Medium riskRPKI ROA coverage
85.2%
6 prefixes RPKI invalid
IRR route objects
90.1%
3 prefixes registered for another origin
Hijack signals
3
3 announced against others' ROAs, 0 own announced by others
Upstreams
4
diversity 48/100
- Announces 3 prefixes that RPKI assigns to another network (possible hijack or misconfiguration)
- 15% of announced prefixes (12 of 81) have no valid ROA, 6 of them RPKI invalid
Based on 81 announced prefixes, updated daily (2026-10-24). How the score works · RPKI explained
Listed on the threat map (2026-10-24)
Large hosting providers appear because attackers rent their servers, not necessarily because of the operator.
Announced Prefixes
(BGP)81|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | Other IRRRIPE | 2026-10-26 | |
| Valid | ARINOther IRR | 2026-10-26 | |
| Valid | ARINOther IRR | 2026-10-26 | |
| Valid | ARINOther IRR | 2026-10-26 |
1-10 of 81
1 / 9
Allocated Prefixes
(RIR)55Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.199.170.0/24 | 🇱🇹 LT | RIPE | assigned |
| 45.10.158.0/23 | 🇳🇱 NL | RIPE | assigned |
| 45.196.31.0/24 | 🇨🇴 CO | AFRINIC | assigned |
| 46.166.162.0/24 | 🇱🇹 LT | RIPE | assigned |
| 46.166.166.0/24 | 🇱🇹 LT | RIPE | assigned |
| 79.180.124.0/24 | 🇬🇧 GB | RIPE | assigned |
| 82.23.2.0/24 | 🇱🇹 LT | RIPE | assigned |
| 82.206.0.0/23 | 🇺🇸 US | RIPE | assigned |
| 82.206.10.0/23 | 🇺🇸 US | RIPE | assigned |
| 84.32.9.0/24 | 🇱🇹 LT | RIPE | assigned |
1-10 of 55
1 / 6
All 81 announced prefixes of AS16125 →
BGP Neighbours
(seen in AS paths)Upstreams (4)
Networks AS16125 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS16125 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/16125Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/16125" | jq