AS38491 ASPA Check - VITROINC AP VITRO
PublishedVITROINC-AS-AP VITRO INC.🇵🇭 - ASPA check for AS38491: the upstream transit providers AS38491 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS38491 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.
How to read this ASPA check
The 19 providers below are the only networks allowed to appear directly above AS38491 in an AS-path. If AS38491 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(19)
AS38491 authorizes these ASNs as upstream transit providers.
| ASN | Name |
|---|---|
| AS1299 | 🇸🇪TWELVE99 Arelion Sweden AB |
| AS3491 | 🇭🇰PCCWG-APAC-HK PCCW Global HK Ltd. |
| AS4635 | 🇭🇰HKIX-RS1 Hong Kong Internet Exchange--Route Server 1 |
| AS4637 | 🇭🇰ASN-TELSTRA-GLOBAL Telstra Global |
| AS4779 | 🇵🇭PHOPENIX-AS-PH Philippine Open Internet Exchange |
| AS6648 | 🇵🇭BAYAN-TELECOMMUNICATIONS Bayan Telecommunications, Inc. |
| AS7707 | 🇵🇭PHIX-AS-AP PHILIPPINE LONG DISTANCE TELEPHONE COMPANY |
| AS9299 | 🇵🇭IPG-AS-AP Philippine Long Distance Telephone Company |
| AS15169 | 🇺🇸GOOGLE - Google LLC |
| AS15412 | 🇬🇧FLAG-AS Flag Telecom UK Limited |
ASPA object expires: 2026-10-17
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
- AS38491 Overview - prefixes, BGP routes, peers, and RPKI status