Cognite experienced a minor incident on April 30, 2026 affecting Cognite Data Fusion API and Cognite Data Fusion API, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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)