AS2611 ASPA Check - BELNET

BELNET BELNET🇧🇪 - ASPA check for AS2611: the upstream transit providers AS2611 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS2611 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.

AS2611 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

AS2611 peering topology: 0 upstream providers and 1 downstream customerNo upstreams. Downstreams: AS49935.AS2611 - BELNET BELNETAS2611BELNET BELNETAS49935SmartEye SmartEye B.VAS49935 - SmartEye SmartEye B.VUPSTREAMSDOWNSTREAMS

Downstream Customers(1)

These ASNs list AS2611 as an authorized upstream provider.

ASNName
AS49935🇧🇪SmartEye SmartEye B.V
About ASPA - what it is and why AS2611 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.

AS2611 (BELNET BELNET) 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

← Back to AS2611