AS6709 ASPA Check - BGNETT GLOBALCONNECT

Published

BGNETT GLOBALCONNECT AS🇳🇴 - ASPA check for AS6709: the upstream transit providers AS6709 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS6709 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 AS6709 in an AS-path. If AS6709 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

AS6709 peering topology: 1 upstream provider and 0 downstream customersUpstreams: AS2116. No downstreams.AS6709 - BGNETT GLOBALCONNECT ASAS6709BGNETT GLOBALCONNECT …AS2116GlobalConnect-AS2116 …AS2116 - GlobalConnect-AS2116 GLOBALCONNECT ASUPSTREAMSDOWNSTREAMS

Upstream Providers(1)

AS6709 authorizes these ASNs as upstream transit providers.

ASNName
AS2116🇳🇴GlobalConnect-AS2116 GLOBALCONNECT AS

ASPA object expires: 2026-10-27

Related Tools and Guides

← Back to AS6709