Cohesity Outage History

Cohesity is up right now

Pingoru has recorded 49 incidents for Cohesity: 20 in the last 12 months and 7 in the last 90 days.

Source: status.cohesity.com

49incidents recorded
20last 12 months
7last 90 days
2 daystypical duration
Incidents per month
024AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking Cohesity in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202616 of 720 (1%)
May 2026358 of 744 (8%)
June 2026126 of 720 (4%)
July 202600 of 744 (0%)
August 20262175 of 744 (23%)
September 20264227 of 720 (32%)
October 202615 of 590 (1%)

Incidents, newest first

Major December 2, 2024 Cohesity Cloud Services access 19m Cohesity Cloud Services Portal, Data Protect delivered as a Service, Cohesity FortKnox, Cohesity DataHawk and 1 more

Started Dec 02, 2024, 10:25 PM UTC· resolved Dec 02, 2024, 10:44 PM UTC

  1. investigating Dec 02, 2024, 10:25 PM UTC

    We want to let our customers know that we are observing connectivity issues to CCS landing page and APIs as part of the scheduled rollout. We are aggressively looking into this issue and will post updates on the progress. We apologize for any inconvenience.

  2. monitoring Dec 02, 2024, 10:34 PM UTC

    We have identified the issue and have pushed the relevant fixes to address the issues.

  3. resolved Dec 02, 2024, 10:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 30, 2024 Cohesity Cloud Services - US-East 2 - Infrastructure issues 1d 10h Data Protect delivered as a Service

Started Nov 30, 2024, 02:38 PM UTC· resolved Dec 02, 2024, 01:38 AM UTC

  1. investigating Nov 30, 2024, 02:38 PM UTC

    We want to let our customers know that we are experiencing infrastructure issues in US East 2 region due to which indexing might get delayed. We are still assessing the current situation to understand the impact and working to address the issue. We apologize for any inconvenience.

  2. investigating Nov 30, 2024, 04:08 PM UTC

    We are continuing to investigate the issue and have engaged our cloud vendor to understand the root cause and identify the mitigation steps. We will continue to provide status update. We apologize for any inconvenience.

  3. investigating Nov 30, 2024, 05:34 PM UTC

    We are continuing to investigate the issue. Our indexing services are impacted due to node stability issues that are holding the indexes. We are seeing some positive signs on the stabilization of the nodes, but we are continuing to work with our cloud vendors. We will continue to provide status update. We apologize for any inconvenience.

  4. investigating Nov 30, 2024, 06:32 PM UTC

    Updating the Data protect service status to operational

  5. investigating Nov 30, 2024, 06:32 PM UTC

    Updated the Data protect service status to operational

  6. monitoring Nov 30, 2024, 06:39 PM UTC

    We want to let our customers know that the issue is resolved. Our metrics are showing a positive trend on the indexing backlog and we are closely monitoring the situation. The root cause of the issue is due to a read/write latency on the underlying volume and we have worked with our cloud vendor to resolve the issue. We apologize for any inconvenience.

  7. monitoring Nov 30, 2024, 10:03 PM UTC

    The issue is resolved at this time. Our metrics are trending in the right direction. We will keep this incident open for the next 24 hours and will provide one more update before closing it.

  8. resolved Dec 02, 2024, 01:38 AM UTC

    This incident has been resolved.

Read the full incident report →