AS39753 ASPA Check - LIUXYON Kai Liu
PublishedLIUXYON Kai Liu🇨🇳 - ASPA check for AS39753: the upstream transit providers AS39753 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS39753 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.
How to read this ASPA check
The 12 providers below are the only networks allowed to appear directly above AS39753 in an AS-path. If AS39753 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(12)
AS39753 authorizes these ASNs as upstream transit providers.
| ASN | Name |
|---|---|
| AS8772 | 🇺🇦NLineLLC NetAssist LLC |
| AS8849 | 🇱🇹MELBICOM-EU-AS Melbikomas UAB |
| AS29632 | 🇧🇬NASSIST-AS Netassist International EOOD |
| AS35661 | 🇫🇷VIRTUASYS-EU VIRTUA SYSTEMS SAS |
| AS38074 | 🇯🇵SDCC-AS-AP SDCC Japan-West Area |
| AS53356 | 🇨🇦FREE RANGE CLOUD - Free Range Cloud Hosting Inc. |
| AS201398 | 🇺🇸AS201398-NETWORK Guwin Universal Services LLC |
| AS205941 | 🇷🇴LSG Lungu Stefan Gabriel |
| AS206628 | 🇺🇸EzriCloud Tianyu-Zhu |
| AS214205 | 🇷🇴CRISTIAN-TUDOR-MARCUS Cristian Tudor Marcus |
ASPA object expires: 2026-10-12
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
- AS39753 Overview - prefixes, BGP routes, peers, and RPKI status