AS201124 ASPA Check - DKUK Daniel Kuk

Published

DKUK-AS Daniel Kuk🇩🇪 - ASPA check for AS201124: the upstream transit providers AS201124 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS201124 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.

ASPA Status
Published
Upstream Providers
2
Downstream Customers
0

How to read this ASPA check

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

AS201124 peering topology: 2 upstream providers and 0 downstream customersUpstreams: AS49581, AS219418. No downstreams.AS201124 - DKUK-AS Daniel KukAS201124DKUK-AS Daniel KukAS49581TUBE-HOSTING Ferdinan…AS49581 - TUBE-HOSTING Ferdinand Zink trading as Tube-HostingAS219418eHILL-MEDIA Jan HillAS219418 - eHILL-MEDIA Jan HillUPSTREAMSDOWNSTREAMS

Upstream Providers(2)

AS201124 authorizes these ASNs as upstream transit providers.

ASNName
AS49581🇩🇪TUBE-HOSTING Ferdinand Zink trading as Tube-Hosting
AS219418🇩🇪eHILL-MEDIA Jan Hill

ASPA object expires: 2026-10-19

Related Tools and Guides

← Back to AS201124