AS397677 ASPA Check - SixPackets

Published

SIXPACKETS - SixPackets🇺🇸 - ASPA check for AS397677: the upstream transit providers AS397677 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS397677 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 AS397677 in an AS-path. If AS397677 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

AS397677 peering topology: 1 upstream provider and 0 downstream customersUpstreams: AS16970. No downstreams.AS397677 - SIXPACKETS - SixPacketsAS397677SIXPACKETS - SixPacke…AS16970MIDNET - MIDnetAS16970 - MIDNET - MIDnetUPSTREAMSDOWNSTREAMS

Upstream Providers(1)

AS397677 authorizes these ASNs as upstream transit providers.

ASNName
AS16970🇺🇸MIDNET - MIDnet

ASPA object expires: 2026-10-12

Related Tools and Guides

← Back to AS397677