AS201345 ASPA Check - Shuma Watanabe Shuma Watanabe
PublishedShuma-Watanabe Shuma Watanabe🇯🇵 - ASPA check for AS201345: the upstream transit providers AS201345 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS201345 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.
How to read this ASPA check
The 8 providers below are the only networks allowed to appear directly above AS201345 in an AS-path. If AS201345 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(8)
AS201345 authorizes these ASNs as upstream transit providers.
| ASN | Name |
|---|---|
| AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation |
| AS11967 | 🇪🇪HOP179 Hop179 OU |
| AS20473 | 🇺🇸AS-VULTR - The Constant Company, LLC |
| AS31898 | 🇺🇸ORACLE-BMC-31898 - Oracle Corporation |
| AS41051 | 🇨🇭FREETRANSIT Openfactory GmbH |
| AS209533 | 🇨🇭BGPTunnel iFog GmbH |
| AS212895 | 🇩🇪ROUTE64_ORG Johannes Ernst |
| AS396982 | 🇺🇸GOOGLE-CLOUD-PLATFORM - Google LLC |
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
- AS201345 Overview - prefixes, BGP routes, peers, and RPKI status