AS209625 ASPA Check - Redcluster

Published

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

ASPA Status
Published
Upstream Providers
3
Downstream Customers
0

How to read this ASPA check

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

AS209625 peering topology: 3 upstream providers and 0 downstream customersUpstreams: AS3399, AS4849, AS44901. No downstreams.AS209625 - redcluster Redcluster LTDAS209625redcluster Redcluster…AS3399OBE-NET Obenet ABAS3399 - OBE-NET Obenet ABAS4849S3Company S3 Company …AS4849 - S3Company S3 Company LtdAS44901belcloud Belcloud LTDAS44901 - belcloud Belcloud LTDUPSTREAMSDOWNSTREAMS

Upstream Providers(3)

AS209625 authorizes these ASNs as upstream transit providers.

ASNName
AS3399🇸🇪OBE-NET Obenet AB
AS4849🇧🇬S3Company S3 Company Ltd
AS44901🇧🇬belcloud Belcloud LTD

ASPA object expires: 2026-10-12

Related Tools and Guides

← Back to AS209625