AS218280 ASPA Check

Published

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

AS218280 peering topology: 2 upstream providers and 0 downstream customersUpstreams: AS34927, AS35661. No downstreams.AS218280 - AS218280AS34927iFog-GmbH iFog GmbHAS34927 - iFog-GmbH iFog GmbHAS35661VIRTUASYS-EU VIRTUA Sā€¦AS35661 - VIRTUASYS-EU VIRTUA SYSTEMS SASUPSTREAMSDOWNSTREAMS

Upstream Providers(2)

AS218280 authorizes these ASNs as upstream transit providers.

ASNName
AS34927šŸ‡ØšŸ‡­iFog-GmbH iFog GmbH
AS35661šŸ‡«šŸ‡·VIRTUASYS-EU VIRTUA SYSTEMS SAS

ASPA object expires: 2026-10-29

Related Tools and Guides

ā† Back to AS218280