AS3671 ASPA Check - SLAC National Accelerator Laboratory

Published

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

AS3671 peering topology: 2 upstream providers and 0 downstream customersUpstreams: AS293, AS46749. No downstreams.AS3671 - SLAC - SLAC National Accelerator LaboratoryAS3671SLAC - SLAC National …AS293ESNET - ESnetAS293 - ESNET - ESnetAS46749STANFORD-INTERNET-ACC…AS46749 - STANFORD-INTERNET-ACCESS - Stanford UniversityUPSTREAMSDOWNSTREAMS

Upstream Providers(2)

AS3671 authorizes these ASNs as upstream transit providers.

ASNName
AS293🇺🇸ESNET - ESnet
AS46749🇺🇸STANFORD-INTERNET-ACCESS - Stanford University

ASPA object expires: 2026-10-18

Related Tools and Guides

← Back to AS3671