AS58057 ASPA — SECUREBIT Upstream Provider Authorization

SECUREBIT Securebit AG🇨🇭

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

Listed as Upstream By
9 ASNs
Upstream Providers
Downstream Customers
9

Downstream Customers(9)

These ASNs list AS58057 as an authorized upstream provider.

ASNName
AS33711🇺🇸SADDLE-NETWORKS - Saddle Networks
AS57050🇷🇴DREAMSERVER-SRL DreamServer S.R.L.
AS57797🇫🇷SYSLEVEL SysLevel SAS
AS200306🇧🇬BG-STAMOV-AS Ivan Stamov
AS204033🇩🇪sarthur Oliver Arthur
AS214723🇳🇱HEIJKOOP-AS Maria-Elisabeth Annabel Heijkoop
AS216096🇦🇩SECUREPEAK Alex Terrats Ciberseguretat SLU
AS216357🇺🇸INFINITIUM-AS216357 INFINITIUM CORPORATION
AS396416🇰🇳SKNIX-SERVICES - The Government of Saint Kitts and Nevis
About ASPA - what it is and why AS58057 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 authorized to carry its traffic. Together with route origin validation (ROV), ASPA enables BGP route leak detection: routers can reject paths that traverse an unauthorized provider, which is one of the most common causes of large-scale internet outages.

AS58057 (SECUREBIT Securebit AG) has not yet published an ASPA object. Publishing one is free, takes a few minutes in your RIR portal, and strengthens the routing security posture of every network that depends on you. If you only buy transit from well-known upstreams, the record is usually a short list of their ASNs.

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

Related Tools