AS56368 ASPA Check - NICODUCK Nicola Von Thadden
PublishedNICODUCK Nicola von Thadden🇩🇪 - ASPA check for AS56368: the upstream transit providers AS56368 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS56368 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 AS56368 in an AS-path. If AS56368 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)
AS56368 authorizes these ASNs as upstream transit providers.
| ASN | Name |
|---|---|
| AS15945 | 🇩🇪PfalzKom-Net PFALZKOM GmbH |
| AS21473 | 🇩🇪PFALZKOM PFALZKOM GmbH |
Downstream Customers(1)
These ASNs list AS56368 as an authorized upstream provider.
| ASN | Name |
|---|---|
| AS47368 | 🇩🇪AVARA Ava Rose Sophie Jacobsen |
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
- AS56368 Overview - prefixes, BGP routes, peers, and RPKI status