AS219358 ASPA Check - STARLAB MCHJ

Published

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

AS219358 peering topology: 1 upstream provider and 0 downstream customersUpstreams: AS34250. No downstreams.AS219358 - STARLAB STARLAB MCHJAS219358STARLAB STARLAB MCHJAS34250UZTELECOM-AS Uzbektel…AS34250 - UZTELECOM-AS Uzbektelekom Joint Stock CompanyUPSTREAMSDOWNSTREAMS

Upstream Providers(1)

AS219358 authorizes these ASNs as upstream transit providers.

ASNName
AS34250🇺🇿UZTELECOM-AS "Uzbektelekom" Joint Stock Company

ASPA object expires: 2026-10-12

Related Tools and Guides

← Back to AS219358