Cognite incident

Data Modeling schema inconsistency in az-tyo-gp-001

Minor Resolved View vendor source →

Cognite experienced a minor incident on January 27, 2026 affecting Cognite Data Fusion API, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jan 27, 2026, 09:28 AM UTC
Resolved
Jan 27, 2026, 09:28 AM UTC
Duration
Detected by Pingoru
Jan 27, 2026, 09:28 AM UTC

Affected components

Cognite Data Fusion API

Update timeline

  1. investigating Jan 23, 2026, 09:21 AM UTC

    Status: Investigating We are investigating an issue causing data model deployment failures in the az-tyo-gp-001 cluster. The impact is currently isolated to this cluster only. Our engineering team is actively working on identifying and resolving the underlying schema inconsistency. Further updates will be shared as we learn more. Affected components Cognite Data Fusion API (Degraded performance)

  2. identified Jan 23, 2026, 11:20 AM UTC

    Status: Identified The schema inconsistency issue in the multi-tenant-1 cluster, caused by system property propagation failures during cluster setup, has been identified and is currently under investigation. Affected components Cognite Data Fusion API (Degraded performance)

  3. monitoring Jan 26, 2026, 01:54 PM UTC

    Status: Monitoring Our teams have successfully deployed a fix for the issue. The features are working as expected. We will monitor the situation for a period of time before closing the incident Affected components Cognite Data Fusion API (Operational)

  4. resolved Jan 27, 2026, 09:28 AM UTC

    Status: Resolved After monitoring the fix, the engineers have now confirmed the incident is resolved. Affected components Cognite Data Fusion API (Operational)