What is Cognite's uptime?

Over the last 90 days, Cognite reported 98.59% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.cognite.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Cognite's uptime history rolling forward in real time.

Has Cognite had outages in 2026?

Yes — Cognite has had 39 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.

When was the last Cognite outage?

The most recent Cognite incident was "files_is_uploaded_propagated_lag", which started on June 11, 2026 and was resolved on June 11, 2026. Pingoru captured this directly from https://status.cognite.com. See the full incident card above for affected components and the update timeline.

How often does Cognite have outages?

Based on the last 90 days, Cognite averages 13.0 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.

Where is Cognite's status page?

Cognite's official status page is https://status.cognite.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.

Is Cognite down right now?

Cognite is having a partial outage. Pingoru checks the official status page every 5 minutes and flips this headline the moment Cognite reports a change. Current status is based on 93 tracked services.

How does Pingoru know if Cognite is down?

We read https://status.cognite.com directly, using Cognite's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.

Where can I get notified when Cognite has an outage?

Create a free Pingoru account and add Cognite as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.

Cognite's status page says the service is up, but I'm having issues — what's wrong?

Three common reasons: • A real Cognite incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Cognite issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.

Where does Pingoru get the official Cognite status?

We use Cognite's own status page at https://status.cognite.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.

What does "Partial Outage" mean?

Cognite has a partial outage — one or more components are down, but the rest of the service is operational.

Is Cognite down?

Last checked 6m ago

Current status

Cognite is having a partial outage

Active incident: Data Modeling Search/Aggregates Not Refreshing

Get alerts when Cognite breaks → View Cognite outage history →

Free · no credit card

Official status page: https://status.cognite.com · Polled every 5 minutes · 93 components tracked

Cognite is reporting a partial outage right now (last checked 6m ago). Some components are affected; others remain operational.

Real-time Cognite status, recent outages, and incident history — pulled directly from Cognite's official status page at https://status.cognite.com every 5 minutes. Pingoru tracks 93 Cognite services and has captured 40 incidents in the last 90 days (98.59% uptime). Get email, Slack, Discord, or webhook alerts the moment Cognite reports a new incident — free for 5 monitors, no credit card.

Users who monitor Cognite also follow these Cloud Infrastructure services:

Genesys Cloud View all 6,000+ providers

Cognite uptime 98.59% uptime · past 90 days

Mon Wed Fri

MarAprMayJun

Less More

Active incident 1

Data Modeling Search/Aggregates Not Refreshing

Ongoing ● 2d 8h

Started Jun 11, 2026, 11:55 AM UTC

Cognite Data Fusion UICognite Data Fusion API
Timeline · 5 updates
- investigating · Jun 04, 2026, 06:34 PM UTC
  
  Status: Investigating We are currently investigating an issue where Data Modeling search and aggregate results are not refreshing as expected on the az-eastus-1 cluster. Users may experience incorrect or zero counts in search results, and newly ingested data may not appear in the CDF Search UI. Our engineering team has identified the root cause and a fix is currently in progress. We will provide further updates as the situation develops. Affected components Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance)
- identified · Jun 04, 2026, 07:10 PM UTC
  
  Status: Identified We have identified the cause of an issue affecting Data Modeling search and aggregate results on the az-eastus-1 cluster. This issue is limited to a specific data pattern and does not affect all customers only projects ingesting JSON data where one key is used as a prefix before a dot (.) in another key within the same JSON object are impacted. Workaround: To avoid triggering this issue, please ensure JSON objects do not contain keys where one key shares a prefix with another key before a dot (.) or end of string. For example, a structure where one key appears as a prefix of another dot-separated key should be avoided. Our engineering team is actively working on a permanent fix. We will provide further updates as the situation develops. Affected components Cognite Data Fusion API (Degraded performance) Cognite Data Fusion UI (Degraded performance)
- identified · Jun 05, 2026, 07:29 AM UTC
  
  Status: Identified A bug in the Elasticsearch mapping refresh is causing search and aggregate results to not update for projects using JSON properties where a plain key and a dotted key share a prefix (e.g. "min" and "min.A" in the same JSON object). A first fix was insufficient; a second fix (PR #1908) is now in pipeline and rollout to az-eastus-1 is expected within ~1 week, pending testing. Example of triggering data pattern: { "min": "value", "min.A": "nested_value" } Any JSON property where a plain key (min) and a dotted key (min.A) share the same prefix will trigger the naming collision. Currently fixing is in progress. Affected components Cognite Data Fusion API (Degraded performance) Cognite Data Fusion UI (Degraded performance)
- identified · Jun 05, 2026, 01:02 PM UTC
  
  Status: Identified The fix for the Elasticsearch mapping bug has been deployed to staging and initial results look good. Pending successful staging validation, rollout to production is planned throughout next week. The workaround remains to avoid using JSON keys with shared prefixes and dotted variants. Affected components Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance)
- monitoring · Jun 11, 2026, 11:55 AM UTC
  
  Status: Monitoring The fix has been applied and indexing has resumed. We are currently monitoring the state of the fix at this stage. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
Latest: Status: Monitoring The fix has been applied and indexing has resumed. We are currently monitoring the state of the fix at this stage. Affected components Cognite Data Fusion UI (Op…

Recent outages & incidents

Past 90 days

files_is_uploaded_propagated_lag

Resolved —

Started Jun 11, 2026, 06:59 AM UTC · Resolved Jun 11, 2026, 06:59 AM UTC

Cognite Data Fusion API
Timeline · 2 updates
- identified · Jun 09, 2026, 12:30 PM UTC
  
  Status: Identified We have identified a significant delay in the propagation of the isUploaded flag for files uploaded in the az-eastus-1 cluster. Files may take over 2 hours to be marked as uploaded after a successful upload. Root cause identified: At least one project in the az-eastus-1 cluster is being rate limited by the DMS (Data Modeling Service), which is causing the file storage subscriber to back up and delay processing of upload notifications. Our engineering team has applied a fix to increase the DMS write concurrency limit for the affected project, and the change has been deployed. We are actively monitoring the situation to confirm recovery. We will provide further updates as the situation progresses. Affected components Cognite Data Fusion API (Degraded performance)
- resolved · Jun 11, 2026, 06:59 AM UTC
  
  Status: Resolved File upload propagation delays (isUploaded flag) in the az-eastus-1 cluster have been fully resolved. The root cause was an Azure Event Grid outage in the East US region (05:00 UTC June 9 – 06:30 UTC June 10, 2026), which prevented blob storage notifications from reaching our internal file processing pipeline. Propagation lag has now stabilized at normal, near-zero levels. All affected workflows, including CDF Function deployments and file-dependent processes, should be fully operational. We will continue to monitor system metrics to ensure stability. Affected components Cognite Data Fusion API (Operational)
Latest: Status: Resolved File upload propagation delays (isUploaded flag) in the az-eastus-1 cluster have been fully resolved. The root cause was an Azure Event Grid outage in the East US …
Performance Degradation for Instance Queries

Resolved —

Started Jun 08, 2026, 09:52 AM UTC · Resolved Jun 08, 2026, 09:52 AM UTC

Cognite Data Fusion UICognite Data Fusion APICognite Data Fusion UI
Timeline · 4 updates
- investigating · May 28, 2026, 09:42 AM UTC
  
  Status: Investigating We are currently investigating reports of very slow queries when fetching instances. Our engineering team is actively analyzing the issue and working to identify the root cause. Affected components Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance)
- investigating · May 28, 2026, 10:48 AM UTC
  
  Status: Investigating The issue has been mitigated and service performance has returned to normal. Our team has confirmed the issue is resolved and will continue to monitor the environment to ensure stability. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
- monitoring · May 28, 2026, 03:38 PM UTC
  
  Status: Monitoring The issue has been mitigated and service performance has returned to normal. Our team has confirmed the issue is resolved and will continue to monitor the environment to ensure stability. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
- resolved · Jun 08, 2026, 09:52 AM UTC
  
  Status: Resolved The final rollout of the fix for intermittent Data Modeling performance degradation on az-eastus-1 completed successfully, with no significant latency spikes observed during deployment. Application performance is stable and we have not observed any further issues. This incident is now considered resolved. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
Latest: Status: Resolved The final rollout of the fix for intermittent Data Modeling performance degradation on az-eastus-1 completed successfully, with no significant latency spikes obser…
Data Workflow Unavailable in Cluster az-tyo-gp-001

Resolved —

Started Jun 04, 2026, 02:20 PM UTC · Resolved Jun 04, 2026, 02:20 PM UTC

Cognite Data Fusion UICognite Data Fusion API
Timeline · 2 updates
- investigating · Jun 04, 2026, 01:30 PM UTC
  
  Status: Investigating Data Workflow is unavailable in cluster az-tyo-gp-001, impacting workflow execution and related operations. Investigation and recovery efforts are ongoing. Affected components Cognite Data Fusion UI (Degraded performance) Cognite Data Fusion API (Degraded performance)
- resolved · Jun 04, 2026, 02:20 PM UTC
  
  Status: Resolved Data Workflow availability has been fully restored in cluster az-tyo-gp-001. Validation and monitoring confirm normal operation, and the incident has been resolved and closed. Affected components Cognite Data Fusion UI (Operational) Cognite Data Fusion API (Operational)
Latest: Status: Resolved Data Workflow availability has been fully restored in cluster az-tyo-gp-001. Validation and monitoring confirm normal operation, and the incident has been resolved…
Rendering issue identified in the Agent selector in Atlas AI

Resolved —

Started Jun 03, 2026, 02:52 PM UTC · Resolved Jun 03, 2026, 02:52 PM UTC

Cognite Data Fusion UI
Timeline · 3 updates
- investigating · Jun 03, 2026, 01:08 PM UTC
  
  Status: Investigating We have identified a potential issue surrounding AI Chat agent, where the agent selector dropdown is rendering with heavily overlapped/duplicated text, making it effectively unusable. The issue is a frontend rendering regression, internally detected at 14:35 CEST today. Affected components Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage)
- identified · Jun 03, 2026, 01:13 PM UTC
  
  Status: Identified We have identified a potential issue surrounding AI Chat agent, where the agent selector dropdown is rendering with heavily overlapped/duplicated text, making it effectively unusable. The issue is a frontend rendering regression, internally detected at 14:35 CEST today. Affected components Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage) Cognite Data Fusion UI (Partial outage)
- resolved · Jun 03, 2026, 02:52 PM UTC
  
  Status: Resolved The incident is now resolved as the fix was deployed to mitigate the UI rendering issue in the agent chat. 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)
Latest: Status: Resolved The incident is now resolved as the fix was deployed to mitigate the UI rendering issue in the agent chat. Affected components Cognite Data Fusion UI (Operational)…
Unwanted popup appearing in Cognite hub page

Resolved —

Started Jun 01, 2026, 08:08 AM UTC · Resolved Jun 01, 2026, 08:08 AM UTC

Cognite AcademyCognite Hub
Timeline · 2 updates
- investigating · Jun 01, 2026, 07:35 AM UTC
  
  Status: Investigating We have identified that Polyfill.io is asking for credentials on page load for hub.cognite.com the team is still investigating this issue. Affected components Cognite Academy (Partial outage) Cognite Hub (Partial outage)
- resolved · Jun 01, 2026, 08:08 AM UTC
  
  Status: Resolved The team has identified the root cause of the issue and successfully deployed a fix. As a result, the popup is no longer appearing, and normal functionality has been restored. This incident has been fully resolved. Affected components Cognite Academy (Operational) Cognite Hub (Operational)
Latest: Status: Resolved The team has identified the root cause of the issue and successfully deployed a fix. As a result, the popup is no longer appearing, and normal functionality has be…

See the full Cognite outage history

30 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Cognite outage history →

Or sign up free to get alerts when Cognite breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 35 incidents View full outage history →

Data Modeling Search/Aggregates Not Refreshing Ongoing

Started Jun 11, 2026, 11:55 AM UTC · ● 2d 8h
files_is_uploaded_propagated_lag Resolved

Started Jun 11, 2026, 06:59 AM UTC · Resolved Jun 11, 2026, 06:59 AM UTC · —
Performance Degradation for Instance Queries Resolved

Started Jun 08, 2026, 09:52 AM UTC · Resolved Jun 08, 2026, 09:52 AM UTC · —
Data Workflow Unavailable in Cluster az-tyo-gp-001 Resolved

Started Jun 04, 2026, 02:20 PM UTC · Resolved Jun 04, 2026, 02:20 PM UTC · —
Rendering issue identified in the Agent selector in Atlas AI Resolved

Started Jun 03, 2026, 02:52 PM UTC · Resolved Jun 03, 2026, 02:52 PM UTC · —
Unwanted popup appearing in Cognite hub page Resolved

Started Jun 01, 2026, 08:08 AM UTC · Resolved Jun 01, 2026, 08:08 AM UTC · —
InField create observation asset tree not scrollable / asset selection blocked Resolved

Started May 27, 2026, 09:10 PM UTC · Resolved May 27, 2026, 09:10 PM UTC · —
DMS periodic instability on az-eastus-1, 5XX responses Resolved

Started May 22, 2026, 05:56 PM UTC · Resolved May 22, 2026, 05:56 PM UTC · —