AS50427 ORIONNET-ABK Orion Telecom LLC
🇷🇺Org handle: ORG-MNL1-RIPE
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
27total
26 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)4,352
Announced (BGP)13,568
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)1.9×10²⁸
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
4
diversity 51/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 27 announced prefixes, updated daily (2026-10-22). How the score works · RPKI explained
Announced Prefixes
(BGP)27|
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 | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
1-10 of 27
1 / 3
Allocated Prefixes
(RIR)8Prefix | Country | RIR | Status |
|---|---|---|---|
| 86.62.4.0/24 | 🇷🇺 RU | RIPE | assigned |
| 86.62.5.0/24 | 🇷🇺 RU | RIPE | assigned |
| 109.226.248.0/24 | 🇷🇺 RU | RIPE | assigned |
| 185.84.174.0/23 | 🇷🇺 RU | RIPE | assigned |
| 185.112.224.0/22 | 🇷🇺 RU | RIPENCC | allocated |
| 185.112.224.0/23 | 🇷🇺 RU | RIPE | assigned |
| 185.112.226.0/23 | 🇷🇺 RU | RIPE | assigned |
| 193.106.168.0/22 | 🇷🇺 RU | RIPENCC | assigned |
All 27 announced prefixes of AS50427 →
Upstream Providers(6)
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS50022 | 🇷🇺ORIONNET-MNSK Kristelecom Ltd. |
BGP Neighbours
(seen in AS paths)Upstreams (4)
Networks AS50427 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS50427 passes on: usually its customers.
- AS50022ORIONNET MNSK Kristelecom3
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/50427Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/50427" | jq