Summary

  • AS216408 is recorded in public routing data as an Estonian content network registered to Tavid AS on 24 August 2023, originating one IPv4 and one IPv6 prefix and peering with Telia Eesti and Tele2 Sverige.
  • The registration object behind it lists dummy contact handles and carries an explicit note that personal data has been removed, so it attributes a network to an organisation and to no natural person; on 17 October 2026 no inspected source named an individual in connection with it.

What the record actually says

Start with the object rather than with the name attached to it. Public routing data records AS216408 as an autonomous system registered to Tavid AS, under the RIPE region identifier ee.tavid, registered on 24 August 2023 (bgp.tools record for AS216408). The same record classifies it as a content network and shows it originating a single IPv4 prefix, 185.87.216.0/24, and a single IPv6 prefix, 2a13:85c0:100::/40. Upstream relationships are visible too: the network is observed peering with Telia Eesti AS3249 and Tele2 Sverige AB AS1257.

None of that is thin. It is a compact, coherent, checkable description of a working network: one organisation, two address families, two transit counterparties. A second, independent routing observatory records the same assignment to Tavid AS in Estonia and, like the first, names no individual in connection with the network (Hurricane Electric BGP record for AS216408).

The contact fields explain the silence

The interesting part is not the absence of a name. It is the mechanism that produces it.

The registration object behind AS216408, as rendered publicly, lists its administrative and technical contacts as DUMY-RIPE. It carries status ASSIGNED and keeps two maintainers, RIPE-NCC-END-MNT and lir-ee-tavid-1-MNT. And it carries a remark stating that data generally regarded as personal has been removed from the object (bgp.tools record for AS216408).

That is a privacy mechanism, not a gap in the record-keeping. Registry objects in the RIPE service region have been systematically depersonalised, and the maintainer chain above shows the ordinary commercial path: an end-user maintainer for the organisation alongside the registry's own end-marker. Anyone who hoped to read an operator's name out of an inetnum or aut-num contact field is reading a document that was deliberately rebuilt so that this reading would fail. The object still tells you who answers for the resource at the organisation level.

It no longer tells you which human being sits behind that organisation, and it says so in plain text.

Where a person-level claim would have to come from

If a claim about a named individual's operating role is to survive scrutiny, the evidence has to come from somewhere the redaction does not reach. There are four plausible places, and none of them was obtained in this reporting set.

A corporate filing would do it: a business registry entry naming the person as a board member, officer or shareholder of the organisation that holds the network. A court or regulatory document would do it. A first-party statement, on the record, from the person or the company would do it. Contemporaneous technical or procurement records naming the individual in an operational capacity would do it. Each of these carries a verb the registry object cannot: "serves as", "was appointed", "signed", "directed".

What the routing record can carry is narrower and still useful: "is recorded as", "originates", "is observed peering with". Those verbs describe a network and its holder. They do not describe a person, and stretching them until they do is the specific failure this piece is written to make visible.

The retrieval gap on the day

One further fact belongs in the open. The conventional RDAP addresses for the AS216408 registration record did not return the object content on 17 October 2026 (rdap.org autnum endpoint for AS216408; RIPE NCC RDAP aut-num endpoint for AS216408). The object text quoted above was read through the public rendering of the record, not through a first-party registry JSON response.

That is a retrieval outcome on a date, not a statement about the object's existence. Registry endpoints fail, rate-limit and time out. But it matters for how the finding should be weighted: a reader who wants the strongest available version of this record should still pull it directly, and should treat the rendering used here as evidence of what the public surface displays rather than as a substitute for the registry's own response.

What remains open, and what does not

Three things are unresolved. Whether any relationship exists between Indrek Kalluste and Tavid AS or AS216408 is not established by any source inspected here. What the object contained before personal data was removed cannot be recovered from the rendering. And whether the RDAP failure was transient cannot be settled from a single day's retrieval.

One thing is not open. As of 17 October 2026, no source inspected in this reporting set named Indrek Kalluste, or any other natural person, in connection with AS216408 or Tavid AS (bgp.tools record for AS216408). That sentence is a statement about a bounded evidence set on a stated date. It is not a statement about anyone's conduct, employment or role, and it should never be read as one. The distinction is the whole point: a record can be silent about a person without that silence meaning anything about the person.