AS39728 ASPA Check - Luganet Likhno Dmitriy Trading Luganet
PublishedLuganet Likhno Dmitriy trading as Luganet🇷🇺 - ASPA check for AS39728: the upstream transit providers AS39728 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS39728 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.
How to read this ASPA check
The 7 providers below are the only networks allowed to appear directly above AS39728 in an AS-path. If AS39728 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(7)
AS39728 authorizes these ASNs as upstream transit providers.
| ASN | Name |
|---|---|
| AS3216 | 🇷🇺SOVAM-AS PJSC "Vimpelcom" |
| AS12389 | 🇷🇺ROSTELECOM-AS PJSC Rostelecom |
| AS31500 | 🇦🇬GNM-AS Global Network Management Inc |
| AS41039 | 🇷🇺DON-FTTH Timer, LLC |
| AS50509 | 🇷🇺TRANSROUTE Transroute Telecom LTD |
| AS198310 | 🇷🇺ooo-molniya OOO Molniya |
| AS201706 | 🇷🇺AS-SERVICEPIPE SERVICEPIPE LLC |
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
- AS39728 Overview - prefixes, BGP routes, peers, and RPKI status