AS209718 ASPA Check - REDPANDA DNS Jori Vanneste

Published

REDPANDA-DNS-AS Jori Vanneste🇧🇪 - ASPA check for AS209718: the upstream transit providers AS209718 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS209718 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 AS209718 in an AS-path. If AS209718 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

AS209718 peering topology: 2 upstream providers and 0 downstream customersUpstreams: AS34927, AS209022. No downstreams.AS209718 - REDPANDA-DNS-AS Jori VannesteAS209718REDPANDA-DNS-AS Jori …AS34927iFog-GmbH iFog GmbHAS34927 - iFog-GmbH iFog GmbHAS209022Tschajera-Limited Tsc…AS209022 - Tschajera-Limited Tschajera LimitedUPSTREAMSDOWNSTREAMS

Upstream Providers(2)

AS209718 authorizes these ASNs as upstream transit providers.

ASNName
AS34927🇨🇭iFog-GmbH iFog GmbH
AS209022🇬🇧Tschajera-Limited Tschajera Limited

ASPA object expires: 2026-10-27

Related Tools and Guides

← Back to AS209718