AS50427 ASPA Check - ORIONNET ABK Orion Telecom
PublishedORIONNET-ABK Orion Telecom LLC🇷🇺 - ASPA check for AS50427: the upstream transit providers AS50427 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS50427 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.
How to read this ASPA check
The 6 providers below are the only networks allowed to appear directly above AS50427 in an AS-path. If AS50427 uses a transit provider that is missing from this list, routers that enforce ASPA treat its routes through that provider as invalid, so the list should include every current and backup transit provider. Peers do not belong in it.
Step-by-step ASPA check guide - including how to validate an AS-path hop by hop.
Peering Topology
Upstream Providers(6)
AS50427 authorizes these ASNs as upstream transit providers.
| ASN | Name |
|---|---|
| AS3216 | 🇷🇺SOVAM-AS PJSC "Vimpelcom" |
| AS12389 | 🇷🇺ROSTELECOM-AS PJSC Rostelecom |
| AS31133 | 🇷🇺MF-MGSM-AS PJSC MegaFon |
| AS31257 | 🇷🇺ORIONNET-KRK Orion Telecom LLC |
| AS43298 | 🇷🇺StormNetworks Storm Networks LLC |
| AS48858 | 🇷🇺Milecom-as JSC "ER-Telecom Holding" |
Downstream Customers(1)
These ASNs list AS50427 as an authorized upstream provider.
| ASN | Name |
|---|---|
| AS50022 | 🇷🇺ORIONNET-MNSK Kristelecom Ltd. |
ASPA object expires: 2026-10-27
Related Tools and Guides
- How to run an ASPA check - read and verify an ASPA record step by step
- ASPA explained - how provider authorization stops route leaks
- ASPA Check tool - check the ASPA record of any other ASN
- RPKI & ROA Lookup - validate prefixes and check ASPA records for any ASN
- Global ASPA Adoption Statistics - transit-free ASNs, top upstream providers, adoption trends
- AS50427 Overview - prefixes, BGP routes, peers, and RPKI status