Summary

  • AS210973, registered to DATAMATIX Datensysteme GmbH in Vienna and allocated by RIPE NCC on 30 July 2021, originates four IPv4 /24s plus 2a10:fd00::/32. The service layer of each prefix gives a different answer about who operates inside it. https://ipinfo.io/AS210973
  • 149.62.35.0/24 is the clearest Datamatix-attributed block: its RIPE inetnum carries netname AT-DATAMATIX-20180831, ALLOCATED PA status under ORG-DDG16-RIPE, an abuse contact in the Datamatix domain, and an associated-domain field of datamatix.at. https://ipinfo.io/AS210973/149.62.35.0/24
  • 212.236.9.0/24 is assigned to AS210973 in the registry, yet its Domain field reads video-broadcast.at, its route object is maintained by AS8245-MNT (Video-Broadcast GmbH's maintainer) since 16 August 2021, and IPinfo records zero hosted domains on the range. https://ipinfo.io/AS210973/212.236.9.0/24
  • 194.0.132.0/24 holds the only two hosted domains IPinfo counts across the entire ASN, on 194.0.132.90 and 194.0.132.173 — meaning all of the ASN's visible hosting sits in a single /24 that CIDR Report omits from its AS view altogether. https://ipinfo.io/AS210973
  • Monitors disagree on what AS210973 announces: CIDR Report lists three /24s, RIPEstat lists four without showing the IPv6 block, and IPGeolocation lists four IPv4 routes plus 2a10:fd00::/32. https://www.cidr-report.org/cgi-bin/as-report?as=AS210973&view=2.0

AS210973 (DATAMATIX-AS) belongs to a real, documented Vienna company: DATAMATIX Datensysteme GmbH, whose RIPE organisation ORG-DDG16-RIPE was allocated the autonomous system number on 30 July 2021. The ASN originates four IPv4 /24s — 149.62.35.0/24, 194.0.132.0/24, 212.236.9.0/24 and 212.236.10.0/24 — and one IPv6 block, 2a10:fd00::/32. https://bgp.he.net/AS210973 IPinfo's AS page lists the same four netblocks plus the IPv6 block and names three peers: AS8218 (Zayo Infrastructure France SA), AS8245 (Video-Broadcast GmbH) and AS24953 (NETPLANET GmbH). https://ipinfo.io/AS210973 The company's own business — wireless data links for vehicles, Secall-CAN fleet management for mining equipment, LoRaWAN devices — has no hosting or cloud product line. https://btw.media/en/who-runs-inside-datamatix-212-236-10-0-24

The question this article takes up is the one left open after prior coverage of 212.236.10.0/24: do the other prefixes behave like that one, or differently? The method is the same layer-by-layer reading of reverse-DNS delegation, abuse contacts, attribution labels and hosted-domain counts, using RIPE's own documentation of how in-addr.arpa delegation defines the operator-controlled service layer. https://www.ripe.net/manage-ips-and-asns/dns/reverse-dns/

149.62.35.0/24: the Datamatix-branded block

The RIPE inetnum for 149.62.35.0/24 reads netname AT-DATAMATIX-20180831, status ALLOCATED PA, organisation ORG-DDG16-RIPE, country AT, with the abuse contact recorded to the Datamatix domain through abuse-c AR70385-RIPE. https://ipinfo.io/AS210973/149.62.35.0/24 IPinfo's Domain field for the range reads datamatix.at. https://ipinfo.io/AS210973/149.62.35.0/24 This is the only /24 in the set where registry identity, abuse contact and attribution label all agree on Datamatix.

One ambiguity deserves note: the organisation object carries a personal e-mail distinct from the abuse address — a mirror of RIPE whois text that flags where responsibility for the block and the contact for abuse of it are recorded differently. https://ipinfo.io/AS210973/149.62.35.0/24

212.236.9.0/24: the video-broadcast.at label with nothing hosted

212.236.9.0/24 sits inside RIPE-allocated 212.236.0.0/16, and its route object (origin AS210973) is maintained by AS8245-MNT — the maintainer associated with Video-Broadcast GmbH — with a creation date of 16 August 2021. https://bgp.he.net/net/212.236.9.0/24 Hurricane Electric lists the origin registrant as DATAMATIX Datensysteme GmbH but the prefix registrant as 'Clemens Schmikal', a RIPE person object (CS145-RIPE) maintained by AS8245-MNT. https://bgp.he.net/net/212.236.9.0/24 IPinfo labels the range's Domain field as video-broadcast.at while recording zero hosted domains across the range. https://ipinfo.io/AS210973/212.236.9.0/24 The covering aggregates for the 212.236.x space (212.236.0.0/16, /18 and /19) are announced by AS8245. https://bgp.he.net/net/212.236.9.0/24

This is the same split pattern as 212.236.10.0/24, minus one element: the .10/24 showed reverse names like rsd-tik.rom.video-broadcast.at and an abuse contact in the video-broadcast.at domain; https://ipinfo.io/212.236.10.1 the .9/24 shows the domain label and the maintainer but no visible hosted content at all.

194.0.132.0/24: all of the ASN's visible hosting, and one monitor's blind spot

IPinfo counts exactly two hosted domains across the whole of AS210973 — on 194.0.132.90 and 194.0.132.173, both inside 194.0.132.0/24. https://ipinfo.io/AS210973 This makes the block the only place in the Datamatix-originated space where visible hosting exists, and the mirror context (BigDataCloud and checkip records describe the range's network setting) confirms third-party interest in it. https://www.bigdatacloud.com/network-lookup/194.0.132.0/24 Yet CIDR Report's AS210973 view lists only three prefixes — 149.62.35.0/24, 212.236.9.0/24 and 212.236.10.0/24 — and omits 194.0.132.0/24 entirely, while RIPEstat lists it at a 25% origination share alongside the other three. https://www.cidr-report.org/cgi-bin/as-report?as=AS210973&view=2.0 A reader relying on CIDR Report alone would conclude the one /24 that actually hosts anything does not exist.

The IPv6 block: partial visibility

2a10:fd00::/32 appears in IPGeolocation's route list and, per prior BTW coverage citing bgp.tools, in that tool's five-prefix set — but RIPEstat's reported view does not display it. https://ipgeolocation.io/browse/asn/AS210973 The IPv6 service layer has no hosted-domain counts or reverse-DNS evidence in the sources assembled here; it remains the least-documented part of the network.

What the split means

The evidence permits precise per-prefix sentences, not a unified verdict. Registry ownership is clear in every case. The service layer diverges: one /24 answers to Datamatix in registry, abuse and attribution; one /24 carries a foreign domain label with nothing visible behind it; one /24 holds all the hosted domains and is missing from one major monitor's view; one /24 was already shown to belong, in service terms, to the video-broadcast.at namespace. https://btw.media/en/datamatix-as210973-prefix-attribution Whether this reflects deliberate segmentation of a shared address portfolio, historical allocations carried forward in registry objects, or mirror-data artifacts is a question the public record does not answer — and the per-prefix divergence itself is the strongest evidence that treating "the Datamatix network" as a single behavioural unit is a category error.