AS41572 ASPA Check - HAFSLUND GLOBALCONNECT

Published

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

AS41572 peering topology: 1 upstream provider and 0 downstream customersUpstreams: AS2116. No downstreams.AS41572 - HAFSLUND GLOBALCONNECT ASAS41572HAFSLUND GLOBALCONNEC…AS2116GlobalConnect-AS2116 …AS2116 - GlobalConnect-AS2116 GLOBALCONNECT ASUPSTREAMSDOWNSTREAMS

Upstream Providers(1)

AS41572 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 AS41572