AS43298 ASPA Check - StormNetworks Storm Networks

StormNetworks Storm Networks LLC🇷🇺 - ASPA check for AS43298: the upstream transit providers AS43298 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS43298 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.

AS43298 has not published its own ASPA object, but 3 ASNs list it as an authorized upstream provider.

Listed as Upstream By
3 ASNs
Upstream Providers
-
Downstream Customers
3

Downstream Customers(3)

These ASNs list AS43298 as an authorized upstream provider.

ASNName
AS31257🇷🇺ORIONNET-KRK Orion Telecom LLC
AS50427🇷🇺ORIONNET-ABK Orion Telecom LLC
AS200240🇮🇩EKA-SOPPENG-ID EKA SAPUTRA
About ASPA - what it is and why AS43298 should publish one

ASPA (Autonomous System Provider Authorization) is a cryptographically signed RPKI object specified in the IETF draft-ietf-sidrops-aspa-profile that lets an AS declare which upstream networks are its authorized transit providers. Together with route origin validation (ROV), ASPA enables BGP route leak detection: routers can reject AS-paths in which a network appears as a provider without being authorized. Route leaks are a frequent cause of large routing incidents, and ROV alone cannot detect them because the origin of a leaked route is correct.

AS43298 (StormNetworks Storm Networks LLC) has not published an ASPA object. Hops through it are therefore "unknown" to ASPA validation - not invalid, but not protected either. An ASPA object lists every transit provider of the network (or AS0 if it has none) and is created in the RIR's hosted RPKI where ASPA is supported, or in a delegated RPKI setup. For most networks the record is a short list of their upstream ASNs.

Create an ASPA object: RIPE Portal · ARIN RPKI · APNIC MyAPNIC · ipctl.io RPKI & ROA tools

Related Tools and Guides