AS200625 ASPA Check - MA P NET Maciej Peczyk

Published

MA-P-NET Maciej Peczyk🇵🇱 - ASPA check for AS200625: the upstream transit providers AS200625 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS200625 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.

ASPA Status
Published
Upstream Providers
3
Downstream Customers
0

How to read this ASPA check

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

AS200625 peering topology: 3 upstream providers and 0 downstream customersUpstreams: AS209533, AS212895, AS215467. No downstreams.AS200625 - MA-P-NET Maciej PeczykAS200625MA-P-NET Maciej PeczykAS209533BGPTunnel iFog GmbHAS209533 - BGPTunnel iFog GmbHAS212895ROUTE64_ORG Johannes …AS212895 - ROUTE64_ORG Johannes ErnstAS215467Skhron Skhron OUAS215467 - Skhron Skhron OUUPSTREAMSDOWNSTREAMS

Upstream Providers(3)

AS200625 authorizes these ASNs as upstream transit providers.

ASNName
AS209533🇨🇭BGPTunnel iFog GmbH
AS212895🇩🇪ROUTE64_ORG Johannes Ernst
AS215467🇪🇪Skhron Skhron OU

ASPA object expires: 2026-10-27

Related Tools and Guides

← Back to AS200625