Vendor Status Watch

← all vendors

Cohesity status history

Current state: operational — “All Systems Operational” per https://status.cohesity.com (Atlassian Statuspage), checked 2026-09-24 12:28 UTC.

4incidents, last 30 days
7incidents, last 90 days
21incidents on record
Incidents per week, last 12 weeks:

How long do Cohesity incidents last?

13.1 hmedian incident duration16 measured
14.5 days90th percentile1 in 10 ran longer
21.8 hmedian, major/critical only5 incidents

From 16 incidents with a vendor-posted start and resolve time. Longest on record: Intermittent issue impacting OneDrive and Mailbox workloads in CCS. — 22.7 days (2026-08-24 20:47 UTC). Excluded, never estimated: 3 scheduled maintenance, 2 still open / no resolve time. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (21)

StartedIncidentStatusImpactDuration
2026-09-22 18:41 UTCData Processing Delays - GlobalSearch Affectedinvestigatingnoneopen
2026-09-22 11:35 UTCCohesity cloud services scheduled maintenance for Data Protect Service (GovCloud)maintenancemaintenance24 h 54 min (approx.)
2026-09-19 08:30 UTCCohesity Cloud Services Infrastructure Maintenancemaintenancemaintenance27 h 59 min (approx.)
2026-09-01 17:34 UTCMicrosoft Issue May have impacted M365 workloads (CCS)resolvednone0 min
2026-08-24 20:47 UTCIntermittent issue impacting OneDrive and Mailbox workloads in CCS.resolvedminor22 d 16 h
2026-08-24 17:16 UTCData Processing Delays - Activity Page and Reports Affectedresolvedminor22 h 22 min
2026-07-16 19:32 UTCCustomer Action Needed - Migrate to Certificate Based Authentication (CBA)resolvedmaintenance61 d 18 h
2026-06-03 18:35 UTCHelios Gov & CCS Gov Impactresolvedmajor25 h 44 min
2026-05-13 15:22 UTCStale Activity Page and Reporting Data on Heliosresolvedminor18 h 04 min
2026-05-08 18:04 UTCCCS AWS Availability Zone incident on US-EAST-1 - minor impactresolvednone21 h 26 min
2026-05-06 11:30 UTCStale Activity Page and Reporting Data on Heliosresolvedminor1 h 54 min
2026-04-30 18:32 UTCSSO authenticationresolvedmajor21 h 48 min
2026-03-05 12:29 UTCStale Activity Page and Reporting Data on Heliosresolvedminor3 h 23 min
2026-03-04 03:20 UTCCCS - Source Refresh and New Cloud Source Additions Currently Not Workingresolvedmajor14 d 13 h
2026-03-02 10:26 UTCCCS impacted in AWS UAE regioninvestigatingmajoropen
2026-02-06 16:51 UTCCohesity Cloud Services Backup issues involving Azureresolvedmajor6 h 28 min
2026-01-07 21:40 UTCHelios Connectivityresolvednone3 h 46 min
2025-11-26 16:41 UTCMicrosoft Issue Impacting CCS backup jobsresolvednone6 h 10 min
2025-11-18 22:20 UTCIssues accessing the Helios serviceresolvedmajor6 h 43 min
2025-11-04 12:50 UTCIntermittent delays in loading Activity & Reporting page on Heliosresolvedminor28 h 53 min
2025-10-20 14:32 UTCAWS outage impact on backupsresolvednone8 h 11 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Cohesity with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "cohesity"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}