Historia awarii Cohesity

1. 3 czerwca 2026 18:35 UTCinvestigating

   We want to let you know that we are encountering issues with our Helios service. As a result of this you might experience frequent logout in the Management portal and device connector service. We are aggressively working to resolve the issues. We apologize for any inconvenience.

2. 3 czerwca 2026 19:45 UTCinvestigating

   We have identified the root cause of the current outage and our team is actively working toward a resolution. This issue affects only CCS customers on Helios Gov. Customers managing on-premises clusters through Helios Gov are not impacted and can continue operating normally. We will share a further update as soon as one is available. We appreciate your patience.

3. 4 czerwca 2026 00:12 UTCmonitoring

   We have deployed a fix to address the issue and are closely monitoring the situation to ensure stability. We will continue to keep you updated as we confirm full resolution. Thank you for your patience.

4. 4 czerwca 2026 20:20 UTCresolved

   This incident has been resolved.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 13 maja 2026 15:22 UTCmonitoring

   Some parts of the Helios platform, including the Activity Page and Reports, may display delayed or stale information due to recent system maintenance. Your data is safe we're actively re-syncing everything and will update you as soon as services are fully restored. Thank you for your patience.

2. 14 maja 2026 09:26 UTCresolved

   This incident has been resolved.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 8 maja 2026 18:04 UTCmonitoring

   AWS has notified us of some impacted nodes on specific availability zones in US-EAST-1 clusters. All backups are still running on impacted clusters. Cohesity has added more infrastructure to mitigate this issue, but backup jobs may run longer than expected. AWS expects to be restored to full capacity within a day.

2. 9 maja 2026 15:31 UTCresolved

   AWS has resolved the issue. Everything seems to be back on line.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 6 maja 2026 11:30 UTCmonitoring

   We identified some infrastructure issues and are currently replaying system data to ensure everything is up to date. As a result, some screens like Activity Page, Reporting etc. may show stale or delayed information. We're working to get everything synced as quickly as possible and appreciate your patience!

2. 6 maja 2026 13:24 UTCresolved

   This incident has been resolved.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 30 kwietnia 2026 18:32 UTCinvestigating

   We want to let our customers know that we are currently working on an intermittent issue with logging into Helios via SSO integration. We are actively working to resolve the problem and will keep you updated on our progress.

2. 30 kwietnia 2026 21:57 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 1 maja 2026 16:20 UTCresolved

   A fix has been rolled out for this issue, and our internal monitoring indicates that all login issues have been resolved.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 5 marca 2026 12:29 UTCmonitoring

   We identified some infrastructure issues and are currently replaying system data to ensure everything is up to date. As a result, some screens like Activity Page, Reporting etc. may show stale or delayed information. We're working to get everything synced as quickly as possible and appreciate your patience!

2. 5 marca 2026 15:52 UTCresolved

   This incident has been resolved.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 4 marca 2026 03:20 UTCinvestigating

   We want to inform our customers of an issue when adding a new cloud source to CCS or when doing a source refresh. These features are currently impacted and not functional. This impact stems from the current AWS outage in the Middle East region. We are working on a fix to address this issue. We will provide updates as we make progress.

2. 4 marca 2026 04:14 UTCinvestigating

   This issue only impacts AWS cloud resources. Azure cloud resources are not impacted.

3. 4 marca 2026 22:11 UTCidentified

   We are currently implementing a fix for this issue.

4. 4 marca 2026 23:12 UTCmonitoring

   Fix is applied. Source refresh and adding new cloud sources should work. We will keep this open and monitoring over the next 24 hours.

5. 6 marca 2026 18:04 UTCmonitoring

   We found some customers were still experiencing issues due to an edge case. Fix has been applied. Monitoring.

6. 18 marca 2026 16:24 UTCresolved

   This issue should be resolved. If you continue to experience issues with adding resources or source refresh, please work with our support team.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 2 marca 2026 10:26 UTCinvestigating

   We are currently experiencing an impact to our backend infrastructure in AWS ME-Central-1 region due to operational issues with our primary cloud provider (AWS). Our team is actively monitoring the situation and working to minimize any disruption. We will share updates here as soon as we have more information on resolution and restored availability

2. 3 marca 2026 10:53 UTCinvestigating

   We are closely working with the AWS team to address issues in ME-Central-1 & ME-South-1 regions. We will continue to provide updates as we get more from our cloud provider.

3. 5 marca 2026 17:26 UTCinvestigating

   We continue to work with the AWS team to address issues in ME-Central-1 & ME-South-1 regions. We will continue to provide updates as we get more from our cloud provider.

4. 3 czerwca 2026 19:49 UTCinvestigating

   We are continuing to investigate this issue.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 6 lutego 2026 16:51 UTCinvestigating

   We are seeing connectivity issues related to Azure. We are currently investigating and will provide updates here. Our connections with AWS are not impacted.

2. 6 lutego 2026 17:03 UTCmonitoring

   We have identified the issue and have applied a fix and are closely monitoring.

3. 6 lutego 2026 23:20 UTCresolved

   This issue has been resolved.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 7 stycznia 2026 21:40 UTCinvestigating

   We want to let our customers know that we are seeing connectivity issues between the Cohesity Cluster and the Helios service. We are currently looking into this issue, and we will update you on the progress. We really apologize for the inconvenience.

2. 7 stycznia 2026 21:58 UTCinvestigating

   We want to let our customers know that activities on the Data Protect services are also impacted and we are aggressively working to resolve this issue.

3. 7 stycznia 2026 22:18 UTCidentified

   We have identified the issue and are working on a fix. We will keep you updated on the progress.

4. 7 stycznia 2026 22:41 UTCmonitoring

   A fix has been deployed, and we are closely monitoring the situation.

5. 8 stycznia 2026 01:27 UTCresolved

   This incident has been resolved.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 26 listopada 2025 16:41 UTCinvestigating

   Customers with F3 O365 licenses may experience backup issues with a 403 response code. Microsoft is aware of the issue and is rolling out a fix. We will send out another notice when we believe it is resolved.

2. 26 listopada 2025 16:43 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 26 listopada 2025 22:51 UTCresolved

   Microsoft has rolled out a fix and all should be resolved. If you are still experiencing issues, please reach out to our support team.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 18 listopada 2025 22:20 UTCinvestigating

   We want to let our customers know that we are seeing issues accessing the Helios services. We are working to resolve the problem as soon as possible. We apologize for the inconvenience.

2. 18 listopada 2025 23:04 UTCmonitoring

   Helios service is currently up and running. We are working to understand the root cause of the issue and will keep our customers posted on the update.

3. 19 listopada 2025 05:03 UTCresolved

   This incident has been resolved.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 4 listopada 2025 12:50 UTCinvestigating

   Our users may experience intermittent delays in seeing latest job updates in "Activity page & Reporting page". The team has identified the issue and is verifying the fix.

2. 5 listopada 2025 07:02 UTCmonitoring

   We have deployed a fix and are monitoring the system health.

3. 5 listopada 2025 17:43 UTCresolved

   This incident has been resolved.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 20 października 2025 14:32 UTCinvestigating

   We want to let our customers know that some of the backup runs have been impacted due to the AWS outage. We are closely looking at the issue and will be sending communication to our customers on the impacted runs.

2. 20 października 2025 22:43 UTCresolved

   AWS has reported that most of its services have recovered at this time. We have also communicated with our impacted customers due to this outage through emails and support bot cases. Our current metrics indicate that all backups are functioning normally. We are closing this incident at this time. If you have any questions, please contact Cohesity Support.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 12 sierpnia 2025 18:13 UTCinvestigating

   We will upgrade the Data Protect Service in the APAC region on August 14, 2025. This upgrade involves both the backend infrastructure and the SAAS Connectors. We don't anticipate any impact on accessing your data, backups, management console, cluster management, or other services. This rollout impacts only customers subscribed to Data Protect as a Service. Should you experience any issues, please reach out to Cohesity support.

2. 12 sierpnia 2025 18:16 UTCresolved

   This was a maintenance announcement, but was opened as an incident. Resolving incident, and scheduling the maintenance accordingly.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 11 sierpnia 2025 19:52 UTCinvestigating

   We want to let our customers know that we are seeing issues while logging into the Cohesity Cloud services. At this time, one of our underlying cloud vendors is having issues, which is causing this disruption. We are closely working with our vendor to address this issue as soon as possible. We apologize for any inconvenience.

2. 11 sierpnia 2025 19:58 UTCinvestigating

   We are continuing to investigate this issue.

3. 11 sierpnia 2025 23:02 UTCmonitoring

   The issue is addressed by our cloud vendor, and we are closely monitoring the situation.

4. 11 sierpnia 2025 23:24 UTCresolved

   This incident has been resolved.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 19 lipca 2025 18:01 UTCinvestigating

   We want to inform our customers that Teams backups are experiencing intermittent failures due to a change on the Microsoft end. We are working internally to come up with a workaround while Microsoft addresses the core issue. We apologize for any inconvenience. We will continue to provide updates on the progress.

2. 20 lipca 2025 03:06 UTCinvestigating

   We are continuing to investigate this issue.

3. 20 lipca 2025 04:03 UTCinvestigating

   We are continuing to work on this issue and escalating it to Microsoft. We will provide more updates as we hear from Microsoft. We are also working to see if we can mitigate this issue from our end. We apologize for any inconvenience.

4. 25 lipca 2025 06:09 UTCinvestigating

   We would like to inform our customers that Microsoft has confirmed the issue is resolved, and we are closely monitoring our metrics. We will continue to provide updates.

5. 28 lipca 2025 14:20 UTCresolved

   This incident has been resolved.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 5 czerwca 2025 15:11 UTCinvestigating

   We want to let our customers know that we are seeing connectivity issues with Cohesity Fortknox and we are looking into this issue. We apologize for any inconvenience.

2. 5 czerwca 2025 16:05 UTCidentified

   We have identified the issue and are working to roll out a fix. We will continue to update on the progress. We apologize for any inconvenience.

3. 5 czerwca 2025 17:12 UTCidentified

   We want to let our customers know that we have deployed the fix and closely monitoring the situation.

4. 5 czerwca 2025 19:27 UTCmonitoring

   We want to let our customers know the fix has been applied and our metrics are showing a positive trend. All of the FortKnox functions should have resumed at this time and we are closely monitoring the situation.

5. 5 czerwca 2025 20:31 UTCresolved

   We want to let our customers know the issues is resolved and we are operating normally. We apologize for the inconvenience.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 8 kwietnia 2025 14:21 UTCidentified

   Our users may experience intermittent delays in seeing latest job updates in "Activity page & Reporting page". The team has identified the issue and is verifying the fix.

2. 8 kwietnia 2025 17:48 UTCresolved

   We have addressed this issue and all the functions have been restored to a healthy state for Activity Page and Reporting Page.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 25 marca 2025 15:53 UTCinvestigating

   We want to let our customers know there are issues while logging into the Helios Portal. We are currently looking into it and will update on the progress as soon as possible.

2. 25 marca 2025 16:08 UTCinvestigating

   We are continuing to see intermittent login issues into the Helios Portal. We are aggressively working to determine the root cause of the issue. We will keep updating on the progress.

3. 25 marca 2025 16:34 UTCmonitoring

   Our customers should be able to login into the Helios Portal at this time. We are working to find the root cause of the problem. We will continue to provide an update on the progress.

4. 25 marca 2025 18:57 UTCresolved

   We have been closely monitoring our metrics for the last few hours and we could confirm the issue is resolved. The connectivity to Helios Portal was intermittent for few minutes between 8:44 AM PST and 8:51 AM PST. We have identified the root cause to be an infrastructure issue in the backend and we have addressed it. We apologize for the inconvenience.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.