While resolving the problem, we had to replace some cluster resources. This appear to have caused some unexpected down-time for the MQTT server between 20:30 - 21:00 CET (UTC+01:00).
If you are writing data via MQTT with QoS setting 0 (fire and forget), or if the client lacks caching of meesages for when a connection can not be established, then you are adviced to check for gaps in your Clarify data for the relevant period.
Inputs written via our HTTP API does not appear to be affected.
The issue with query performance should now be resolved.
Posted Jan 23, 2026 - 08:41 CET
Monitoring
A fix has been implemented and we are monitoring the results.
Posted Jan 22, 2026 - 21:50 CET
Identified
There is an issue with our cloud that is causing slower than usual performance for ~16% of our time-series which must now be fetched from cold storage. We are investiagting how to resolve the issue.
Posted Jan 22, 2026 - 12:12 CET
This incident affected: Access to data (Query time-series).