AS50022 ASPA Check - ORIONNET MNSK Kristelecom

Published

ORIONNET-MNSK Kristelecom Ltd.🇷🇺 - ASPA check for AS50022: the upstream transit providers AS50022 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS50022 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.

ASPA Status
Published
Upstream Providers
3
Downstream Customers
0

How to read this ASPA check

The 3 providers below are the only networks allowed to appear directly above AS50022 in an AS-path. If AS50022 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

AS50022 peering topology: 3 upstream providers and 0 downstream customersUpstreams: AS3216, AS20485, AS50427. No downstreams.AS50022 - ORIONNET-MNSK Kristelecom Ltd.AS50022ORIONNET-MNSK Kristel…AS3216SOVAM-AS PJSC Vimpelc…AS3216 - SOVAM-AS PJSC VimpelcomAS20485TRANSTELECOM Joint St…AS20485 - TRANSTELECOM Joint Stock Company TransTeleComAS50427ORIONNET-ABK Orion Te…AS50427 - ORIONNET-ABK Orion Telecom LLCUPSTREAMSDOWNSTREAMS

Upstream Providers(3)

AS50022 authorizes these ASNs as upstream transit providers.

ASNName
AS3216🇷🇺SOVAM-AS PJSC "Vimpelcom"
AS20485🇷🇺TRANSTELECOM Joint Stock Company TransTeleCom
AS50427🇷🇺ORIONNET-ABK Orion Telecom LLC

ASPA object expires: 2026-10-27

Related Tools and Guides

← Back to AS50022