Historial de interrupciones de Kenna Security

1. 19 de octubre de 2026 a las 15:54 UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. 19 de octubre de 2026 a las 16:18 UTCinvestigating

   Seguimos investigando esta cuestión.

3. 20 de octubre de 2026 a las 17:43 UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

4. 21 de octubre de 2026 a las 15:44 UTCidentified

   Seguimos trabajando en una solución para esta cuestión.

5. 23 de octubre de 2026 a las 9:43 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

Traducido automáticamente desde la actualización oficial del incidente.

1. 28 de septiembre de 2026 a las 12:26 UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. 28 de septiembre de 2026 a las 19:40 UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. 30 de septiembre de 2026 a las 8:21 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 28 de julio de 2026 a las 11:59 UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

2. 28 de julio de 2026 a las 15:25 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. 31 de julio de 2026 a las 12:27 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 8 de julio de 2026 a las 16:39 UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. 28 de julio de 2026 a las 10:31 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 30 de junio de 2026 a las 12:11 UTCinvestigating

   We are currently investigating this issue.

2. 1 de julio de 2026 a las 14:16 UTCidentified

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

3. 6 de julio de 2026 a las 13:36 UTCmonitoring

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

4. 7 de julio de 2026 a las 7:52 UTCresolved

   This incident has been resolved.

1. 30 de junio de 2026 a las 11:00 UTCinvestigating

   We are currently investigating this issue.

2. 1 de julio de 2026 a las 15:35 UTCresolved

   This incident has been resolved.

1. 8 de enero de 2026 a las 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 de enero de 2026 a las 20:24 UTCidentified

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

3. 8 de enero de 2026 a las 21:27 UTCmonitoring

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

4. 9 de enero de 2026 a las 17:24 UTCresolved

   This incident has been resolved.

1. 6 de octubre de 2025 a las 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 de octubre de 2025 a las 21:14 UTCidentified

   The issue has been identified and fix is being implemented.

3. 7 de octubre de 2025 a las 19:37 UTCidentified

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

4. 8 de octubre de 2025 a las 14:33 UTCmonitoring

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

5. 10 de octubre de 2025 a las 16:36 UTCresolved

   This incident has been resolved.

1. 12 de junio de 2025 a las 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 de junio de 2025 a las 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 de junio de 2025 a las 22:12 UTCmonitoring

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

4. 13 de junio de 2025 a las 1:30 UTCresolved

   This incident has been resolved.

1. 28 de marzo de 2025 a las 16:11 UTCinvestigating

   We are currently investigating this issue.

2. 28 de marzo de 2025 a las 16:12 UTCinvestigating

   We are continuing to investigate this issue.

3. 28 de marzo de 2025 a las 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 de marzo de 2025 a las 17:07 UTCmonitoring

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

5. 28 de marzo de 2025 a las 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 de marzo de 2025 a las 20:00 UTCresolved

   This incident has been resolved.

1. 6 de marzo de 2025 a las 13:03 UTCinvestigating

   We are currently investigating the issue

2. 6 de marzo de 2025 a las 13:40 UTCmonitoring

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

3. 7 de marzo de 2025 a las 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 de marzo de 2025 a las 20:14 UTCresolved

   This incident has been resolved.

1. 11 de febrero de 2025 a las 17:07 UTCinvestigating

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

2. 11 de febrero de 2025 a las 19:54 UTCmonitoring

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

3. 11 de febrero de 2025 a las 21:56 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 12 de febrero de 2025 a las 20:34 UTCresolved

   This incident has been resolved.

1. 16 de enero de 2025 a las 20:16 UTCidentified

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

2. 16 de enero de 2025 a las 20:19 UTCresolved

   This incident has been resolved.

1. 8 de enero de 2025 a las 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 de enero de 2025 a las 21:00 UTCmonitoring

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

3. 9 de enero de 2025 a las 15:14 UTCresolved

   This incident has been resolved.

1. 30 de octubre de 2024 a las 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 de octubre de 2024 a las 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 de noviembre de 2024 a las 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 de noviembre de 2024 a las 15:15 UTCresolved

   This incident has been resolved.

1. 1 de octubre de 2024 a las 17:08 UTCidentified

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

2. 1 de octubre de 2024 a las 17:48 UTCidentified

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

3. 1 de octubre de 2024 a las 17:57 UTCmonitoring

   All impacted environments have the fix and we are monitoring.

4. 1 de octubre de 2024 a las 20:35 UTCresolved

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

1. 21 de agosto de 2024 a las 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 de agosto de 2024 a las 16:16 UTCinvestigating

   We are continuing to investigate this issue.

3. 21 de agosto de 2024 a las 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 de agosto de 2024 a las 20:32 UTCidentified

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

5. 22 de agosto de 2024 a las 15:25 UTCmonitoring

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

6. 22 de agosto de 2024 a las 15:43 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 23 de agosto de 2024 a las 14:50 UTCresolved

   This incident has been resolved.

1. 13 de agosto de 2024 a las 14:11 UTCinvestigating

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

2. 13 de agosto de 2024 a las 15:16 UTCmonitoring

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

3. 14 de agosto de 2024 a las 16:07 UTCresolved

   This incident has been resolved.

1. 18 de julio de 2024 a las 21:27 UTCinvestigating

   We are currently experiencing an issue with NVD data integration

2. 19 de julio de 2024 a las 0:19 UTCmonitoring

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

3. 19 de julio de 2024 a las 16:27 UTCresolved

   This incident has been resolved.

1. 18 de julio de 2024 a las 13:09 UTCinvestigating

   We are currently investigating this issue.

2. 18 de julio de 2024 a las 17:18 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 de julio de 2024 a las 17:18 UTCmonitoring

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

4. 18 de julio de 2024 a las 19:58 UTCresolved

   This incident has been resolved.