Summary

  • AS210973 (DATAMATIX-AS, held by DATAMATIX Datensysteme GmbH, Austria, LIR at.datamatix) originates 212.236.9.0/24 and 212.236.10.0/24, and both prefixes carry valid RPKI ROAs with the origin AS and max-length 24. Origination and cryptographic authorization are both attributable to DATAMATIX.
  • The registry layer says something else. Both route objects carry origin AS210973 but are maintained by AS8245-MNT — the maintainer of Video-Broadcast GmbH, holder of the enclosing 212.236.0.0/16 allocation — not by any DATAMATIX maintainer. Both objects were created on 16 August 2021.
  • Third-party mirrors disagree on the delegation record: IPregistry lists 212.236.9.0/24 as ASSIGNED PA with identifier DATAMATIX-01, and 212.236.10.0/24 as SUB-ALLOCATED PA under an organization named Rapid Solution Development. Neither label matches the operating company.
  • The canonical RIPE database pages for both /24s could not be retrieved during this reporting window; every object-level field below comes from attributed third-party mirrors and should be read as evidence candidates, not verified registry state.

Three planes, three answers

Routing registries answer three different questions through three different mechanisms, and for these two prefixes the mechanisms do not converge.

The first plane is origination: which autonomous system announces the prefixes in the global routing table. Here the answer is unambiguous. RIPEstat identifies AS210973 as DATAMATIX-AS, held by DATAMATIX Datensysteme GmbH with an allocation dated 2021-07-30, and associates both 212.236.x /24s with it (RIPEstat). Hurricane Electric's prefix pages likewise show both prefixes announced with origin AS210973, whose registrant is DATAMATIX Datensysteme GmbH (212.236.9.0/24; 212.236.10.0/24).

The second plane is the registry database itself. The enclosing 212.236.0.0/16 is a RIPE allocation attributed to Video-Broadcast GmbH, the Austrian LIR behind AS8245 (ORG-CA2-RIPE), and the /16, /18 and /19 aggregates covering these addresses are originated by AS8245 (IPIP.NET whois mirror; 212.236.0.0/16 netblock). The route objects for both /24s — origin AS210973, created 2021-08-16 — are maintained by AS8245-MNT, Video-Broadcast's maintainer, not by a DATAMATIX maintainer (Robtex mirror of RIPE data). AS210973's own aut-num, by contrast, is maintained by RIPE-NCC-END-MNT and lir-at-datamatix-1-MNT with organization ORG-DDG16-RIPE (Robtex), so the asymmetry is visible inside a single source: DATAMATIX maintains its AS number, Video-Broadcast's maintainer maintains its route objects.

The third plane is cryptographic authorization. Both prefixes have RPKI ROAs with origin AS210973 and max-length 24, with rpki-ov-state listed as valid in the Robtex mirror of the RIPE objects, and bgpthingy shows visible RIPE-TAL ROAs covering 149.62.35.0/24, 194.0.132.0/24, 212.236.9.0/24, 212.236.10.0/24 and 2a10:fd00::/32 (bgpthingy). An ROA authorizes origination; it says nothing about title.

What the delegation record says — and who it fails to name

Mirrors classify the two prefixes differently, and neither label resolves the question. IPregistry lists 212.236.9.0/24 as ASSIGNED PA with identifier DATAMATIX-01 — a netname that at least ties it to the company — while 212.236.10.0/24 is listed as SUB-ALLOCATED PA under the organization Rapid Solution Development (IPregistry). Hurricane Electric goes further in a different direction: it lists the prefix registrant of 212.236.9.0/24 as Clemens Schmikal and of 212.236.10.0/24 as Rapid Solution Development (212.236.9.0/24; 212.236.10.0/24). Schmikal is a RIPE person object (CS145-RIPE) maintained by AS8245-MNT, alongside Christian Forstner (CF32-RIPE) (IPIP.NET whois mirror). A person-object label rendered as a prefix registrant is more plausibly stale maintainer-attached metadata than evidence of individual ownership.

For contrast, IPregistry lists DATAMATIX's other two /24s — 149.62.35.0/24 and 194.0.132.0/24 — as ALLOCATED PA to Datamatix Datensysteme GmbH (IPregistry). Whatever arrangement governs the 212.236.x space, it is recorded differently from the prefixes DATAMATIX plainly holds.

The retrieval gap, published as a finding

The canonical RIPE database pages for both /24 objects — the db-web-ui queries at 212.236.9.0/24 and 212.236.10.0/24 — could not be inspected as rendered documents during this reporting window, because they are client-side applications and no verbatim object text was obtained from those URLs. Three subsequent attempts to retrieve the canonical records through the RIPE REST API failed provider-side and produced no usable artifact. Every object-level field cited here therefore comes from attributed third-party mirrors of RIPE data, which may lag the live database.

That gap is itself part of the story: for a disputed delegation, the difference between "recorded" and "verified against the canonical record" is exactly the difference that matters, and no public aggregation closes it on its own.

What a third-party-maintained route object implies

The mnt-by field is an authorization handle. Because AS8245-MNT — Video-Broadcast GmbH's maintainer — maintains the route objects for two prefixes originated by AS210973, whoever controls that maintainer can create, modify or delete the IRR objects that feed filtering policies across the industry. DATAMATIX's RPKI ROAs sit outside that channel, which is precisely why the two authorization planes are worth checking separately: IRR maintenance and RPKI validation can be held by different parties, and here the record shows them split.

The split is consistent with several arrangements — a sub-allocation or delegated use inside Video-Broadcast's /16, a courtesy or legacy object from 2021, or a commercial lease — and the public record does not discriminate between them. No transfer record, registration agreement or sub-allocation contract tying any party to either /24 is visible in the sources reviewed.