Summary

  • The organisation object ORG-TA1587-RIPE, registered to Tideo ApS, has existed in the RIPE Database since 9 September 2021, and its last recorded modification is dated 13 May 2026.
  • Autonomous system number AS210972 carries the registry name TIDEO-AS and is associated with that organisation object.
  • RIPE RIS data records AS210972 as last seen originating the prefix 45.95.115.0/24 on 22 October 2025 at 08:00 UTC, and on the observation date of this report it is not seen originating any address space.
  • The defensible conclusion is narrow: the registry documents a holding that remains on the books, not a network that is still carrying traffic.

What the public records show

The RIPE Database keeps the organisation object ORG-TA1587-RIPE, whose registered name is Tideo ApS. According to the registry's own public query, the object was created on 9 September 2021 and its last recorded change is dated 13 May 2026. A maintained organisation object means the registry continues to hold a responsible entity with declared contacts; it does not mean that entity is passing traffic.

The same set of records ties autonomous system number AS210972 to that object. The registry name of the AS is TIDEO-AS. The public page for that AS in the RIPE NCC statistics service is the source of the routing observation cited here.

The timeline that matters

The order of the dates is the core of this case. The organisation object was created in 2021. The last prefix announcement observed in RIS data is 22 October 2025 at 08:00 UTC for 45.95.115.0/24. The object was last modified in May 2026, roughly seven months after that last observed announcement. And on this report's observation date, AS210972 is not seen originating any address space in the RIS view.

That order matters because it inverts the usual intuition. The most recent timestamp in the registry corresponds to an administrative task — an object update — not to routing activity. A reader who treats presence in the registry as proof that a network is in service commits a category error: they are reading an accountability obligation as an operations log.

What remains unresolved

The public registry record alone cannot settle several things. Whether contact handle TA8097-RIPE denotes a natural person or a role account is not resolved by the public material reviewed here. Why AS210972 stopped being observed originating address space is not documented in the public records. And whether 45.95.115.0/24 was transferred, returned, or remains allocated to the organisation has not been established.

These are not peripheral gaps. They are precisely the points where any stronger claim about network operation would require evidence the registry does not supply. The distinction between registry maintenance and network operation is not a technicality: it decides whether a reader may treat the object's existence as a signal of activity.

Why an organisation keeps an object that no longer routes

There are practical and legitimate reasons to keep an organisation object without announcing address space. An organisation may be holding the allocation, preparing a change of ownership, keeping its books consistent with the registry, or simply not having asked for removal. The public material reviewed here does not identify which of these applies to Tideo ApS, and this report does not assert any of them as fact. What can be stated is that the object was created in 2021, that it is still present, that its last recorded modification is dated May 2026, and that this most recent date does not correspond to any observed prefix announcement.

The difference between a live record and a live network

For an institutional observer, the operational lesson is evidence discipline. Registry presence and routing activity are two different sources with two different lifecycles. One can outlive the other by months or years. When a decision — by a counterparty, an allocator or a supervisor — leans on the object's existence as a substitute for operation, that decision rests on an indicator that was never designed to measure it. Verifying operation requires routing observation, not just a row in a database.

Primary sources for this report: the query of the organisation object ORG-TA1587-RIPE in the RIPE Database and the AS210972 page in RIPE Stat. Entity context is in the Tideo ApS directory entry.