Historia awarii Kenna Security

1. 19 października 2026 15:54 UTCinvestigating

   Obecnie badamy tę kwestię.

2. 19 października 2026 16:18 UTCinvestigating

   Nadal badamy tę kwestię.

3. 20 października 2026 17:43 UTCidentified

   Problem został zidentyfikowany i jest w trakcie wdrażania.

4. 21 października 2026 15:44 UTCidentified

   Kontynuujemy prace nad rozwiązaniem tego problemu.

5. 23 października 2026 09:43 UTCmonitoring

   Wprowadzono rozwiązanie i monitorujemy wyniki.

6. 27 października 2026 10:15 UTCmonitoring

   Nadal monitorujemy wszelkie dalsze problemy.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 28 września 2026 12:26 UTCinvestigating

   Obecnie badamy tę kwestię.

2. 28 września 2026 19:40 UTCidentified

   Problem został zidentyfikowany i jest w trakcie wdrażania.

3. 30 września 2026 08:21 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 28 lipca 2026 11:59 UTCidentified

   Problem został zidentyfikowany i jest w trakcie wdrażania.

2. 28 lipca 2026 15:25 UTCmonitoring

   Wprowadzono rozwiązanie i monitorujemy wyniki.

3. 31 lipca 2026 12:27 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 8 lipca 2026 16:39 UTCinvestigating

   Obecnie badamy tę kwestię.

2. 28 lipca 2026 10:31 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 30 czerwca 2026 12:11 UTCinvestigating

   We are currently investigating this issue.

2. 1 lipca 2026 14:16 UTCidentified

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

3. 6 lipca 2026 13:36 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 7 lipca 2026 07:52 UTCresolved

   This incident has been resolved.

1. 30 czerwca 2026 11:00 UTCinvestigating

   We are currently investigating this issue.

2. 1 lipca 2026 15:35 UTCresolved

   This incident has been resolved.

1. 8 stycznia 2026 18:41 UTCinvestigating

   Virtual Tunnel clients are unable to establish connection. Connector runs using Virtual Tunnel are returning failures. We are currently investigating this issue.

2. 8 stycznia 2026 20:24 UTCidentified

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

3. 8 stycznia 2026 21:27 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 9 stycznia 2026 17:24 UTCresolved

   This incident has been resolved.

1. 6 października 2025 18:26 UTCinvestigating

   Users might be experiencing delays and timeouts when navigating the CVM dashboard and performing data updates. We are currently investigating this issue.

2. 6 października 2025 21:14 UTCidentified

   The issue has been identified and fix is being implemented.

3. 7 października 2025 19:37 UTCidentified

   We are continuing to work on a fix for this issue.

4. 8 października 2025 14:33 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 10 października 2025 16:36 UTCresolved

   This incident has been resolved.

1. 12 czerwca 2025 19:33 UTCidentified

   Multiple GCP services are currently experiencing partial outages or degraded performance. This is impacting key components of the CVM platform across several environments.

2. 12 czerwca 2025 22:04 UTCidentified

   Google Cloud Platform has started mitigating the issue. CVM services are becoming more stable, but we’re still monitoring closely as GCP continues to stabilize.

3. 12 czerwca 2025 22:12 UTCmonitoring

   CVM services have stabilized across all environments, and we're monitoring closely to ensure continued performance.

4. 13 czerwca 2025 01:30 UTCresolved

   This incident has been resolved.

1. 28 marca 2025 16:11 UTCinvestigating

   We are currently investigating this issue.

2. 28 marca 2025 16:12 UTCinvestigating

   We are continuing to investigate this issue.

3. 28 marca 2025 16:17 UTCidentified

   The issue has been identified and a fix is being implemented., The MS Defender TVM connector is importing fewer assets than usual.

4. 28 marca 2025 17:07 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 28 marca 2025 17:27 UTCmonitoring

   The root cause has been identified and platform improvements have already been implemented. The Engineering team is currently monitoring the system, and connector runs have stabilized across the affected environments

6. 28 marca 2025 20:00 UTCresolved

   This incident has been resolved.

1. 6 marca 2025 13:03 UTCinvestigating

   We are currently investigating the issue

2. 6 marca 2025 13:40 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 7 marca 2025 19:51 UTCmonitoring

   We have released a potential fix for the outage you may have experienced and will continue to monitor the situation.

4. 10 marca 2025 20:14 UTCresolved

   This incident has been resolved.

1. 11 lutego 2025 17:07 UTCinvestigating

   Connector runs might be stalled. We are currently investigating this issue.

2. 11 lutego 2025 19:54 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 11 lutego 2025 21:56 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 12 lutego 2025 20:34 UTCresolved

   This incident has been resolved.

1. 16 stycznia 2025 20:16 UTCidentified

   We are rolling back the recent NACL-related change to restore affected services

2. 16 stycznia 2025 20:19 UTCresolved

   This incident has been resolved.

1. 8 stycznia 2025 15:42 UTCinvestigating

   Qualys connector runs might fail with the error: "There was an issue parsing Qualys' response, which appears to be malformed XML. Please re-run your connector, and contact support if this issue persists." An internal error is returned by Qualys when retrieving the host list. We are currently investigating this issue.

2. 8 stycznia 2025 21:00 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 9 stycznia 2025 15:14 UTCresolved

   This incident has been resolved.

1. 30 października 2024 14:48 UTCinvestigating

   We are currently investigating an issue with a 3rd party for failed responses [MS Defender TVM.] This issue is isolated to the single 3rd party. We are currently unable to extract data from their endpoint.

2. 31 października 2024 12:15 UTCidentified

   The MS Defender TVM Connector issue has been identified as isolated to a 3rd party service degradation. This is currently affecting our ability to retrieve vulnerability data, resulting in failed responses from the MS Defender TVM endpoint, we are actively weighing possible workarounds to mitigate the impact while awaiting further updates from Microsoft.

3. 1 listopada 2024 17:35 UTCmonitoring

   The CVM engineering team has identified an issue with the Microsoft Defender for Endpoint APIs. Currently, attempting to export files from the following endpoint: https://api.securitycenter.microsoft.com/api/machines/SoftwareVulnerabilitiesExport results in a 404 error indicating that the specified blob does not exist. As a temporary workaround, we have moved the vulnerability extracts to the SoftwareVulnerabilitiesByMachine endpoint. Please note this endpoint operates significantly slower than the file export previously used, therefore, we expect connector runs to take longer than usual while the workaround is in place. The engineering team will continue collaborating with Microsoft to revert to the original file export API once the issue is resolved.

4. 6 listopada 2024 15:15 UTCresolved

   This incident has been resolved.

1. 1 października 2024 17:08 UTCidentified

   The issues is identified and we are currently deploying a fix.

2. 1 października 2024 17:48 UTCidentified

   We are continuing to work on a fix for this issue.

3. 1 października 2024 17:57 UTCmonitoring

   All impacted environments have the fix and we are monitoring.

4. 1 października 2024 20:35 UTCresolved

   Systems have been functioning as normal for the last 3+ hours, moving this incident to resolved.

1. 21 sierpnia 2024 15:39 UTCinvestigating

   US Prod 1 is experiencing a backlog, customers may experience slow response times and 504 errors. We are currently investigating this issue.

2. 21 sierpnia 2024 16:16 UTCinvestigating

   We are continuing to investigate this issue.

3. 21 sierpnia 2024 19:21 UTCinvestigating

   Metrics in homepage and dashboard risk meter page have been temporarily disabled to alleviate the observed performance issues. We are continuing to investigate this issue.

4. 21 sierpnia 2024 20:32 UTCidentified

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

5. 22 sierpnia 2024 15:25 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

6. 22 sierpnia 2024 15:43 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 23 sierpnia 2024 14:50 UTCresolved

   This incident has been resolved.

1. 13 sierpnia 2024 14:11 UTCinvestigating

   Connector runs for multiple connectors are not able to complete. We are currently investigating this issue.

2. 13 sierpnia 2024 15:16 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 14 sierpnia 2024 16:07 UTCresolved

   This incident has been resolved.

1. 18 lipca 2024 21:27 UTCinvestigating

   We are currently experiencing an issue with NVD data integration

2. 19 lipca 2024 00:19 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 19 lipca 2024 16:27 UTCresolved

   This incident has been resolved.

1. 18 lipca 2024 13:09 UTCinvestigating

   We are currently investigating this issue.

2. 18 lipca 2024 17:18 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 lipca 2024 17:18 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 18 lipca 2024 19:58 UTCresolved

   This incident has been resolved.