AS49974 ASPA Check - BODATA Bo Data ApS

Published

BODATA Bo data ApS🇩🇰 - ASPA check for AS49974: the upstream transit providers AS49974 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS49974 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
1

How to read this ASPA check

The 2 providers below are the only networks allowed to appear directly above AS49974 in an AS-path. If AS49974 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

AS49974 peering topology: 2 upstream providers and 1 downstream customerUpstreams: AS3292, AS43557. Downstreams: AS45024.AS49974 - BODATA Bo data ApSAS49974BODATA Bo data ApSAS3292TDC TDC Holding A/SAS3292 - TDC TDC Holding A/SAS43557ASEMNET Sinal A/SAS43557 - ASEMNET Sinal A/SAS45024PARTNERIT-AS Bo data …AS45024 - PARTNERIT-AS Bo data ApSUPSTREAMSDOWNSTREAMS

Upstream Providers(2)

AS49974 authorizes these ASNs as upstream transit providers.

ASNName
AS3292🇩🇰TDC TDC Holding A/S
AS43557🇩🇰ASEMNET Sinal A/S

Downstream Customers(1)

These ASNs list AS49974 as an authorized upstream provider.

ASNName
AS45024🇩🇰PARTNERIT-AS Bo data ApS

ASPA object expires: 2026-10-27

Related Tools and Guides

← Back to AS49974