AS3214 ASPA — XTOM Upstream Provider Authorization
XTOM xTom GmbH🇩🇪
AS3214 has not published its own ASPA object, but 6 ASNs list it as an authorized upstream provider.
Peering Topology
Downstream Customers(6)
These ASNs list AS3214 as an authorized upstream provider.
| ASN | Name |
|---|---|
| AS23347 | 🇺🇸ZYC - ZYC Network LLC |
| AS34854 | 🇩🇪BLAHAJ-CLOUD Maria Merkel trading as Blahaj Studio |
| AS51087 | 🇬🇧BLING-AS Bling Network Ltd |
| AS200229 | 🇩🇪STATBYTE-AS Florian Kasper |
| AS207252 | 🇩🇪Realtox-Media Felix Gassan |
| AS214915 | 🇩🇪PawHost Jan Smyrek |
About ASPA - what it is and why AS3214 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.
AS3214 (XTOM xTom GmbH) 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
- RPKI & ROA Lookup — validate prefixes and check ASPA records for any ASN
- Global ASPA Adoption Statistics — transit-free ASNs, top upstream providers, adoption trends
- AS3214 Overview — prefixes, BGP routes, peers, and RPKI status