- Detected by Pingoru
- May 02, 2026, 06:04 AM UTC
- Resolved
- May 02, 2026, 06:04 AM UTC
- Duration
- —
Affected: Cognite Data Fusion APICognite Data Fusion UI
Timeline · 5 updates
-
investigating Apr 30, 2026, 10:38 AM UTC
Status: Investigating We are investigating an issue that may cause file upload statuses to appear delayed or incorrect. Our engineering team is actively working to identify the root cause and assess the overall impact. Affected components Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance)
-
identified Apr 30, 2026, 01:42 PM UTC
Status: Identified The engineering team has identified the issue and is raising the relevant limits to reduce impact while closely monitoring progress. Affected components Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance)
-
identified Apr 30, 2026, 06:35 PM UTC
Status: Identified Cognite has deployed a configuration change to double the DMS local concurrency limit per pod, aiming to reduce throttling and help clear the file syncing backlog in the az-eastus-1 cluster. The deployment is complete and we are monitoring relevant dashboards to assess its impact on file upload propagation and timeout rates. Affected components Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance)
-
monitoring May 01, 2026, 09:37 AM UTC
Status: Monitoring The limit increases are effective, and we are observing stable conditions for the API. We will monitor the progress and will proceed further depending on the observations. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
-
resolved May 02, 2026, 06:04 AM UTC
Status: Resolved The conditions are now stable for the API after observing the fixes applied, Therefore this incident is now resolved. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2026, 11:28 AM UTC
- Resolved
- Apr 30, 2026, 11:28 AM UTC
- Duration
- —
Affected: Cognite Data Fusion API
Timeline · 4 updates
-
investigating Apr 29, 2026, 06:43 PM UTC
Status: Investigating Cognite is investigating a large slowdown on Raw storage in AZ-EASTUS-1. Slowdowns have been experienced by multiple customers. More information will follow as our investigation continues. ***UPDATE*** Cognite has deployed a new Raw DB to AZ-EASTUS-1. We are observing the load to the new database to see how much the new db will alleviate the slowness. This could take a bit of healing time. Cognite is also requesting updates from Microsoft on the Sev A case currently opened. Affected components Cognite Data Fusion API (Degraded performance)
-
investigating Apr 29, 2026, 06:45 PM UTC
Status: Investigating ***UPDATE*** Cognite has deployed a new Raw DB to AZ-EASTUS-1. We are observing the load to the new database to see how much the new db will alleviate the slowness. This could take a bit of healing time. Cognite is also requesting updates from Microsoft on the Sev A case currently opened. Affected components Cognite Data Fusion API (Degraded performance)
-
identified Apr 30, 2026, 03:31 AM UTC
Status: Identified The immediate performance issue for new tables has been mitigated. Teams have confirmed a significant speed improvement when data is reingested into new tables, with successful runs of key workflows. However, existing tables remain on the original, slower cluster. Their performance is still degraded and is dependent on performance enhancements of a 3rd party service. Affected components Cognite Data Fusion API (Degraded performance)
-
resolved Apr 30, 2026, 11:28 AM UTC
Status: Resolved The issue is resolved now and the service is back to normal. Affected components Cognite Data Fusion API (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2026, 11:01 AM UTC
- Resolved
- Apr 30, 2026, 11:01 AM UTC
- Duration
- —
Affected: Cognite Data Fusion APICognite Data Fusion UI
Timeline · 4 updates
-
investigating Apr 29, 2026, 01:19 PM UTC
Status: Investigating We have identified a potential issue when trying to open canvas you are prompted with insufficient access rights across projects in the cluster. Affected components Cognite Data Fusion UI (Partial outage) Cognite Data Fusion API (Partial outage)
-
identified Apr 29, 2026, 02:59 PM UTC
Status: Identified The team has identified the issue and a fix is currently on the way. Affected components Cognite Data Fusion UI (Partial outage) Cognite Data Fusion API (Partial outage)
-
monitoring Apr 29, 2026, 03:20 PM UTC
Status: Monitoring A fix has been rolled out now and we are currently monitoring the state of this incident. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
-
resolved Apr 30, 2026, 11:01 AM UTC
Status: Resolved The issue has been resolved, and the service is now operating normally. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 27, 2026, 11:50 PM UTC
- Resolved
- Apr 27, 2026, 11:50 PM UTC
- Duration
- —
Affected: Cognite Data Fusion APICognite Data Fusion UICognite MaintainCognite InField
Timeline · 3 updates
-
investigating Apr 27, 2026, 11:07 PM UTC
Status: Investigating Azure OpenAI models are currently experiencing degraded availability in certain regions. Our team is actively monitoring the situation and working to restore full service. Affected production clusters: • aw-was-gp-001 • az-eastus-1 • az-gru-001 • az-pnq-gp-001 • az-tyo-002 • az-tyo-gp-001 Affected components Cognite InField (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite InField (Degraded performance) Cognite Maintain (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite InField (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite InField (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Maintain (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Maintain (Degraded performance) Cognite Maintain (Degraded performance) Cognite Maintain (Degraded performance) Cognite Maintain (Degraded performance) Cognite Infield (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite InField (Degraded performance)
-
monitoring Apr 27, 2026, 11:30 PM UTC
Status: Monitoring Azure OpenAI model availability has stabilized. We are no longer observing 500 errors from Azure, though our team continues to monitor closely. Affected components Cognite Data Fusion UI (Degraded performance) Cognite InField (Degraded performance) Cognite InField (Degraded performance) Cognite InField (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Maintain (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 Maintain (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Maintain (Degraded performance) Cognite Maintain (Degraded performance) Cognite Maintain (Degraded performance) Cognite Infield (Degraded performance) Cognite Maintain (Degraded performance) Cognite InField (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite InField (Degraded performance) Cognite Data Fusion UI (Degraded performance)
-
resolved Apr 27, 2026, 11:50 PM UTC
Status: Resolved Azure OpenAI GPT model endpoints in the affected US regions have fully recovered. Multiple rounds of health checks confirmed all endpoints are responding successfully with no errors. Affected components Cognite Data Fusion API (Operational) Cognite Data Fusion API (Operational) Cognite Maintain (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational) Cognite Maintain (Operational) Cognite Maintain (Operational) Cognite Maintain (Operational) Cognite Data Fusion API (Operational) Cognite Maintain (Operational) Cognite Data Fusion UI (Operational) Cognite InField (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational) Cognite InField (Operational) Cognite InField (Operational) Cognite Data Fusion API (Operational) Cognite Data Fusion UI (Operational) Cognite InField (Operational) Cognite InField (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion UI (Operational) Cognite Maintain (Operational) Cognite Infield (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 25, 2026, 09:25 AM UTC
- Resolved
- Apr 25, 2026, 09:25 AM UTC
- Duration
- —
Affected: Cognite Data Fusion API
Timeline · 7 updates
-
investigating Apr 24, 2026, 02:17 PM UTC
Status: Investigating Cognite is investigating k8s pod restarts in az-eastus-1. This is possibly affecting time series, searching, and contextualization capabilities. Updates will be provided when more information is gathered. Affected components Cognite Data Fusion API (Degraded performance)
-
investigating Apr 24, 2026, 03:15 PM UTC
Status: Investigating We are seeing widespread DNS resolution failures in the az-eastus-1 cluster, affecting multiple pods and disrupting the timeseries service. Affected components Cognite Data Fusion API (Degraded performance)
-
identified Apr 24, 2026, 03:40 PM UTC
Status: Identified We have confirmed that all customers on az-eastus-1 are affected due to ongoing Azure platform issues in the East US region, now officially acknowledged by Microsoft. These issues impact provisioning, scaling, and connectivity for workloads, resulting in widespread DNS resolution failures and a large number of pods across multiple namespaces in CrashLoopBackOff. Customer impact includes service disruptions for timeseries and data modeling services, intermittent errors accessing InField, and degraded availability for multiple workloads and endpoints. Example error patterns include Postgres connection timeouts and DNS lookup failures. Affected components Cognite Data Fusion API (Degraded performance)
-
monitoring Apr 24, 2026, 04:20 PM UTC
Status: Monitoring Cognite has observed all services have recovered or are in a good state of recovery. Customers may possibly still see some slowness in apps recovering from the dns outage. Affected components Cognite Data Fusion API (Degraded performance)
-
monitoring Apr 24, 2026, 11:26 PM UTC
Status: Monitoring While our previous update indicated a good state of recovery, we have started to observe service interruptions again across the environment. Customers may continue to experience slowness or intermittent failures in applications as we navigate the final stages of stabilization following the DNS outage. Our engineering team is closely monitoring these new developments and working to ensure a consistent recovery. We will provide further updates as the situation stabilizes. Affected components Cognite Data Fusion API (Degraded performance)
-
monitoring Apr 25, 2026, 12:43 AM UTC
Status: Monitoring CDF has recovered again after recurrence of the DNS issue. Microsoft has confirmed they have now completed the rollback of the suspected root cause and we will continue monitoring the issue for a few more hours to verify CDF has fully recovered. Affected components Cognite Data Fusion API (Degraded performance)
-
resolved Apr 25, 2026, 09:25 AM UTC
Status: Resolved Microsoft has confirmed the underlying issue has been mitigated and CDF has been running without issues for several hours. Affected components Cognite Data Fusion API (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 08:10 AM UTC
- Resolved
- Apr 24, 2026, 08:10 AM UTC
- Duration
- —
Affected: Cognite Data Fusion API
Timeline · 8 updates
-
investigating Apr 17, 2026, 04:29 PM UTC
Status: Investigating Customers are seeing 35-40% of function deployments failing. Possible correlation to an issue with the files api returning large amounts of 429 codes. Affected components Cognite Data Fusion API (Partial outage)
-
investigating Apr 17, 2026, 04:31 PM UTC
Status: Investigating Currently doing triage on the API issue with incident commander. Affected components Cognite Data Fusion API (Partial outage)
-
identified Apr 17, 2026, 07:15 PM UTC
Status: Identified Cognite has discovered a certificate that has expired that is impacting az-eastus-1 customers. More info to come as we work to renew the cert. Affected components Cognite Data Fusion API (Partial outage)
-
monitoring Apr 17, 2026, 08:45 PM UTC
Status: Monitoring Our engineering team oncall was unable to renew the certificate at the time as he was not at home or in the office. We are hopeful that the cert will be renewed as soon as possible. Affected components Cognite Data Fusion API (Degraded performance)
-
investigating Apr 17, 2026, 09:16 PM UTC
Status: Investigating We've noticed there are frequent function deployments failing in az-eastus-1 and we are investigating the issue. Due to the technically of the situation we are awaiting more information from relevant parties, and have paused the incident as we don't see any clear backend issues. Affected components Cognite Data Fusion API (Degraded performance)
-
identified Apr 20, 2026, 08:04 PM UTC
Status: Identified Cognite continues to work on this issue affecting function deployments. Currently, there is a hypothesis around deploying functions to entra virtual networks. We will provide updates as soon as progress is made. Affected components Cognite Data Fusion API (Degraded performance)
-
monitoring Apr 21, 2026, 04:41 PM UTC
Status: Monitoring Cognite will be placing this incident in monitoring status. Investigation has shifted to an issue with Microsofts AZ-EASTUS-1. It appears a vnet was deployed by Microsoft last week and was not available to it's customers. Affected components Cognite Data Fusion API (Operational)
-
resolved Apr 24, 2026, 08:10 AM UTC
Status: Resolved After carefully monitoring the implemented fixes, our engineering team has confirmed that the incident has been resolved. Affected components Cognite Data Fusion API (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 05:53 PM UTC
- Resolved
- Apr 23, 2026, 05:53 PM UTC
- Duration
- —
Affected: Cognite Data Fusion APICognite Data Fusion UICognite MaintainCognite InField
Timeline · 7 updates
-
investigating Apr 01, 2026, 07:44 AM UTC
Status: Investigating "We are currently investigating an issue affecting the Data Modeling service. Some users may experience degraded performance and increased error rates, including 408 Request Timeout errors. Our engineering team is actively working to resolve the issue. We will provide further updates as the situation develops. " Affected components Cognite Maintain (Degraded performance) Cognite InField (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance)
-
investigating Apr 01, 2026, 07:54 AM UTC
Status: Investigating Please be informed that DMS services will be temporarily unavailable during the scheduled maintenance window. Maintenance Window: 16:00 – 18:00 CEST / 23:00 – 01:00 JST Cluster: az-tyo-gp-001 Affected components Cognite InField (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Maintain (Degraded performance)
-
monitoring Apr 01, 2026, 02:48 PM UTC
Status: Monitoring The scheduled maintenance has been successfully completed, and DMS service has returned to normal operation. The engineering team is continuing to monitor the service to ensure stability. Affected components Cognite Maintain (Operational) Cognite InField (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
-
investigating Apr 02, 2026, 08:26 AM UTC
Status: Investigating We have observed that DMS services remain unstable. Consequently, the engineering team has decided to conduct additional emergency maintenance. Please be informed that DMS services will be temporarily unavailable during the maintenance window. Emergency Maintenance Window: 17:00 – 18:00 CEST / 00:00 – 01:00 JST Cluster: az-tyo-gp-001 Affected components Cognite Data Fusion API (Degraded performance) Cognite Maintain (Degraded performance) Cognite InField (Degraded performance) Cognite Data Fusion UI (Degraded performance)
-
identified Apr 02, 2026, 04:01 PM UTC
Status: Identified Our teams have completed the emergency maintenance successfully, the engineering team is continuing to monitor the service to ensure stability. Affected components Cognite Maintain (Degraded performance) Cognite InField (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance)
-
monitoring Apr 02, 2026, 08:25 PM UTC
Status: Monitoring Service success rates have recovered to 100%, and the affected dashboards are now reporting normal operation. The team is continuing to monitor the situation closely Affected components Cognite Maintain (Operational) Cognite InField (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
-
resolved Apr 23, 2026, 05:53 PM UTC
Status: Resolved Since the success rates have returned to 100%, and all affected dashboards are reporting normal operation. The issue has been fully resolved. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational) Cognite Maintain (Operational) Cognite InField (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 01:23 PM UTC
- Resolved
- Apr 23, 2026, 01:23 PM UTC
- Duration
- —
Affected: Cognite Data Fusion APICognite Data Fusion UI
Timeline · 4 updates
-
investigating Apr 23, 2026, 08:30 AM UTC
Status: Investigating The Streams and records API is experiencing issues. Our teams are investigating the issue at this time. Affected components Cognite Data Fusion API (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance)
-
identified Apr 23, 2026, 08:34 AM UTC
Status: Identified The cause of the issue has been identified and the fixes are in development. Affected components Cognite Data Fusion API (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance)
-
monitoring Apr 23, 2026, 08:36 AM UTC
Status: Monitoring The fixes have been deployed, and the services are back to normal. The incident is now in monitoring state. Affected components Cognite Data Fusion API (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
-
resolved Apr 23, 2026, 01:23 PM UTC
Status: Resolved The issue is now resolved. No issues during the monitoring period. Affected components Cognite Data Fusion API (Operational) Cognite Data Fusion API (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion UI (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 01:27 PM UTC
- Resolved
- Apr 22, 2026, 01:27 PM UTC
- Duration
- —
Affected: Cogite Data Fusion APICognite Data Fusion UI
Timeline · 3 updates
-
investigating Apr 17, 2026, 01:45 AM UTC
Status: Investigating We are currently experiencing intermittent degradation in integration services, related to ongoing database maintenance in Microsoft Azure. Our engineers are actively investigating the issue with Azure to identify the root cause and will provide updates as more information becomes available. Affected components Cognite Data Fusion UI (Degraded performance) Cogite Data Fusion API (Degraded performance)
-
monitoring Apr 17, 2026, 11:28 AM UTC
Status: Monitoring The database maintenance has completed , services and database connectivity is restored. We are still monitoring the issue and waiting for an RCA from the Azure team. Affected components Cogite Data Fusion API (Degraded performance) Cognite Data Fusion UI (Degraded performance)
-
resolved Apr 22, 2026, 01:27 PM UTC
Status: Resolved Our engineering team has completed monitoring this issue. The database maintenance has completed, services and database connectivity is restored. Therefore, we are resolving this incident. Affected components Cognite Data Fusion UI (Operational) Cogite Data Fusion API (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 11:13 AM UTC
- Resolved
- Apr 20, 2026, 11:13 AM UTC
- Duration
- —
Affected: Cognite Data Fusion UI
Timeline · 2 updates
-
monitoring Apr 20, 2026, 08:24 AM UTC
Status: Monitoring There has been an issue due to which Custom Apps menu item were not visible in the Fusion Menu. Engineering team has deployed a fix and working on a rca. 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 Apr 20, 2026, 11:13 AM UTC
Status: Resolved The issue has been resolved and the Custom Apps menu is visible and functional. 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
- Apr 20, 2026, 08:24 AM UTC
- Resolved
- Apr 20, 2026, 11:13 AM UTC
- Duration
- 2h 48m
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2026, 04:29 PM UTC
- Resolved
- Apr 24, 2026, 08:10 AM UTC
- Duration
- 6d 15h
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 12:34 AM UTC
- Resolved
- Apr 15, 2026, 12:34 AM UTC
- Duration
- —
Affected: Cognite Data Fusion APICognite Data Fusion UI
Timeline · 3 updates
-
investigating Mar 31, 2026, 07:33 AM UTC
Status: Investigating The engineering team is currently investigating alerts related to Data Model Storage availability and Time Series API error rates. Affected components Cognite Data Fusion API (Degraded performance) Cognite Data Fusion UI (Degraded performance)
-
monitoring Mar 31, 2026, 08:24 AM UTC
Status: Monitoring The engineering team verifies that both the Data Model Storage availability and Time Series API error rate alerts have been resolved and is currently monitoring the fix. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
-
resolved Apr 15, 2026, 12:34 AM UTC
Status: Resolved We are pleased to report that the recent performance issues have been resolved. Our engineering team has verified that both Data Model Storage availability and Time Series API error rates have returned to normal operating parameters. We have implemented a fix and are currently monitoring the system closely to ensure long-term stability. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 20, 2026, 05:22 PM UTC
- Resolved
- Mar 20, 2026, 05:22 PM UTC
- Duration
- —
Affected: Cognite Data Fusion API
Timeline · 3 updates
-
investigating Mar 20, 2026, 03:31 PM UTC
Status: Investigating We are seeing a downtime in Timeseries and Sequence component of the Cognite API. Affected components Cognite Data Fusion API (Partial outage)
-
monitoring Mar 20, 2026, 03:57 PM UTC
Status: Monitoring Service has been restored to the timeseries and sequence API. Investigation continues into the cause of the service interruption. Affected components Cognite Data Fusion API (Operational)
-
resolved Mar 20, 2026, 05:22 PM UTC
Status: Resolved The incident is now resolved as the issue is contained after a period of monitoring. Affected components Cognite Data Fusion API (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2026, 02:03 PM UTC
- Resolved
- Mar 18, 2026, 02:03 PM UTC
- Duration
- —
Affected: Cognite 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 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 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 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 UI
Timeline · 2 updates
-
investigating Feb 27, 2026, 09:35 AM UTC
Status: Investigating Workflow deletion requests may experience extended response times or timeouts. We are currently working on a fix. Affected components 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 UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cogite Data Fusion API (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion API (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) Cognite Data Fusion API (Degraded performance) Cognite Data Fusion API (Degraded performance)
-
resolved Feb 27, 2026, 09:57 AM UTC
Status: Resolved The issue has now been resolved by the Engineering team. Affected components Cognite Data Fusion API (Operational) Cognite Data Fusion API (Operational) Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational) Cognite 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 UI (Operational) Cogite Data Fusion API (Operational) Cognite Data Fusion UI (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) 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 UI (Operational) Cognite Data Fusion API (Operational) Cognite Data Fusion UI (Operational)
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 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 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 →