AS48116 ASPA Check - Highsec Fredrik Holmqvist

Published

highsec-as Fredrik Holmqvist🇸🇪 - ASPA check for AS48116: the upstream transit providers AS48116 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS48116 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 AS48116 in an AS-path. If AS48116 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

AS48116 peering topology: 2 upstream providers and 0 downstream customersUpstreams: AS39889, AS50989. No downstreams.AS48116 - highsec-as Fredrik HolmqvistAS48116highsec-as Fredrik Ho…AS39889DCS-Networks-AS Fredr…AS39889 - DCS-Networks-AS Fredrik HolmqvistAS50989DCS-Networks-AS SITAB…AS50989 - DCS-Networks-AS SITAB InfrastrukturUPSTREAMSDOWNSTREAMS

Upstream Providers(2)

AS48116 authorizes these ASNs as upstream transit providers.

ASNName
AS39889🇸🇪DCS-Networks-AS Fredrik Holmqvist
AS50989🇸🇪DCS-Networks-AS SITAB Infrastruktur

ASPA object expires: 2026-10-27

Related Tools and Guides

← Back to AS48116