Update - The Incident team has released a workaround for this Incident.
During investigation of an incident that occurred at this time, we found that around 0.1% of time series datapoints write operations failed to be written to the backing store during this period between 11:28 GMT and 12:00 GMT, Thursday November 25, 2021. However the API was still returned HTTP 200 success code. This means that a small portion of data may be missing when attempting to read time series data points from this period. You may want to check critical time series for gaps in this period and / or re-ingest data points from this time interval.

The Incident team is closely monitoring the health of 2 services, while working on a permanent fix. If you would like more in depth information, then don’t hesitate to reach out to support@cognite.com.
Nov 26, 18:50 CET

Monitoring - The Incident team has mitigated the issue with a workaround.
This workaround ensures that all Cognite services are fully operational again.

The Incident team is closely monitoring the health of our services, while working on a permanent fix. If you would like more in depth information, then don’t hesitate to reach out to support@cognite.com.
Nov 26, 16:55 CET

Update - Mitigations actions are in place . Cognite service engineering team is ensuring that affected services are fully operational as soon as possible .
We further investigating to permanent resolution
Nov 26, 16:15 CET

Identified - The Incident team has identified the root cause of the Incident. The main focus of our Incident team is now to use these findings in ensuring that our services are fully operational as soon as possible.
Nov 26, 14:48 CET

Investigating - We are currently experiencing an incident that is affecting the Cognite API endpoint. Users may experience 404 errors messages when using Cognite timeseries and sequences APIs.

The Cognite engineering team is currently investigating the cause of this Incident.
Nov 26, 14:35 CET