AS32167 ASPA Check - LSHIY
PublishedLSHIY-USER-CONTENT - LSHIY LLC๐บ๐ธ - ASPA check for AS32167: the upstream transit providers AS32167 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS32167 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.
How to read this ASPA check
The provider below is the only network allowed to appear directly above AS32167 in an AS-path. If AS32167 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(1)
AS32167 authorizes these ASNs as upstream transit providers.
| ASN | Name |
|---|---|
| AS955 | ๐บ๐ธLSHIY - LSHIY LLC |
Downstream Customers(1)
These ASNs list AS32167 as an authorized upstream provider.
| ASN | Name |
|---|---|
| AS401615 | ๐บ๐ธACCK-LTD - ACCK LLC |
ASPA object expires: 2026-10-28
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
- AS32167 Overview - prefixes, BGP routes, peers, and RPKI status