Summary

  • DATAMATIX Datensysteme GmbH, an industrial wireless systems vendor registered in Vienna, has held AS210973 since the RIPE NCC allocated it on 30 July 2021. The network originates five prefixes — four IPv4 /24s and one IPv6 block — totalling 768 IPv4 addresses, carried through three upstream networks that prior reporting showed are themselves entangled under shared parent infrastructure.
  • Public monitors still disagree on what AS210973 announces: RIPEstat and bgp.tools count four IPv4 prefixes including 194.0.132.0/24, while CIDR Report, Hurricane Electric, Qrator, WorldIP and Whisper count three; the IPv6 prefix 2a10:fd00::/32 is counted everywhere except RIPEstat's detail table. RPKI authorization covers all five prefixes, so the split is a measurement artefact, not an authorization defect.
  • The company's own product pages describe Secall-CAN, a fleet-management radio system for open-pit mining that runs on dedicated licensed frequencies with on-premises software and, by the vendor's statement, does not rely on external networks or cloud, alongside UniNode LoRaWAN end-devices for industrial telemetry.
  • The three records — registry, routing, catalogue — are each verifiable, but together they underdetermine the business. No public source names customers, revenue, or the operator of the routers. The case is a standing warning: a routing footprint is proof of a footprint, not proof of a business.

A closed registry identity

The administrative record needs little re-litigation, because prior reporting closed it. RIPEstat's resource view for AS210973 names the network DATAMATIX-AS, attributes it to DATAMATIX Datensysteme GmbH, records the RIPE NCC allocation status as ALLOCATED with a registration date of 2021-07-30, and places the holder in Austria. The same view carries the network's routing detail — four IPv4 prefixes at an equal 25% share of origination, with the AS not seen in RIS as a transit network — and its timestamps run from 11 September 2026 to 26–27 September 2026. The routing-and-registry aggregator bgp.tools and the IRR database mirror published by Hurricane Electric (both examined in the monitor comparison below) agree, the latter showing the matching aut-num block: as-name DATAMATIX-AS, organisation ORG-DDG16-RIPE, status ASSIGNED, created 2021-07-30, last-modified 2023-06-05, source RIPE. The operator's imprint confirms the corporate entity behind all of it: DATAMATIX Datensysteme GmbH, registered in Vienna.

BTW's earlier reporting has already traced this chain in full: an English-language investigation followed the evidence path from public routing data through control to continuity here, and the monitor disagreement around 194.0.132.0/24 was then examined in separate reports published in German and in Chinese. That work closed the registry-to-business link and documented, layer by layer, how AS210973's reachability rides on aggregates and route objects maintained by others. None of it asked the question the operator's own catalogue now forces: why does a firm whose products are built to avoid the public internet hold an autonomous system at all?

What the monitors see — and where they split

Seven public views of AS210973's announcements, compared as they stood between late June and late September 2026, produce three different prefix counts.

  • RIPEstat's resource view, cited above, lists four IPv4 prefixes — 149.62.35.0/24, 194.0.132.0/24, 212.236.9.0/24 and 212.236.10.0/24 — at an equal 25% share of origination. Its prefix-detail table omits the IPv6 prefix 2a10:fd00::/32 that bgp.tools, Hurricane Electric, Qrator and Whisper count.
  • bgp.tools reports five originated prefixes, adding 2a10:fd00::/32, with three upstream adjacencies — AS8218 (Zayo Europe), AS8245 (Video-Broadcast GmbH), AS24953 (NETPLANET GmbH) — three peers, and a descriptive label on 212.236.10.0/24 reading 'Rapid Solution Development'.
  • Hurricane Electric's AS page, in a footer updated 30 June 2026 at 15:16 PDT, counts four originated and four announced prefixes (three IPv4, one IPv6), four RPKI-originated-valid with zero invalid, three observed peers, 768 originated IPv4 addresses, and 1,008 observed IPv4 AS paths against 639 IPv6 paths at an average length of roughly 4.49. The page also carries a standing flag that AS210973 announces bogons, without enumerating which.
  • CIDR Report lists exactly three prefixes — 149.62.35.0/24, 212.236.9.0/24, 212.236.10.0/24 — with 768 originated addresses, zero transit address space, three upstream adjacencies (AS24953, AS8218, AS8245) and zero downstream. Its exemplar AS paths read 2914 24953 210973 210973 210973 210973 for the first prefix and 6939 8245 210973 for the other two. 194.0.132.0/24 does not appear.
  • Qrator Radar, over the window 2026-05-20 to 2026-08-20, shows four prefix rows — 2a10:fd00::/32, 149.62.35.0/24, 212.236.9.0/24 and 212.236.10.0/24 — each marked RPKI ROA Valid and route object Valid, with 100% propagation counts of 381, 548, 562 and 562 respectively. 194.0.132.0/24 is absent from the rows.
  • WorldIP reports 768 announced IPv4 addresses across three prefixes, all last seen on 13 August 2026 at 10:18:12: 149.62.35.0/24 with 5,156 collector samples, 212.236.9.0/24 with 5,023 and 212.236.10.0/24 with 4,975. In the same page's registry-allocation table, 194.0.132.0/24 appears — with a reverse-DNS density of 0.0% — but not in the live BGP list.
  • Whisper, with AS data as of 7 August 2026 and hostname data as of 5 July 2026, counts four routed prefixes and three peers, reports no active MOAS conflicts, and states that every prefix announced by AS210973 is unique to that AS in its current snapshot. It counts five hostnames depending on the network across the four announced prefixes.

Authorization, by contrast, is unanimous where it can be checked. rpki-client's console shows two ROAs in the RIPE RPKI repository, both authorizing AS210973: one covers 212.236.9.0/24 and 212.236.10.0/24 (maxlen 24 each); the other covers 149.62.35.0/24 (maxlen 24), 194.0.132.0/24 (maxlen 24) and 2a10:fd00::/32 (maxlen 32). No monitor disputes the ROAs. The disagreement is about announcement, not authorization.

The divergence concentrates on the IPv4 prefix 194.0.132.0/24, and a second, smaller split runs through the IPv6 block. Two structural features of public measurement explain most of the gap. RIPEstat's own announced-prefixes documentation specifies a two-week default window and a min_peers_seeing default of 10, which explicitly excludes low-visibility or localized announcements: a genuinely announced prefix seen by too few peers can simply fail the threshold. Collection vantages differ in parallel. Qrator's propagation counts run to 381–562 vantage points; WorldIP's sample counts run to about 5,000; and CIDR Report's exemplar paths show traffic arriving through AS24953 for one prefix and through AS8245 for the other two. Whether the fourth prefix is announced this week therefore depends on which instruments are asked — the same conclusion BTW's German- and Chinese-language reports reached when they documented this disagreement in detail, and the latest data confirms the disagreement has not healed.

The product line that argues against dependence

The operator's own catalogue is the record's most surprising layer. DATAMATIX's product pages describe hardware and software for wireless data transmission to vehicles and objects. The flagship application is Secall-CAN, a fleet-management and radio-communication system for open-pit mining that runs on a dedicated licensed radio frequency, with software installed on the customer's own premises. The vendor's description of that system is unusually explicit about its independence: it does not rely on external networks or cloud services. Alongside it, the company develops UniNode LoRaWAN end-devices supporting Classes B and C — another technology whose value proposition is long-range, low-power transmission over a network the customer can host itself.

The Vienna corporate identity behind this catalogue was confirmed above; the catalogue itself fixes the business shape: a hardware-and-firmware vendor whose systems are designed to keep public networks out of the loop. A mining fleet that talks to its dispatcher over licensed radio does not transit AS210973. A LoRaWAN node reporting tank levels or machine states does not, in the architecture the vendor describes, depend on a BGP-reachable address.

Yet the routing record contains exactly the artefacts one would look for in an internet-facing business. The 212.236.10.0/24 range carries the identifier RSD-SUB1 with the description 'Rapid Solution Development' and is RPKI-valid under AS210973; IPinfo associates the autonomous system with the domain crashcars.at and shows a traceroute sample whose third hop lands at 212.236.10.251 inside AS210973. Whisper's five hostnames are the strongest public traces of anything internet-facing on the network — and they are meagre: one /24 with a development label, a single observed traceroute hop, five hostnames, and no verifiable service, customer or product behind them.

Why an AS at all? Three readings the record permits

The public record cannot answer why a radio-hardware vendor holds an autonomous system, but it constrains the possible answers. Three readings fit the evidence; none is proven.

The first is a hosted-services remnant. The 'Rapid Solution Development' label on 212.236.10.0/24 and the small hostname footprint fit a vendor that once — or still — runs development and support infrastructure on its own address space. Under this reading, AS210973 exists to make a handful of internal hosts reachable, and the 768 addresses are capacity that arrived with the block and will never be used.

The second is a resource-strategy hold. An AS number with four /24s is a transferable, leaseable asset in today's IPv4 market, and prior reporting on this network documented how its reachability is carried by upstream aggregates maintained by others. A firm holding licensed-radio expertise might reasonably have secured numbering resources at a moment when they were cheap to obtain, without ever building the commercial network the resources imply.

The third is a control-plane convenience for the product line itself. Radio base stations, gateways and support infrastructure sometimes terminate on fixed addresses for remote management. Under this reading, the AS is plumbing for the wireless systems, not a business line of its own — and the products' independence from public networks argues that this plumbing is minimal.

The record favours none of the three. What it does establish is the negative: nothing in it supports a cloud service. The directory category that collects this company is a classification of the footprint, not of the business; the footprint is 768 addresses carried by other people's aggregates, and the business, on its own account, sells systems that avoid networks.

What the footprint proves — and what it cannot

The verifiable facts form a short list. The registry identity is closed: AS210973 belongs to DATAMATIX Datensysteme GmbH, allocated 2021-07-30, holder in Austria. The routing footprint is real but thin: 768 IPv4 addresses across three or four prefixes depending on the instrument, five prefixes including IPv6 at most, carried by three upstreams. Authorization is complete: two ROAs cover all five prefixes. Maintenance is current: route objects valid and propagation complete across Qrator's three-month window, with last-seen timestamps of 13 August 2026 at WorldIP.

What the footprint cannot prove is everything commercial. No public source in this investigation shows a customer of AS210973, a price, a contract, a data centre, a staffed point of presence, or revenue attributable to the network. WorldIP's reverse-DNS density of 0.0% on the disputed prefix is a small but telling datum: address space held without hostnames is address space held, not address space used. The five hostnames Whisper counts are the entire visible payload of a five-prefix network — less than one hostname per 150 addresses.

A note on method. This report compares the operator's own pages with seven public monitor views as they stood between late June and late September 2026, including general ASN mirrors such as TheIpapi's entry for AS210973. Dates are attached to every figure because each monitor refreshes on its own clock; the routing data for this network is too small for any single monitor to resolve unambiguously, and the disagreement is itself the finding. BTW's directory record for the subject is maintained at its DATAMATIX entry.