AS154796 ASPA Check - METANAME AP Metaname

Published

METANAME-AS-AP Metaname🇳🇿 - ASPA check for AS154796: the upstream transit providers AS154796 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS154796 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
0

How to read this ASPA check

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

AS154796 peering topology: 2 upstream providers and 0 downstream customersUpstreams: AS18400, AS23838. No downstreams.AS154796 - METANAME-AS-AP MetanameAS154796METANAME-AS-AP Metana…AS18400XTREME-AS-AP Xtreme N…AS18400 - XTREME-AS-AP Xtreme Networks LimitedAS23838SOLARIX-INTERNET-AS-A…AS23838 - SOLARIX-INTERNET-AS-AP Solarix Networks LimitedUPSTREAMSDOWNSTREAMS

Upstream Providers(2)

AS154796 authorizes these ASNs as upstream transit providers.

ASNName
AS18400🇳🇿XTREME-AS-AP Xtreme Networks Limited
AS23838🇳🇿SOLARIX-INTERNET-AS-AP Solarix Networks Limited

ASPA object expires: 2026-10-18

Related Tools and Guides

← Back to AS154796