- Detected by Pingoru
- Mar 18, 2026, 02:03 PM UTC
- Resolved
- Mar 18, 2026, 02:03 PM UTC
- Duration
- —
Affected: Cognite Data Fusion UICognite Data Fusion APICognite Data Fusion APICognite Data Fusion UI
Timeline · 3 updates
-
investigating Mar 17, 2026, 05:17 PM UTC
Status: Investigating We are currently investigating a synchronization issue in the westeurope-1 region where CogniteTimeSeries updates and deletions are failing to propagate from PG3 to the time series backend. This disruption has led to sync delays exceeding around 1 hour for affected projects and may result in stale data appearing in DMS search results. Affected components Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance)
-
monitoring Mar 17, 2026, 06:27 PM UTC
Status: Monitoring We have implemented a mitigation strategy to resolve the synchronization bottleneck in the westeurope-1 region and are now observing the recovery of the CogniteTimeSeries pipeline. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
-
resolved Mar 18, 2026, 02:03 PM UTC
Status: Resolved The engineering team confirmed that the issue is resolved. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 16, 2026, 05:59 PM UTC
- Resolved
- Mar 16, 2026, 05:59 PM UTC
- Duration
- —
Affected: Cognite Data Fusion UICognite Data Fusion APICognite Data Fusion APICognite Data Fusion UI
Timeline · 5 updates
-
investigating Mar 03, 2026, 01:07 PM UTC
Status: Investigating We are currently observing a degraded performance issue with file uploads to Semantic Search. However, this is limited to new file uploads, file deletes and viewing recently uploaded files. Affected components Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance)
-
identified Mar 03, 2026, 03:06 PM UTC
Status: Identified The underlying issue has been identified and a fix is now being worked on. The backlog of the impacted files is now being processed and the situation is gradually improving. We will update once the components are fully operational. Affected components Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance)
-
monitoring Mar 05, 2026, 12:54 PM UTC
Status: Monitoring Disk usage across the Elasticsearch cluster has decreased and cluster health is now green. A backfill is running to ensure all projects are up to date, and the system is being monitored to confirm stability. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
-
monitoring Mar 09, 2026, 11:01 AM UTC
Status: Monitoring With some improvements made, we are continuing to monitor the incident. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
-
resolved Mar 16, 2026, 05:59 PM UTC
Status: Resolved Following the implementation of several key improvements, we have successfully stabilized the westeurope-1 environment and returned the Elasticsearch cluster to a healthy Green status. While disk usage has been significantly reduced to optimal levels, a backfill process is currently running to ensure all project data is fully synchronized and up to date. We have completed an extended monitoring period to confirm system stability, and all services are now fully operational. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 14, 2026, 06:39 AM UTC
- Resolved
- Mar 14, 2026, 06:39 AM UTC
- Duration
- —
Affected: Cognite InField
Timeline · 3 updates
-
investigating Mar 11, 2026, 11:17 AM UTC
Status: Investigating There is a service outage in Infield, leading to some customers not being able to access Infield. This is caused due to an issue in a planned maintenance - https://status.cognite.com/incidents/01KJ6ZTBW8WGHED40N7935TVBW#updates Affected components Cognite InField (Partial outage)
-
monitoring Mar 11, 2026, 01:35 PM UTC
Status: Monitoring The database maintenance is completed. We are seeing a recovery in services . We will be following up with the cloud vendor on a reason-for-outage report and also why the agreed-on maintenance window was disregarded. Affected components Cognite InField (Degraded performance)
-
resolved Mar 14, 2026, 06:39 AM UTC
Status: Resolved After monitoring the incident, the engineering team has confirmed the incident is now resolved. Affected components Cognite InField (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 09:40 PM UTC
- Resolved
- Mar 12, 2026, 09:40 PM UTC
- Duration
- —
Affected: Cognite Maintain
Timeline · 2 updates
-
investigating Mar 12, 2026, 05:56 PM UTC
Status: Investigating We are currently investigating an issue where users are unable to Create/Edit Activities using the Direct Planning modal on the Maintain application. Affected components Cognite Maintain (Degraded performance)
-
resolved Mar 12, 2026, 09:40 PM UTC
Status: Resolved The issue has now been resolved. The impacted features in Maintain are now operational. Affected components Cognite Maintain (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 11, 2026, 02:54 PM UTC
- Resolved
- Mar 11, 2026, 02:54 PM UTC
- Duration
- —
Affected: Cognite Data Fusion UICognite Data Fusion UICognite InField
Timeline · 4 updates
-
monitoring Mar 11, 2026, 12:01 PM UTC
Status: Monitoring Data modelling services where experiencing high error rate and downtime. This was caused by a scheduled maintenance that was delayed - https://status.cognite.com/incidents/01KJ6ZTBW8WGHED40N7935TVBW The service has been partially restored but there is a risk of further downtime as there is another maintenance scheduled. Affected components Cognite InField (Partial outage)
-
monitoring Mar 11, 2026, 01:17 PM UTC
Status: Monitoring The ongoing issue is impacting Cognite Data Fusion UI. User might see slowness or failure to load UI components Affected components Cognite InField (Partial outage) Cognite Data Fusion UI (Partial outage)
-
monitoring Mar 11, 2026, 01:26 PM UTC
Status: Monitoring The database maintenance is completed. We are seeing a recovery in services . We will be following up with the cloud vendor on a reason-for-outage report and also why the agreed-on maintenance window was disregarded. Affected components Cognite Data Fusion UI (Degraded performance) Cognite InField (Degraded performance)
-
resolved Mar 11, 2026, 02:54 PM UTC
Status: Resolved The issue has been resolved and all the affected service are functional Affected components Cognite Data Fusion UI (Operational) Cognite InField (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 12:50 PM UTC
- Resolved
- Feb 27, 2026, 12:50 PM UTC
- Duration
- —
Affected: Cognite Data Fusion APICognite Data Fusion APICognite Data Fusion UI
Timeline · 3 updates
-
investigating Feb 26, 2026, 05:23 PM UTC
Status: Investigating Currently, we are investigating an issue where functions are failing to upload. However, this is limited to new functions awaiting upload and replacing existing functions. Affected components Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance)
-
monitoring Feb 26, 2026, 06:17 PM UTC
Status: Monitoring The failures are no longer observed and the issue now seems contained. We are currently monitoring the situation until resolution. Affected components Cognite Data Fusion API (Operational) Cognite Data Fusion UI (Operational)
-
resolved Feb 27, 2026, 12:50 PM UTC
Status: Resolved The issue has now been resolved by the Engineering team. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 09:57 AM UTC
- Resolved
- Feb 27, 2026, 09:57 AM UTC
- Duration
- —
Affected: Cogite Data Fusion APICognite Data Fusion APICognite Data Fusion APICognite Data Fusion UI
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 11:27 AM UTC
- Resolved
- Feb 25, 2026, 11:27 AM UTC
- Duration
- —
Affected: Cognite Data Fusion APICognite Data Fusion APICognite Data Fusion UI
Timeline · 3 updates
-
investigating Feb 18, 2026, 12:40 PM UTC
Status: Investigating Some context-api pods are unable to process function scheduler requests due to timeouts when calling Kubernetes TokenReview endpoints. The engineering team is investigating and working to restore normal schedule execution. Affected components Cognite Data Fusion UI (Partial outage) Cognite Data Fusion API (Partial outage)
-
monitoring Feb 18, 2026, 03:56 PM UTC
Status: Monitoring The immediate impact identified as delayed or missed scheduled function runs for a subset of customers in this cluster. Recent metrics indicate that scheduler runtimes have returned to normal levels. To prevent recurrence, we are evaluating improvements to the service. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
-
resolved Feb 25, 2026, 11:27 AM UTC
Status: Resolved The issue is resolved. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 09:06 AM UTC
- Resolved
- Feb 20, 2026, 09:06 AM UTC
- Duration
- —
Affected: Cognite Data Fusion UI
Timeline · 3 updates
-
investigating Feb 20, 2026, 04:25 AM UTC
Status: Investigating We are currently investigating an issue where an error is displayed on the CDF UI for newly initiated login sessions. However, this is limited to new user logins and can be mitigated after a manual refresh as a temporary workaround. Affected components Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance)
-
identified Feb 20, 2026, 07:52 AM UTC
Status: Identified The team has identified the cause and a fix is currently underway. Affected components Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance)
-
resolved Feb 20, 2026, 09:06 AM UTC
Status: Resolved The team has successfully mitigated the issue with the fix and this incident is considered as resolved. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion UI (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 16, 2026, 10:03 AM UTC
- Resolved
- Feb 16, 2026, 10:03 AM UTC
- Duration
- —
Affected: Cogite Data Fusion APICognite Data Fusion APICognite Data Fusion API
Timeline · 2 updates
-
investigating Feb 16, 2026, 09:07 AM UTC
Status: Investigating We are currently investigating an ongoing issue with the IAM API. Further updates will be available as we continue to investigate. Affected components Cognite Data Fusion API (Degraded performance) Cogite Data Fusion API (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion API (Degraded performance)
-
resolved Feb 16, 2026, 10:03 AM UTC
Status: Resolved The issue has now been fully contained. All impacted services related to the IAM API are now back in full operation. Affected components Cognite Data Fusion API (Operational) Cognite Data Fusion API (Operational) Cognite Data Fusion API (Operational) Cognite Data Fusion API (Operational) Cogite Data Fusion API (Operational) Cognite Data Fusion API (Operational) Cognite Data Fusion API (Operational) Cognite Data Fusion API (Operational) Cognite Data Fusion API (Operational) Cognite Data Fusion API (Operational) Cognite Data Fusion API (Operational) Cognite Data Fusion API (Operational) Cognite Data Fusion API (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 06, 2026, 08:39 AM UTC
- Resolved
- Feb 06, 2026, 08:39 AM UTC
- Duration
- —
Affected: Cognite Data Fusion APICognite Data Fusion UI
Timeline · 4 updates
-
investigating Feb 03, 2026, 01:22 PM UTC
Status: Investigating Atlas users are encountering frequent errors and reduced performance when working with agents. Affected components Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance)
-
investigating Feb 03, 2026, 08:50 PM UTC
Status: Investigating If performance and load issues are observed, we recommend utilizing the following models to ensure optimal performance: • gpt-5 • gpt-5-nano • gpt-4.1 • gpt-4.1-mini • gpt-4.1-nano Affected components Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance)
-
identified Feb 04, 2026, 01:54 PM UTC
Status: Identified We have identified the underlying issue and we are currently working on a fix. A potential fix will be available once it is thoroughly tested. Affected components Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance)
-
resolved Feb 06, 2026, 08:39 AM UTC
Status: Resolved The issue is now fully contained and all impacted services are back in operation. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
Read the full incident report →
- Detected by Pingoru
- Jan 27, 2026, 09:08 PM UTC
- Resolved
- Jan 27, 2026, 09:08 PM UTC
- Duration
- —
Affected: Cogite Data Fusion APICognite Data Fusion APICognite Data Fusion UI
Timeline · 2 updates
-
investigating Jan 27, 2026, 02:34 PM UTC
Status: Investigating Engineers have identified a failure in the Agent Chat completion endpoint. They are currently investigating the issue. Affected components Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion API (Degraded performance) Cogite Data Fusion API (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion UI (Degraded performance)
-
resolved Jan 27, 2026, 09:08 PM UTC
Status: Resolved This incident is resolved based on the Azure service update. Service availability has improved, and successful requests are being observed across affected clusters. Affected components Cognite Data Fusion API (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational) Cognite Data Fusion UI (Operational) Cogite Data Fusion API (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational) Cognite Data Fusion API (Operational) Cognite Data Fusion API (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational) Cognite Data Fusion UI (Operational)
Read the full incident report →
- Detected by Pingoru
- Jan 27, 2026, 02:34 PM UTC
- Resolved
- Jan 27, 2026, 09:08 PM UTC
- Duration
- 6h 34m
Read the full incident report →
- Detected by Pingoru
- Jan 27, 2026, 09:28 AM UTC
- Resolved
- Jan 27, 2026, 09:28 AM UTC
- Duration
- —
Affected: Cognite Data Fusion API
Timeline · 4 updates
-
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)
-
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)
-
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)
-
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)
Read the full incident report →
- Detected by Pingoru
- Jan 23, 2026, 04:30 PM UTC
- Resolved
- Jan 23, 2026, 09:35 PM UTC
- Duration
- 5h 5m
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2026, 06:05 PM UTC
- Resolved
- Jan 23, 2026, 09:13 AM UTC
- Duration
- 15h 7m
Read the full incident report →
- Detected by Pingoru
- Jan 12, 2026, 02:56 PM UTC
- Resolved
- Jan 13, 2026, 08:59 AM UTC
- Duration
- 18h 2m
Read the full incident report →
- Detected by Pingoru
- Jan 08, 2026, 02:20 AM UTC
- Resolved
- Jan 08, 2026, 03:42 AM UTC
- Duration
- 1h 21m
Read the full incident report →
- Detected by Pingoru
- Jan 08, 2026, 12:15 AM UTC
- Resolved
- Jan 08, 2026, 02:50 PM UTC
- Duration
- 14h 34m
Read the full incident report →
- Detected by Pingoru
- Jan 06, 2026, 08:41 PM UTC
- Resolved
- Jan 07, 2026, 05:00 PM UTC
- Duration
- 20h 18m
Read the full incident report →