Summary

  • The RIPE registry binds AS210972 to the organisation Tideo ApS and points its administrative and technical contact at a role object, TA8097-RIPE, not at a natural person.
  • The abuse channel is a third, separate object (ACRO42495-RIPE) on the organisation, so the party who answers a routing complaint is not the party named as the operational contact.
  • The record tells you exactly who is registered, and it stops there: nothing in it establishes whether the network is announcing, who staffs the role, or whether the abuse window is monitored.

The registration, as the registry states it

Three machine-readable RIPE NCC responses, retained in this run, carry the facts. The aut-num and organisation objects for AS210972 register the autonomous system with as-name TIDEO-AS and bind it to organisation ORG-TA1587-RIPE, whose org-name is Tideo ApS. The administrative contact, admin-c, is TA8097-RIPE, and the response marks that reference explicitly as referenced-type: role.

A second query, for the contact object itself, returns a record of type role: role: Tideo Administration, nic-hdl: TA8097-RIPE, with the address Tingvejen 30G, 6500 Vojens. Independently, RIPEstat's AS overview reports the holder of AS210972 as TIDEO-AS Tideo ApS.

So the registry is not ambiguous about ownership. It names a legal entity, a Danish private limited company form, a street address, an autonomous system number and a NIC handle. What it does not name anywhere in those three records is a person.

Two identities, two different jobs

The interesting detail is not that the contact is a role. Role objects are ordinary infrastructure in the RIPE Database, and most European operators use them. The detail that matters for escalation is where the two functions sit.

  • Operational contact: admin-c and tech-c resolve to TA8097-RIPE, the role labelled Tideo Administration.
  • Abuse contact: the organisation object carries abuse-c: ACRO42495-RIPE, a handle that is neither the autonomous system nor the administrative role.

In other words, if you are a network engineer with a routing problem, the registry sends you to the administration of the operator. If you are a security team filing an abuse report, the registry sends you somewhere else entirely. Nothing in the retained record establishes who reads either mailbox, whether the two are staffed by the same team, or whether ACRO42495-RIPE is a monitored desk, an alias or an outsourced function.

What the record cannot tell you

This is where the accountability question becomes concrete, and also where the evidence stops. The retained excerpts contain no incident record, abuse report, enforcement action, dispute or dated event involving AS210972 or TA8097-RIPE. That is a documented absence in three short registry responses, not a finding about the operator's conduct. It is equally true that the same responses establish nothing about whether the network is announcing routes in the observed period; routing visibility was not measured for this article.

Two boundaries are worth stating plainly.

  1. Registration is not operation. A correct, complete registration proves that someone filed it and maintains it. It does not prove the company is trading, that the AS is in use, or that the address is current.
  2. A role is not a person. A role object is a durable, transferable handle. That is precisely its advantage: staff turn over, the handle survives. It is also its cost: the registry can be entirely accurate and still name nobody who can be held to a decision.

Why this matters beyond one Danish registration

The same pattern recurs across European registrations: an organisation holds the resource, an administrative role holds the contact fields, a separate abuse handle holds the complaint window, and no natural person is named in any of them. For an investigator, that structure is legible and honest. For an affected third party trying to reach a decision-maker, it is a chain of handles with no accountable endpoint.

What the record does provide is a fixed, checkable starting point: a named organisation, a NIC handle, an address, an AS number and a distinct abuse window. Whether that chain leads anywhere is testable — and it is worth testing before treating a registry entry as proof of an operator, or a role handle as proof that someone is listening.

The directory entry for this registration is here: Tideo Administration.