AS201741 ASPA Check - Nety Burak GULDOGAN

Published

nety Burak GULDOGAN🇹🇷 - ASPA check for AS201741: the upstream transit providers AS201741 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS201741 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 AS201741 in an AS-path. If AS201741 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

AS201741 peering topology: 1 upstream provider and 0 downstream customersUpstreams: AS210574. No downstreams.AS201741 - nety Burak GULDOGANAS201741nety Burak GULDOGANAS210574POYRAZ PH Bilisim Tek…AS210574 - POYRAZ PH Bilisim Teknolojileri Limited SirketiUPSTREAMSDOWNSTREAMS

Upstream Providers(1)

AS201741 authorizes these ASNs as upstream transit providers.

ASNName
AS210574🇹🇷POYRAZ PH Bilisim Teknolojileri Limited Sirketi

ASPA object expires: 2026-10-27

Related Tools and Guides

← Back to AS201741