Summary

  • AS210973 (DATAMATIX-AS) was allocated by RIPE NCC on 30 July 2021 to DATAMATIX Datensysteme GmbH, a Vienna-registered LIR, and 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 — plus one IPv6 prefix.
  • Three upstreams attach to the network across independent databases — AS8218 (Zayo Infrastructure France SA), AS8245 (Video-Broadcast GmbH) and AS24953 (NETPLANET GmbH) — but the retained RIPE aut-num policy names only AS8245 and AS24953, and AS-SET membership explains how the third propagates anyway.
  • Both 212.236.x /24s carry route objects maintained by AS8245-MNT and sit inside larger 212.236.0.0 aggregates that AS8245 announces; their reachability is a layered dependency on Video-Broadcast's infrastructure rather than an independent capability of the leaf network.
  • Registrant labels attached to the two /24s — Clemens Schmikal and Rapid Solution Development — match neither DATAMATIX nor each other, an AS8218-versus-aut-num contradiction is unresolved, and bogon flags on the network and both prefixes remain unexplained in the retained records.

A routing table entry for a small network reads like an independent act: one origin, one announcement, one set of providers. The public record for AS210973 rewards a closer look, because the three upstream names attached to it do not describe three independent contracts, and the two prefixes at the center of this examination carry registrant designations that match neither the operator nor each other.

The sections below assemble that record as the public databases render it, keep every claim attached to the record that states it, and draw the one structural conclusion that survives the contradictions: this network's reachability is a layered, shared dependency — not a standalone table position a small operator owns.

The registry record and its boundaries

The entity side of the record is unusually clean, and it is worth stating in full before complicating it. The operator behind AS210973 is DATAMATIX Datensysteme GmbH, a Vienna-registered company operating as a Local Internet Registry under RIPE NCC; the IPgeolocation ASN record retained for this article reproduces the underlying RIPE organization data — organization handle ORG-DDG16-RIPE, an address at Mrzstraße 1 in the 1150 Wien postal district, and a commercial-register entry recorded as FN240683x https://ipgeolocation.io/browse/asn/AS210973. The autonomous system itself, DATAMATIX-AS, was allocated on 30 July 2021 under RIPE NCC and recorded under country code AT; the same RIPEstat record states that the network is 'not seen in RIS as transiting', a formulation consistent with a customer network that originates its own space and forwards nothing for others https://stat.ripe.net/AS210973.

The route views enumerate the origin set the same way everywhere: four IPv4 /24s — 149.62.35.0/24, 194.0.132.0/24, 212.236.9.0/24 and 212.236.10.0/24 — plus one IPv6 prefix, with three upstreams attached to the network: AS8218, AS8245 and AS24953 https://bgp.gibir.net.tr/as/210973. BigDataCloud's ASN lookup returns the same operator identity and the same three-way connection picture https://www.bigdatacloud.com/asn-lookup/AS210973.

That convergence is worth stating plainly, because the remainder of the article is built on exceptions to it. Where several independent databases agree, agreement itself is evidence. Where they disagree — on whether a third upstream actually carries the traffic, on who the registrants of two prefixes are, on whether the network announces space outside its delegation — the disagreement is the finding, and each side of it is named below.

One evidentiary boundary applies to everything that follows. The records reviewed here are public database renderings — route views, whois mirrors, ASN lookups — not contracts, corporate filings or statements from the parties. Each factual claim below is attributed to the record that states it; where a record's own phrasing is ambiguous, the ambiguity is preserved rather than promoted into a fact.

Three upstream names that overlap each other

Three upstream names attach to AS210973 across the retained set, and their mutual overlap is the structural finding of this article.

The retained ASN database record for AS8218 — which identifies that network's operator as Zayo Infrastructure France SA — lists AS210973 among AS8218's downstreams, alongside AS8245 and AS24953, and attaches a 3/5 count to the AS210973 entry; the retained view does not explain what the count measures https://iamroot.tech/asndatabase/?search=AS8218. The retained whois record for AS8245 identifies Video-Broadcast GmbH as the operator and lists AS8218 and AS24953 among its upstreams https://whois.ipip.net/AS8245. The retained record for AS24953 identifies NETPLANET GmbH, also in Austria https://ipv4.bgp.he.net/AS24953.

Assembled, the picture is a ladder rather than a fan-out. AS210973's three named upstreams are not three independent roads out of Vienna: AS8245 and AS24953 both appear as downstreams of AS8218, and AS8245's own upstream list includes both AS8218 and AS24953. Two of the three names sit below the third on the same ladder.

Whether AS8218 carries AS210973's traffic directly, or reaches it only through the middle rungs, is precisely the question the record does not answer. Nothing in the retained set shows an observed BGP path carrying AS210973's prefixes through AS8218's own customer cone; nothing in it excludes the possibility either. The distinction matters because redundancy on paper and redundancy in fact are different products. A customer that contracts three upstreams believes it has bought independent failure modes; when the upstreams are themselves entangled, those failure modes correlate.

If the top of the ladder has a bad day, the middle rungs offer no escape from it. On this record, the economically honest description of AS210973's connectivity is not three transit contracts but one dependency with three names attached.

The aut-num that never mentions Zayo

The sharpest contradiction in the record sits between the network's own registered policy and the reachability data compiled about it. The RIPE aut-num object for AS210973, as reflected in the retained bgp.tools record, names only AS8245 and AS24953 in its import and export policy, even though the same record lists AS8218 among the network's upstreams and lists AS210973 as a member of the AS-SETs all three upstreams consult for export filtering — as8218:as-at-customers, as8245:as-video-broadcast-at, as-vb and as-24953 https://bgp.tools/as/210973.

That combination stops being contradictory once it is read as routing machinery rather than as business structure. Export filters at an upstream are commonly generated from the AS-SET the customer declares, not from the aut-num's import and export lines, which age badly. If AS210973 is a member of as8218:as-at-customers, its routes are exported toward AS8218 regardless of what the aut-num says — which is consistent with the third-party listing of AS210973 as an AS8218 downstream, and consistent with the upstream attribution the aut-num itself omits.

On this reading the aut-num is stale policy text, and the AS-SET memberships are the live wiring.

The reading carries a discipline requirement: it is an interpretation, not a recorded fact. What the record establishes is the three data points — a registered policy naming two upstreams, a third-party attribution naming three, and AS-SET membership on all three sides. What it does not establish is observed carriage: RIPEstat's RIS-based statement concerns transiting, not which upstream carries the network's own announcements. The falsifiable form of the question is concrete. If AS210973's prefixes appear in BGP paths traversing AS8218's customer cone, Zayo's network carries them and the aut-num is simply stale.

If they appear only inside AS8245's and AS24953's cones, the top of the ladder is an AS-SET formality with no traffic behind it. The retained record supports neither arm; it only makes both testable.

Two 212.236.x prefixes: maintenance, aggregates and disputed owners

For the two prefixes at the center of this examination, the dependency stops being inferential and becomes itemized.

The 212.236.9.0/24 route view carries three signals at once. It shows a RIPE route object with origin AS210973, maintained under AS8245-MNT — the maintainer handle of Video-Broadcast, not of Datamatix — and created on 16 August 2021. It lists the registrant as Clemens Schmikal, a designation attached nowhere else in the retained set, even though the origin's inetnum identifies the range as DATAMATIX-01, assigned PA. And it attaches a bogon flag to the announcement https://bgp.he.net/net/212.236.9.0/24.

The 212.236.10.0/24 view mirrors the maintenance structure — a route object with the same origin, the same AS8245-MNT maintainer and the same 16 August 2021 creation date — while listing its registrant as Rapid Solution Development and carrying the same bogon flag. The same views show the covering 212.236.0.0/16 and its /18 and /19 less-specifics announced by AS8245 itself https://bgp.he.net/net/212.236.10.0/24. A /24 whose covering aggregates are announced by a different network is visible, in the first instance, because that other network's table makes it visible.

IPregistry's ASN record adds the classification that ties the two halves together: AS210973 is described as a leaf network with no downstreams and no direct peering agreements, and 212.236.10.0/24 is labelled SUB-ALLOCATED PA — registry language saying the range was not allocated directly to the network announcing it, but sub-allocated out of a larger block https://ipregistry.co/AS210973.

The registrant layer therefore diverges from the operator layer on both ranges, and the retained set contains nothing that connects Clemens Schmikal or Rapid Solution Development to DATAMATIX Datensysteme GmbH, to Video-Broadcast, or to each other. The boundary is stated explicitly: these are third-party database designations for the two ranges; the records do not establish whether the named parties are customers, predecessor holders, administrative contacts, related companies or data artifacts; and this article therefore treats the operational ownership of both /24s as unresolved rather than adopting any label as the answer.

IPinfo's record for 212.236.9.0/24 adds two details that pull in opposite directions: the range is recorded as RPKI-valid with a ROA issued for DATAMATIX, and the domain IPinfo associates with the range is video-broadcast.at https://ipinfo.io/AS210973/212.236.9.0/24. Authorization in the operator's name alongside an upstream-adjacent domain on the same range is the signature a layered dependency produces; nothing in the retained set explains the domain association.

The bogon flags that will not reconcile

Hurricane Electric's ASN record flags AS210973 itself as announcing bogons, and the same site's prefix records attach the flag to both 212.236.x ranges as well https://bgp.he.net/AS210973. A bogon flag is the route view's classification for announcements outside what the tool recognizes as legitimate delegation — in plain terms, space showing up where the view says it should not.

The flags are hard to square with the delegation record retained here, and the tension is reported rather than resolved. RIPE delegation data exists for both ranges — an inetnum identifier for 212.236.9.0/24, sub-allocation labelling and route objects for both — and the origin on each announcement matches the delegated holder's system.

Three explanations fit the retained facts without being distinguishable from them: the flags are artifacts of how the flagging tool handles these ranges; the announcements travel through paths the tool cannot map to the delegation records; or space related to these ranges is genuinely being announced beyond delegation somewhere inside the wider 212.236.0.0/16. The classification belongs to the source, not to this article, and its persistence or clearing on a dated re-check is one of the monitoring indicators below.

What a small LIR's reachability is actually made of

Strip the record to its structural content and AS210973's reachability is composed of five elements: an allocation from RIPE NCC dated 30 July 2021; route objects maintained by an upstream; covering aggregates announced by that same upstream; AS-SET memberships the three upstreams consult; and a registered policy document that names only two of the three networks involved. Exactly one of the five — the allocation — is unambiguously in the operator's hands. BTW's directory entry for Datamatix tracks the entity behind these records https://btw.media/en/directory/datamatix.

That composition is the general condition of small LIR networks rather than a peculiarity of this one, and it has a clean economic reading. A small operator's table position is an asset it may not own: whoever maintains the route objects and announces the covering aggregates holds operating control over whether the operator's customers are reachable at all. The public record for AS210973 makes that control legible — which is rarer than it sounds, because in most networks it stays invisible.

The bounded conclusion is this. On the retained record, AS210973's announcements travel through a layered structure in which Video-Broadcast's AS8245 maintains the two 212.236.x route objects, announces the covering aggregates, and sits — with NETPLANET — under Zayo's AS8218 in the third-party reachability data: a shared dependency rather than three independent contracts.

The next observable conditions are specific: AS210973's prefixes appearing inside, or staying outside, AS8218's customer cone in dated BGP paths; registry-side changes to the maintainer handles or registrant labels of the two /24s; and the persistence or clearing of the bogon flags. The material uncertainty is equally specific: who operates the two 212.236.x ranges — a question the public record keeps open, and that only registry-side movement or the parties themselves can close.