Cognite incident

Function deployment failures at 35-40% in az-eastus-1

Resolved after 6 days 15 hours, affecting Cognite Data Fusion API and Cognite Data Fusion API and 1 more, on April 17, 2026.

resolved Apr 24, 2026, 08:10 AM UTC

After carefully monitoring the implemented fixes, our engineering team has confirmed that the incident has been resolved.

Started
Apr 17, 2026, 04:29 PM UTC
Resolved
Apr 24, 2026, 08:10 AM UTC
Duration
6d 15h
Detected by Pingoru
Apr 17, 2026, 04:29 PM UTC

Affected components

Cognite Data Fusion APICognite Data Fusion APICognite Data Fusion API

Update timeline

  1. investigating Apr 17, 2026, 04:29 PM UTC

    Customers are seeing 35-40% of function deployments failing. Possible correlation to an issue with the files api returning large amounts of 429 codes.

  2. investigating Apr 17, 2026, 04:31 PM UTC

    Currently doing triage on the API issue with incident commander.

  3. identified Apr 17, 2026, 07:15 PM UTC

    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.

  4. monitoring Apr 17, 2026, 08:45 PM UTC

    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.

  5. investigating Apr 17, 2026, 09:16 PM UTC

    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.

  6. identified Apr 20, 2026, 08:04 PM UTC

    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.

  7. monitoring Apr 21, 2026, 04:41 PM UTC

    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.

  8. resolved Apr 24, 2026, 08:10 AM UTC

    After carefully monitoring the implemented fixes, our engineering team has confirmed that the incident has been resolved.

Your product runs on more than Cognite

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →