AS38927 ASPA Check - NETBUILD Net Build
PublishedNETBUILD-AS Net-Build GmbH🇩🇪 - ASPA check for AS38927: the upstream transit providers AS38927 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS38927 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.
How to read this ASPA check
The 2 providers below are the only networks allowed to appear directly above AS38927 in an AS-path. If AS38927 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(2)
AS38927 authorizes these ASNs as upstream transit providers.
| ASN | Name |
|---|---|
| AS9063 | 🇩🇪SAARGATE-AS VSE NET GmbH |
| AS15965 | 🇱🇺AS15965 CEGECOM S.A. |
Downstream Customers(1)
These ASNs list AS38927 as an authorized upstream provider.
| ASN | Name |
|---|---|
| AS204762 | 🇩🇪AYEDO Ayedo Cloud Solutions GmbH |
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
- AS38927 Overview - prefixes, BGP routes, peers, and RPKI status