All Systems Operational

Uptime over the past 90 days. View historical uptime.
Access to Clarify Operational
90 days ago
100.0 % uptime
Today
Clarify UI Operational
90 days ago
100.0 % uptime
Today
Auth0 User Authentication Operational
Clarify API Operational
90 days ago
100.0 % uptime
Today
Access to data Operational
90 days ago
100.0 % uptime
Today
Query time-series Operational
90 days ago
100.0 % uptime
Today
Ingest time-series to persistent storage Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Feb 4, 2026

No incidents reported today.

Feb 3, 2026

No incidents reported.

Feb 2, 2026

No incidents reported.

Feb 1, 2026

No incidents reported.

Jan 31, 2026

No incidents reported.

Jan 30, 2026

No incidents reported.

Jan 29, 2026

No incidents reported.

Jan 28, 2026

No incidents reported.

Jan 27, 2026

No incidents reported.

Jan 26, 2026

No incidents reported.

Jan 25, 2026

No incidents reported.

Jan 24, 2026

No incidents reported.

Jan 23, 2026
Timeseries performance
Resolved - 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.
Jan 23, 08:41 CET
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 22, 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.
Jan 22, 12:12 CET
Jan 22, 2026
Jan 21, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage