AS48387 ASPA Check - RTBH Christian Seitz

Published

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

AS48387 peering topology: 1 upstream provider and 0 downstream customersUpstreams: AS29670. No downstreams.AS48387 - RTBH-AS Christian SeitzAS48387RTBH-AS Christian Sei…AS29670IN-BERLIN-AS Individu…AS29670 - IN-BERLIN-AS Individual Network Berlin (IN-Berlin) e.V.UPSTREAMSDOWNSTREAMS

Upstream Providers(1)

AS48387 authorizes these ASNs as upstream transit providers.

ASNName
AS29670🇩🇪IN-BERLIN-AS Individual Network Berlin ("IN-Berlin") e.V.

ASPA object expires: 2026-10-27

Related Tools and Guides

← Back to AS48387