AS208321 ASPA Check - Itsr Sebastian Tobias Reimers

Published

itsr Sebastian Tobias Reimers🇩🇪 - ASPA check for AS208321: the upstream transit providers AS208321 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS208321 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 AS208321 in an AS-path. If AS208321 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

AS208321 peering topology: 2 upstream providers and 0 downstream customersUpstreams: AS20473, AS214915. No downstreams.AS208321 - itsr Sebastian Tobias ReimersAS208321itsr Sebastian Tobias…AS20473AS-VULTR - The Consta…AS20473 - AS-VULTR - The Constant Company, LLCAS214915PawHost Jan SmyrekAS214915 - PawHost Jan SmyrekUPSTREAMSDOWNSTREAMS

Upstream Providers(2)

AS208321 authorizes these ASNs as upstream transit providers.

ASNName
AS20473🇺🇸AS-VULTR - The Constant Company, LLC
AS214915🇩🇪PawHost Jan Smyrek

ASPA object expires: 2026-10-27

Related Tools and Guides