AS50263 ASPA Check - IXP 1 IX EU A Systems Sp. Z O.O

IXP-1-IX-EU A-Systems Sp. z o.o.🇵🇱 - ASPA check for AS50263: the upstream transit providers AS50263 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS50263 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.

AS50263 has not published its own ASPA object, but 13 ASNs list it as an authorized upstream provider.

Listed as Upstream By
13 ASNs
Upstream Providers
-
Downstream Customers
13

Peering Topology

AS50263 peering topology: 0 upstream providers and 13 downstream customersNo upstreams. Downstreams: AS30823, AS42739, AS51202, AS51396, AS62000, AS64289, AS207994, AS214757 and more.AS50263 - IXP-1-IX-EU A-Systems Sp. z o.o.AS50263IXP-1-IX-EU A-Systems…AS30823AUROLOGIC aurologic G…AS30823 - AUROLOGIC aurologic GmbHAS42739FONE-ASN Hawe Telekom…AS42739 - FONE-ASN Hawe Telekom S.A.AS51202NUXOA NUXOA GmbHAS51202 - NUXOA NUXOA GmbHAS51396PFCLOUD Pfcloud UG (h…AS51396 - PFCLOUD Pfcloud UG (haftungsbeschrankt)AS62000AS62000 SERVERD SASAS62000 - AS62000 SERVERD SASAS64289MACARNE - Macarne.comAS64289 - MACARNE - Macarne.comAS207994Blockchain-Creek Bloc…AS207994 - Blockchain-Creek Blockchain Creek B.V.AS214757Jakub-Krsa Jakub KrsaAS214757 - Jakub-Krsa Jakub KrsaView all 13 downstreams →UPSTREAMSDOWNSTREAMS

Downstream Customers(13)

These ASNs list AS50263 as an authorized upstream provider.

ASNName
AS30823🇩🇪AUROLOGIC aurologic GmbH
AS42739🇵🇱FONE-ASN Hawe Telekom S.A.
AS51202🇩🇪NUXOA NUXOA GmbH
AS51396🇩🇪PFCLOUD Pfcloud UG (haftungsbeschrankt)
AS62000🇫🇷AS62000 SERVERD SAS
AS64289🇺🇸MACARNE - Macarne.com
AS207994🇧🇪Blockchain-Creek Blockchain Creek B.V.
AS214757🇨🇿Jakub-Krsa Jakub Krsa
AS214762🇵🇱MATHOST Sebastian Stefanek trading as MatHost.eu
AS215248🇳🇱BastiaanBrink Bastiaan Mathijs Brink
13 total
1 / 2
About ASPA - what it is and why AS50263 should publish one

ASPA (Autonomous System Provider Authorization) is a cryptographically signed RPKI object specified in the IETF draft-ietf-sidrops-aspa-profile that lets an AS declare which upstream networks are its authorized transit providers. Together with route origin validation (ROV), ASPA enables BGP route leak detection: routers can reject AS-paths in which a network appears as a provider without being authorized. Route leaks are a frequent cause of large routing incidents, and ROV alone cannot detect them because the origin of a leaked route is correct.

AS50263 (IXP-1-IX-EU A-Systems Sp. z o.o.) has not published an ASPA object. Hops through it are therefore "unknown" to ASPA validation - not invalid, but not protected either. An ASPA object lists every transit provider of the network (or AS0 if it has none) and is created in the RIR's hosted RPKI where ASPA is supported, or in a delegated RPKI setup. For most networks the record is a short list of their upstream ASNs.

Create an ASPA object: RIPE Portal · ARIN RPKI · APNIC MyAPNIC · ipctl.io RPKI & ROA tools

Related Tools and Guides

← Back to AS50263