AS205901 ASPA Check - RUSK Evgenii Diakov

Published

RUSK-AS Evgenii Diakov🇬🇪 - ASPA check for AS205901: the upstream transit providers AS205901 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS205901 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.

ASPA Status
Published
Upstream Providers
2
Downstream Customers
0

How to read this ASPA check

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

AS205901 peering topology: 2 upstream providers and 0 downstream customersUpstreams: AS58212, AS213520. No downstreams.AS205901 - RUSK-AS Evgenii DiakovAS205901RUSK-AS Evgenii DiakovAS58212DATAFOREST dataforest…AS58212 - DATAFOREST dataforest GmbHAS213520SENKO-AS Senko Digita…AS213520 - SENKO-AS Senko Digital LLCUPSTREAMSDOWNSTREAMS

Upstream Providers(2)

AS205901 authorizes these ASNs as upstream transit providers.

ASNName
AS58212🇩🇪DATAFOREST dataforest GmbH
AS213520🇬🇪SENKO-AS Senko Digital LLC

ASPA object expires: 2026-10-27

Related Tools and Guides

← Back to AS205901