AS57797 ASPA Check - SYSLEVEL SAS
PublishedSYSLEVEL SysLevel SASπ«π· - ASPA check for AS57797: the upstream transit providers AS57797 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS57797 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.
How to read this ASPA check
The 4 providers below are the only networks allowed to appear directly above AS57797 in an AS-path. If AS57797 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(4)
AS57797 authorizes these ASNs as upstream transit providers.
| ASN | Name |
|---|---|
| AS2027 | π«π·MilkyWan MilkyWan Association |
| AS35661 | π«π·VIRTUASYS-EU VIRTUA SYSTEMS SAS |
| AS39801 | π«π·FRANCE-IX-L3P France IX Services SASU |
| AS52025 | π¬π§PARADOXNETWORKS-LIMITED ParadoxNetworks Limited |
Downstream Customers(1)
These ASNs list AS57797 as an authorized upstream provider.
| ASN | Name |
|---|---|
| AS198839 | π«π·MCASYS SysLevel SAS |
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
- AS57797 Overview - prefixes, BGP routes, peers, and RPKI status