AS402584 ASPA Check - Metropolitan

Published

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

AS402584 peering topology: 2 upstream providers and 0 downstream customersUpstreams: AS3356, AS14041. No downstreams.AS402584 - MSUDENVER - MetropolitanAS402584MSUDENVER - Metropoli…AS3356LEVEL3 - Level 3 Pare…AS3356 - LEVEL3 - Level 3 Parent, LLCAS14041AS-FRGP - University …AS14041 - AS-FRGP - University Corporation for Atmospheric ResearchUPSTREAMSDOWNSTREAMS

Upstream Providers(2)

AS402584 authorizes these ASNs as upstream transit providers.

ASNName
AS3356🇺🇸LEVEL3 - Level 3 Parent, LLC
AS14041🇺🇸AS-FRGP - University Corporation for Atmospheric Research

ASPA object expires: 2026-10-27

Related Tools and Guides

← Back to AS402584