AS201732 ASPA Check - Enric Aparisi Verdaguer Enric Aparisi Verdaguer

Published

enric-aparisi-verdaguer Enric Aparisi Verdaguer🇪🇸 - ASPA check for AS201732: the upstream transit providers AS201732 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS201732 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 AS201732 in an AS-path. If AS201732 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

AS201732 peering topology: 2 upstream providers and 0 downstream customersUpstreams: AS41051, AS209533. No downstreams.AS201732 - enric-aparisi-verdaguer Enric Aparisi VerdaguerAS201732enric-aparisi-verdagu…AS41051FREETRANSIT Openfacto…AS41051 - FREETRANSIT Openfactory GmbHAS209533BGPTunnel iFog GmbHAS209533 - BGPTunnel iFog GmbHUPSTREAMSDOWNSTREAMS

Upstream Providers(2)

AS201732 authorizes these ASNs as upstream transit providers.

ASNName
AS41051🇨🇭FREETRANSIT Openfactory GmbH
AS209533🇨🇭BGPTunnel iFog GmbH

ASPA object expires: 2026-10-27

Related Tools and Guides

← Back to AS201732