AS204033 ASPA Check - Sarthur Oliver Arthur

Published

sarthur Oliver Arthur🇩🇪 - ASPA check for AS204033: the upstream transit providers AS204033 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS204033 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 AS204033 in an AS-path. If AS204033 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

AS204033 peering topology: 2 upstream providers and 0 downstream customersUpstreams: AS34872, AS58057. No downstreams.AS204033 - sarthur Oliver ArthurAS204033sarthur Oliver ArthurAS34872Servperso_Systems Sar…AS34872 - Servperso_Systems Sarah Rossius trading as Servperso SystemsAS58057SECUREBIT Securebit AGAS58057 - SECUREBIT Securebit AGUPSTREAMSDOWNSTREAMS

Upstream Providers(2)

AS204033 authorizes these ASNs as upstream transit providers.

ASNName
AS34872🇧🇪Servperso_Systems Sarah Rossius trading as Servperso Systems
AS58057🇨🇭SECUREBIT Securebit AG

ASPA object expires: 2026-10-27

Related Tools and Guides

← Back to AS204033