AS201541 ASPA Check - LixPacket Nedas Dozorec
PublishedLixPacket Nedas Dozorec🇱🇹 - ASPA check for AS201541: the upstream transit providers AS201541 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS201541 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.
How to read this ASPA check
The 7 providers below are the only networks allowed to appear directly above AS201541 in an AS-path. If AS201541 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(7)
AS201541 authorizes these ASNs as upstream transit providers.
| ASN | Name |
|---|---|
| AS56630 | 🇱🇹MELBICOM-EU-AS Melbikomas UAB |
| AS201279 | 🇷🇺AWAS-AS Loginov Vladislav |
| AS209533 | 🇨🇭BGPTunnel iFog GmbH |
| AS212895 | 🇩🇪ROUTE64_ORG Johannes Ernst |
| AS215685 | 🇩🇪Nexus Maik Sussdorf |
| AS215828 | 🇩🇪TMW-Global-Networks Tizian Maxime Weigt trading as "TMW Global Networks" |
| AS219529 | 🇷🇺PODRIL1AK2-AS Yulia Kurganova |
Downstream Customers(1)
These ASNs list AS201541 as an authorized upstream provider.
| ASN | Name |
|---|---|
| AS33711 | 🇺🇸SADDLE-NETWORKS - Saddle Networks |
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
- AS201541 Overview - prefixes, BGP routes, peers, and RPKI status