AS8894 ASPA Check - NICE

NICE-AS Nice LTD🇮🇱 - ASPA check for AS8894: the upstream transit providers AS8894 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS8894 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.

AS8894 has not published its own ASPA object, but 1 ASN lists it as an authorized upstream provider.

Listed as Upstream By
1 ASN
Upstream Providers
-
Downstream Customers
1

Peering Topology

AS8894 peering topology: 0 upstream providers and 1 downstream customerNo upstreams. Downstreams: AS205329.AS8894 - NICE-AS Nice LTDAS8894NICE-AS Nice LTDAS205329Kai-Jung-Chen Kai-Jun…AS205329 - Kai-Jung-Chen Kai-Jung ChenUPSTREAMSDOWNSTREAMS

Downstream Customers(1)

These ASNs list AS8894 as an authorized upstream provider.

ASNName
AS205329🇹🇼Kai-Jung-Chen Kai-Jung Chen
About ASPA - what it is and why AS8894 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.

AS8894 (NICE-AS Nice LTD) 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