DATAMATIX

At a glance

• Autonomous system numberLinked with AS43855, AS8245, AS210973, AS24953 +1High confidence
• Address blocks1 address block currently recordedHigh confidence

Basic information

• Display nameDATAMATIXHigh confidence
• Directory categoryCompanyHigh confidence
• Last updatedJun 15, 2026High confidence

Locations

• Geography scopeUnited StatesHigh confidence
• Data centerUnited StatesMedium confidence
• IP transitUnited StatesMedium confidence
• Peering and IXPsUnited StatesMedium confidence
• Managed networksUnited StatesMedium confidence

What it does

• Data centerUnited States, Data center operator, DATAMATIX's public recordHigh confidence
• IP transitUnited States, IP transit provider, DATAMATIX's public recordHigh confidence
• Peering and IXPsUnited States, Peering or exchange entity, DATAMATIX's public recordHigh confidence
• Managed networksUnited States, Managed network operator, DATAMATIX's public recordHigh confidence

Network identity

• Autonomous system numberAS43855High confidence
• Autonomous system numberAS8245High confidence
• Autonomous system numberAS210973High confidence
• Autonomous system numberAS24953High confidence
• Autonomous system numberAS8218High confidence

IP address resources

Other network resources

• Data centerDATAMATIX United States Data center · United StatesHigh confidence
• Service platformDATAMATIX United States IP transit · United StatesHigh confidence
• Internet exchangeDATAMATIX United States peering/IXP · United StatesHigh confidence
• Service platformDATAMATIX United States Managed networks · United StatesHigh confidence

Registry and related records

• Editorial contextWho actually runs inside Datamatix's 212.236.10.0/24: the service layer the registry cannot answer, BTW's previous reporting on the Vienna network operator DATAMATIX Datensysteme GmbH closed the registry, RPKI, per-prefix routing and mirror-record layers of its autonomous system AS210973 one by one. Each report stopped at the same boundary: the public record shows what Datamatix holds, what it announces and what its routing policy declares, but not who uses the addresses. This report crosses that boundary. Inside one of the four /24s Datamatix's ASN originates — 212.236.10.0/24 — the reverse-DNS names, the abuse contact and the attribution labels do not point at datamatix.at at all. They point into the Video-Broadcast GmbH namespace and at a separate Vienna business called Rapid Solution Development. The evidence assembled here supports a precise distinction: Datamatix holds and originates the prefix; whether it hosts or operates anything inside it is a question the registry cannot answer, and the service-layer signals currently answer it in someone else's favour.Medium confidence
• Editorial contextDATAMATIX AS210973: what the live record proves about real operation, A Vienna company holds an autonomous system with four IPv4 prefixes, two cryptographic authorisations and a handful of upstreams. Reading the registry, the routing table and the service footprint layer by layer shows how far public evidence goes toward proving that a network actually operates — and where it stops.Medium confidence
• Editorial contextRegistered, authorised, and still unproven: what DATAMATIX's live posture says about operating a network, A small Vienna company holds an autonomous system, two valid RPKI authorisations and four IPv4 prefixes that different monitors count differently. Reading the current public posture layer by layer shows exactly how far registration, authorisation and observation go toward proving that a network actually operates — and where each layer stops.Medium confidence
• Editorial contextFive prefixes, five answers: what AS210973's mirror disagreement teaches about trusting the record, Every monitor that watches the routing table tells a slightly different story about the small Vienna network operated by DATAMATIX Datensysteme GmbH. Reading those differences carefully — rather than averaging them away — is the fastest way to learn which layers of the internet's public record a reader can actually trust.Medium confidence
• Editorial contextThe fourth prefix: DATAMATIX's 149.62.35.0/24 and the gap between owning a block and controlling a route, BTW's previous reporting on the Vienna data-systems company DATAMATIX Datensysteme GmbH examined three of the four IPv4 prefixes its autonomous system AS210973 announces, and each examination turned on the same structural tension: registry records, routing announcements, routing-registry objects and cryptographic authorizations do not converge on a single name. One prefix was left unexamined. This report closes that gap — and finds that the fourth prefix, 149.62.35.0/24, answers the ownership question cleanly in the registry while still failing the consistency test everywhere else that matters.Medium confidence
• Editorial contextTwo prefixes, three answers: the disputed registry record behind AS210973's 212.236.x space, DATAMATIX Datensysteme GmbH, a Vienna data-systems company, has run AS210973 since the RIPE NCC allocated the number to it on 30 July 2021. Prior reporting closed the chain from that registry record to the operating business and mapped the layered dependency the network's routes actually follow. One thread stayed open: who, if anyone, is the legitimate holder of two of the four IPv4 prefixes the network announces, 212.236.9.0/24 and 212.236.10.0/24. This briefing pulls the public record apart into three separate control planes and finds they do not converge on a single name.Medium confidence
• Editorial contextThe wireless vendor that owns an AS: DATAMATIX, AS210973 and what routing footprints cannot prove, Public routing records give DATAMATIX Datensysteme GmbH a tidy identity: holder of AS210973 since 30 July 2021, five originated prefixes, three named upstreams, 768 IPv4 addresses. The company's own catalogue tells a different story — industrial radio systems engineered to work without the public internet. Read together, the two records form an unusually clean lesson in what routing data proves, what it merely suggests, and what it cannot show at all.Medium confidence
• Editorial contextThree upstream names, one ladder: where AS210973's routes actually travel, DATAMATIX Datensysteme GmbH announces four IPv4 /24s and one IPv6 prefix under AS210973, and the routing databases reviewed here attach the same three upstream names to the network. The structure behind those names is the finding: the upstreams overlap each other through a shared top network, the route objects for both 212.236.x prefixes are maintained by one of the upstreams, and their visibility depends on larger aggregates that the same upstream announces.Medium confidence

Source basis

• public registry sourceDATAMATIX's public recordHigh confidence
• RIPEstat ASN overview for AS210973RIPEstat provides public routing and registry context for ASN 210973, useful for confirming that the ASN exists in the RIPE ecosystem and linking analysis back to the same number resource.High confidence
• RIPE Database web query for person/role handle DA10324-RIPERIPE Database query interface can be used to inspect the public object for handle DA10324-RIPE, the handle associated with DATAMATIX in the aut-num-related registry context.High confidence

How to read these connections

• Address compositionThe visible prefix footprint is IPv6-only with 1 announced prefixes.Medium confidence

Related research

• Primary articleWho actually runs inside Datamatix's 212.236.10.0/24: the service layer the registry cannot answerHigh confidence
• Primary articleDATAMATIX AS210973: what the live record proves about real operationHigh confidence
• Primary articleRegistered, authorised, and still unproven: what DATAMATIX's live posture says about operating a networkHigh confidence
• Primary articleFive prefixes, five answers: what AS210973's mirror disagreement teaches about trusting the recordHigh confidence
• Primary articleThe fourth prefix: DATAMATIX's 149.62.35.0/24 and the gap between owning a block and controlling a routeHigh confidence
• Primary articleTwo prefixes, three answers: the disputed registry record behind AS210973's 212.236.x spaceHigh confidence
• Primary articleThe wireless vendor that owns an AS: DATAMATIX, AS210973 and what routing footprints cannot proveHigh confidence
• Primary articleThree upstream names, one ladder: where AS210973's routes actually travelHigh confidence
• Primary articleWhen the Monitors Disagree: AS210973's 194.0.132.0/24 and the Limits of Routing EvidenceHigh confidence
• Primary articleDATAMATIX and AS210973: Closing the Evidence Chain From Registry Record to Operating BusinessHigh confidence
• Primary articleDATAMATIX and AS210973: The Operating Business Still Has to Be ProvenHigh confidence
• Primary articleDATAMATIX and AS210973: From Network Visibility to a Testable Operating BusinessHigh confidence
• Primary articleDATAMATIX and AS210973: What Public Routing Evidence Can—and Cannot—ProveHigh confidence