AS201269 ASPA Check - IVANS Lavrentjevs
PublishedIVANS-AS Ivans Lavrentjevs🇱🇻 - ASPA check for AS201269: the upstream transit providers AS201269 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS201269 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 AS201269 in an AS-path. If AS201269 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)
AS201269 authorizes these ASNs as upstream transit providers.
| ASN | Name |
|---|---|
| AS49581 | 🇩🇪TUBE-HOSTING Ferdinand Zink trading as Tube-Hosting |
| AS62214 | 🇭🇺RACKFOREST-AS Rackforest Zrt. |
| AS207208 | 🇵🇱Mevspace-projects MEVSPACE sp. z o.o. |
| AS214790 | 🇪🇪BRAINOZA Brainoza OU |
| AS215730 | 🇦🇪H2NEXUS-AS H2NEXUS CLOUD SERVICES - FZCO |
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
- AS201269 Overview - prefixes, BGP routes, peers, and RPKI status