AS61953 ASPA Check - TRANSIT CLOUDEUS SL

Published

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

ASPA Status
Published
Upstream Providers
1
Downstream Customers
0

How to read this ASPA check

The provider below is the only network allowed to appear directly above AS61953 in an AS-path. If AS61953 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

AS61953 peering topology: 1 upstream provider and 0 downstream customersUpstreams: AS62033. No downstreams.AS61953 - TRANSIT CLOUDEUS SLAS61953TRANSIT CLOUDEUS SLAS62033HOSTERS CLOUDEUS SLAS62033 - HOSTERS CLOUDEUS SLUPSTREAMSDOWNSTREAMS

Upstream Providers(1)

AS61953 authorizes these ASNs as upstream transit providers.

ASNName
AS62033🇪🇸HOSTERS CLOUDEUS SL

ASPA object expires: 2026-10-27

Related Tools and Guides

← Back to AS61953