Issues with time-series cache

Incident Report for Clarify

Update

We are continuing to monitor for any further issues.
Posted Feb 12, 2026 - 12:06 CET

Update

All data should now have been synced.
Posted Feb 12, 2026 - 11:35 CET

Monitoring

We have managed to get the sync operational, and are experinecing that the backlog is being processed. All data should soon be available for query.
Posted Feb 12, 2026 - 11:33 CET

Update

The effect on the customer is that arround 16% of items, will appear to not have received data from arround 04:30 CET or slightly later. However, data is persists in cold storage, and will become available once the problem is resolved.

Again, we appologize for the inconvinence, and will update you as soon as we have a solution.
Posted Feb 12, 2026 - 10:48 CET

Identified

We have discovered that there is an issue with 1/6 the time-series cache nodes, starting at 04:30 CET tonight.

The effect on customers is that ~16% of queried items will appear to either be missing data, or return data at a flaky/degrated perforamce. We have verified that this is a cache issue only, and are looking into fixing it.

We have verified that the affected data is reaching cold storage, and is therefore not lost.

We appologize for the inconvinence.
Posted Feb 12, 2026 - 10:31 CET
This incident affects: Access to data (Query time-series).