AS201002 ASPA Check - PebbleHost Customers PebbleHost

Published

PebbleHost-Customers PebbleHost Ltd🇬🇧 - ASPA check for AS201002: the upstream transit providers AS201002 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS201002 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 AS201002 in an AS-path. If AS201002 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

AS201002 peering topology: 2 upstream providers and 0 downstream customersUpstreams: AS212027, AS215413. No downstreams.AS201002 - PebbleHost-Customers PebbleHost LtdAS201002PebbleHost-Customers …AS212027PebbleHost PebbleHost…AS212027 - PebbleHost PebbleHost LtdAS215413PebbleHost-Protected …AS215413 - PebbleHost-Protected PebbleHost LtdUPSTREAMSDOWNSTREAMS

Upstream Providers(2)

AS201002 authorizes these ASNs as upstream transit providers.

ASNName
AS212027🇬🇧PebbleHost PebbleHost Ltd
AS215413🇬🇧PebbleHost-Protected PebbleHost Ltd

ASPA object expires: 2026-10-27

Related Tools and Guides

← Back to AS201002