AS34568 ASPA Check - CONNECTINGBYTES

Published

CONNECTINGBYTES-AS ConnectingBytes GmbH🇩🇪 - ASPA check for AS34568: the upstream transit providers AS34568 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS34568 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 AS34568 in an AS-path. If AS34568 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

AS34568 peering topology: 2 upstream providers and 0 downstream customersUpstreams: AS13237, AS30962. No downstreams.AS34568 - CONNECTINGBYTES-AS ConnectingBytes GmbHAS34568CONNECTINGBYTES-AS Co…AS13237LAMBDANET-AS euNetwor…AS13237 - LAMBDANET-AS euNetworks GmbHAS30962COMTRANCE-AS comtranc…AS30962 - COMTRANCE-AS comtrance service GmbHUPSTREAMSDOWNSTREAMS

Upstream Providers(2)

AS34568 authorizes these ASNs as upstream transit providers.

ASNName
AS13237🇩🇪LAMBDANET-AS euNetworks GmbH
AS30962🇩🇪COMTRANCE-AS comtrance service GmbH

ASPA object expires: 2026-10-28

Related Tools and Guides

← Back to AS34568