AS403202 ASPA Check

Published

ASPA check for AS403202: the upstream transit providers AS403202 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS403202 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.

ASPA Status
Published
Upstream Providers
2
Downstream Customers
0

How to read this ASPA check

The 2 providers below are the only networks allowed to appear directly above AS403202 in an AS-path. If AS403202 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

AS403202 peering topology: 2 upstream providers and 0 downstream customersUpstreams: AS29802, AS397067. No downstreams.AS403202 - AS403202AS29802HVC-AS - HIVELOCITY, …AS29802 - HVC-AS - HIVELOCITY, Inc.AS397067VFOREGONLLC - VFOrego…AS397067 - VFOREGONLLC - VFOregon LLCUPSTREAMSDOWNSTREAMS

Upstream Providers(2)

AS403202 authorizes these ASNs as upstream transit providers.

ASNName
AS29802🇺🇸HVC-AS - HIVELOCITY, Inc.
AS397067🇺🇸VFOREGONLLC - VFOregon LLC

ASPA object expires: 2026-11-09

Related Tools and Guides

← Back to AS403202