AS41371 ASPA Check - BIKADA TOO

Published

BIKADA BiKaDa TOO🇰🇿 - ASPA check for AS41371: the upstream transit providers AS41371 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS41371 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 AS41371 in an AS-path. If AS41371 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

AS41371 peering topology: 1 upstream provider and 0 downstream customersUpstreams: AS35104. No downstreams.AS41371 - BIKADA BiKaDa TOOAS41371BIKADA BiKaDa TOOAS35104KTC-AS QMOBILE JSCAS35104 - KTC-AS QMOBILE JSCUPSTREAMSDOWNSTREAMS

Upstream Providers(1)

AS41371 authorizes these ASNs as upstream transit providers.

ASNName
AS35104🇰🇿KTC-AS QMOBILE JSC

ASPA object expires: 2026-10-27

Related Tools and Guides

← Back to AS41371