AS43171 ASPA Check - MAXNET Lukasz Rafal Hamerski Trading Maxnet
PublishedMAXNET Lukasz Rafal Hamerski trading as Maxnet🇵🇱 - ASPA check for AS43171: the upstream transit providers AS43171 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS43171 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.
How to read this ASPA check
The 5 providers below are the only networks allowed to appear directly above AS43171 in an AS-path. If AS43171 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(5)
AS43171 authorizes these ASNs as upstream transit providers.
| ASN | Name |
|---|---|
| AS9141 | 🇵🇱AS9141 P4 Sp. z o.o. |
| AS21395 | 🇵🇱cPoP Orange Polska Spolka Akcyjna |
| AS29535 | 🇵🇱MIX2_OpenPeering Orange Polska Spolka Akcyjna |
| AS62081 | 🇵🇱EPIX-WAW-GlobalMix Stowarzyszenie e-Poludnie |
| AS201054 | 🇵🇱EPIX-PolMix Stowarzyszenie e-Poludnie |
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
- AS43171 Overview - prefixes, BGP routes, peers, and RPKI status