AS198839 ASPA Check - MCASYS SysLevel SAS

Published

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

ASPA Status
Published
Upstream Providers
1
Downstream Customers
0

How to read this ASPA check

The provider below is the only network allowed to appear directly above AS198839 in an AS-path. If AS198839 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

AS198839 peering topology: 1 upstream provider and 0 downstream customersUpstreams: AS57797. No downstreams.AS198839 - MCASYS SysLevel SASAS198839MCASYS SysLevel SASAS57797SYSLEVEL SysLevel SASAS57797 - SYSLEVEL SysLevel SASUPSTREAMSDOWNSTREAMS

Upstream Providers(1)

AS198839 authorizes these ASNs as upstream transit providers.

ASNName
AS57797🇫🇷SYSLEVEL SysLevel SAS

ASPA object expires: 2026-10-27

Related Tools and Guides

← Back to AS198839