AS214763 ASPA Check - Akshay Revankar Akshay Revankar
PublishedAkshay-Revankar Akshay Revankar🇺🇸 - ASPA check for AS214763: the upstream transit providers AS214763 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS214763 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 AS214763 in an AS-path. If AS214763 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)
AS214763 authorizes these ASNs as upstream transit providers.
| ASN | Name |
|---|---|
| AS24381 | 🇦🇺BGPE-AS - BGP.Exchange |
| AS29632 | 🇧🇬NASSIST-AS Netassist International EOOD |
| AS41051 | 🇨🇭FREETRANSIT Openfactory GmbH |
| AS47272 | 🇺🇸HYEHOST - HYEHOST LLC |
| AS58057 | 🇨🇭SECUREBIT Securebit AG |
| AS209533 | 🇨🇭BGPTunnel iFog GmbH |
| AS211509 | 🇺🇦RUDAKI-AS Rudakov Ihor |
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
- AS214763 Overview - prefixes, BGP routes, peers, and RPKI status