Cognite logo

Is Cognite Down?

SaaSLive status, outages, and incident history

No. Cognite is up right now.

Every monitored Cognite system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · 60s while moving1 active incident

Know the moment Cognite breaks

Cognite is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Cognite status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Cognite Component Status

The main Cognite systems on this page. All 3 are operational right now.

3operational
Cognite Data Fusion API
Operational
Cognite Data Fusion UI
Operational
Cognite Maintain
Operational

Component statuses may change independently during partial outages.

Recent Cognite Outages & Incidents

Incident history from the official Cognite status page, including resolution updates.

Degraded search and data modeling indexing performanceResolved Sep 23, 2026 · 18h 22mResolved

The performance degradation affecting Data Modeling search and indexing in **westeurope-1** has been fully resolved. Syncer capacity has been restored, cluster health metrics have returned to normal, and all indexing backlogs have cleared. Search, aggregation, and data modeling queries are functioning as expected. We are continuing to monitor the services to ensure ongoing stability. --- [2026-09-23T19:18:00Z] (monitoring) • **Problem:** The Propertygraph Elasticsearch cluster in **westeurope-1** experienced degradation, temporarily entering yellow and red states. • **Impact:** Customers with projects in `westeurope-1` may experience delays in newly created instances appearing in search results, along with elevated latency for search and aggregate queries affecting data modeling indexing (`datamodelstorage`) Core data storage is unaffected. • **Root Cause:** A syncer update triggered concurrent restarts across syncer deployments simultaneously, overwhelming the search master nodes with high-volume reads. In addition, an search pod encountered a PVC mount failure during rolling updates. • **Status & Mitigation:** Mitigation steps have been applied. Our engineering team scaled down the syncers to allow the cluster to recover to a healthy green state, subsequently re-enabled the synchronizers in stages, and resolved the PVC volume mount issue. The cluster is stabilizing, and our team is actively monitoring system performance and recovery. --- [2026-09-23T17:45:19Z] (investigating) We are currently experiencing performance degradation affecting search and data modeling indexing services in the **westeurope-1** region. **Impact:** Search and aggregate queries may experience elevated latency, and newly created instances or index updates may take longer to appear in search results. Core data storage is unaffected. Our engineering team is actively investigating the issue and working on mitigation steps to stabilize the service. We will provide updates as more information becomes available

Indexing in data modeling is degradedResolved Sep 22, 2026 · 11h 59mResolved

Service has been restored. The Elasticsearch cluster in westeurope-1 has stabilized, and search, aggregation, and data-modeling indexing are operating normally. --- [2026-09-23T00:08:09Z] (monitoring) The Elasticsearch cluster in **westeurope-1** became overloaded and entered a red state. This degraded search and data-modeling indexing. search and aggregate requests could be slow or fail, while new instances and index changes could take longer to appear. **Root cause:** A rollout restart of **pg3** overloaded the Elasticsearch cluster. **Fixing status:** The incident is now in **Monitoring**. Engineering team paused some background synchronizers to reduce load, allowed Elasticsearch to stabilize, and then started re-enabling the synchronizers. The fix was marked as applied. --- [2026-09-22T21:10:57Z] (investigating) We are currently investigating performance degradation and high latency affecting search and data modeling services in the **westeurope-1** region. **Impact:** Search and aggregate requests may experience high latency or temporary failures. Newly created instances or index updates may take longer than expected to appear. **Status:** Our engineering team is currently scaling down background syncing processes to reduce load and restore cluster stability. Further updates will be posted as soon as they are available.

Degraded Data Modeling Indexing and Search in westeurope-1Resolved Sep 22, 2026 · 50h 7mResolved

The performance degradation affecting Data Modeling search and indexing in **westeurope-1** has been fully resolved. Syncer capacity has been restored, cluster health metrics have returned to normal, and all indexing backlogs have cleared. Search, aggregation, and data modeling queries are functioning as expected. We are continuing to monitor the services to ensure ongoing stability. --- [2026-09-22T10:31:57Z] (monitoring) The underlying cluster in `westeurope-1` has stabilized, and search and aggregate queries are functioning normally. Indexing pipelines are currently processing the remaining backlog, so some users may still see slight delays in newly ingested data appearing. We are monitoring the recovery closely. --- [2026-09-22T10:08:52Z] (investigating) We have identified an issue affecting search and data modeling indexing in the `westeurope-1` region. Users and automated pipelines in this cluster may experience delays in newly ingested data or schema updates appearing in search and data modeling views. Querying existing indexed data and other CDF services remain operational. Our engineering team has implemented traffic-shedding and resource adjustments to stabilize the underlying cluster, and indexing throughput is beginning to recover. We are closely monitoring cluster health and will provide our next update soon,

Cognite Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Cognite incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 7 days with incidentsSep 25

Live Cognite Outage Reports

Problems reported by engineers using Cognite. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Cognite problems reported yet.

Something wrong with Cognite on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Cognite

Is Cognite down? Cognite reports live availability for 16 components at status.cognite.com, among them Cognite InField, Cognite Data Fusion UI and Cognite Hub. Track Cognite outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured Cognite uptime at 99.97%. Response times, incident history, and SLA tracking for Cognite are available on the PulsAPI dashboard.

Cognite Status FAQ

Is Cognite down right now?

The verdict at the top of this page comes from the latest poll of the official Cognite status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Cognite is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Cognite recovers.

How do I check Cognite uptime history?

PulsAPI tracks Cognite uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.97%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Cognite changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Cognite outages?

PulsAPI reads the official Cognite status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Cognite components?

Yes. PulsAPI monitors 3 individual Cognite components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Cognite goes down?

Yes. Create a free account and subscribe to Cognite: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Cognite to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Cognite problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Cognite?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Cognite plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Cognite with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services