AS50022 ORIONNET-MNSK Kristelecom Ltd.
🇷🇺Org handle: ORG-KL61-RIPE
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)13,824
Announced (BGP)4,608
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Routing hygiene
Score 10/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
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
Based on 3 announced prefixes, updated daily (2026-10-27). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 176.116.160.0/19 | 🇷🇺 RU | RIPENCC | assigned |
| 213.110.232.0/22 | 🇷🇺 RU | RIPENCC | assigned |
| 213.110.236.0/23 | 🇷🇺 RU | RIPENCC | assigned |
| 213.110.240.0/20 | 🇷🇺 RU | RIPENCC | assigned |
All 3 announced prefixes of AS50022 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS50022 hands its own prefixes to: transit providers, or peers at an exchange.
- AS50427ORIONNET ABK Orion Telecom3
Abuse Contact
+31205354444
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/50022Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/50022" | jq