Histórico de interrupções do Kenna Security

1. 19 Here 2026 da 15:54 UTCinvestigating

   Estamos actualmente a investigar esta questão.

2. 19 Here 2026 da 16:18 UTCinvestigating

   Continuamos a investigar esta questão.

3. 20 Here 2026 da 17:43 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

4. 21 Here 2026 da 15:44 UTCidentified

   Continuamos trabalhando em uma solução para esse problema.

5. 23 Here 2026 da 09:43 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

6. 27 Here 2026 da 10:15 UTCmonitoring

   Continuamos monitorando quaisquer outros problemas.

Traduzido automaticamente da atualização oficial do incidente.

1. 28 Gwengolo 2026 da 12:26 UTCinvestigating

   Estamos actualmente a investigar esta questão.

2. 28 Gwengolo 2026 da 19:40 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 30 Gwengolo 2026 da 08:21 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 28 Gouere 2026 da 11:59 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

2. 28 Gouere 2026 da 15:25 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

3. 31 Gouere 2026 da 12:27 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 8 Gouere 2026 da 16:39 UTCinvestigating

   Estamos actualmente a investigar esta questão.

2. 28 Gouere 2026 da 10:31 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 30 Mezheven 2026 da 12:11 UTCinvestigating

   We are currently investigating this issue.

2. 1 Gouere 2026 da 14:16 UTCidentified

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

3. 6 Gouere 2026 da 13:36 UTCmonitoring

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

4. 7 Gouere 2026 da 07:52 UTCresolved

   This incident has been resolved.

1. 30 Mezheven 2026 da 11:00 UTCinvestigating

   We are currently investigating this issue.

2. 1 Gouere 2026 da 15:35 UTCresolved

   This incident has been resolved.

1. 8 Genver 2026 da 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 Genver 2026 da 20:24 UTCidentified

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

3. 8 Genver 2026 da 21:27 UTCmonitoring

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

4. 9 Genver 2026 da 17:24 UTCresolved

   This incident has been resolved.

1. 6 Here 2025 da 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 Here 2025 da 21:14 UTCidentified

   The issue has been identified and fix is being implemented.

3. 7 Here 2025 da 19:37 UTCidentified

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

4. 8 Here 2025 da 14:33 UTCmonitoring

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

5. 10 Here 2025 da 16:36 UTCresolved

   This incident has been resolved.

1. 12 Mezheven 2025 da 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 Mezheven 2025 da 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 Mezheven 2025 da 22:12 UTCmonitoring

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

4. 13 Mezheven 2025 da 01:30 UTCresolved

   This incident has been resolved.

1. 28 Meurzh 2025 da 16:11 UTCinvestigating

   We are currently investigating this issue.

2. 28 Meurzh 2025 da 16:12 UTCinvestigating

   We are continuing to investigate this issue.

3. 28 Meurzh 2025 da 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 Meurzh 2025 da 17:07 UTCmonitoring

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

5. 28 Meurzh 2025 da 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 Meurzh 2025 da 20:00 UTCresolved

   This incident has been resolved.

1. 6 Meurzh 2025 da 13:03 UTCinvestigating

   We are currently investigating the issue

2. 6 Meurzh 2025 da 13:40 UTCmonitoring

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

3. 7 Meurzh 2025 da 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 Meurzh 2025 da 20:14 UTCresolved

   This incident has been resolved.

1. 11 Cʼhwevrer 2025 da 17:07 UTCinvestigating

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

2. 11 Cʼhwevrer 2025 da 19:54 UTCmonitoring

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

3. 11 Cʼhwevrer 2025 da 21:56 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 12 Cʼhwevrer 2025 da 20:34 UTCresolved

   This incident has been resolved.

1. 16 Genver 2025 da 20:16 UTCidentified

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

2. 16 Genver 2025 da 20:19 UTCresolved

   This incident has been resolved.

1. 8 Genver 2025 da 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 Genver 2025 da 21:00 UTCmonitoring

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

3. 9 Genver 2025 da 15:14 UTCresolved

   This incident has been resolved.

1. 30 Here 2024 da 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 Here 2024 da 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 Du 2024 da 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 Du 2024 da 15:15 UTCresolved

   This incident has been resolved.

1. 1 Here 2024 da 17:08 UTCidentified

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

2. 1 Here 2024 da 17:48 UTCidentified

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

3. 1 Here 2024 da 17:57 UTCmonitoring

   All impacted environments have the fix and we are monitoring.

4. 1 Here 2024 da 20:35 UTCresolved

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

1. 21 Eost 2024 da 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 Eost 2024 da 16:16 UTCinvestigating

   We are continuing to investigate this issue.

3. 21 Eost 2024 da 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 Eost 2024 da 20:32 UTCidentified

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

5. 22 Eost 2024 da 15:25 UTCmonitoring

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

6. 22 Eost 2024 da 15:43 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 23 Eost 2024 da 14:50 UTCresolved

   This incident has been resolved.

1. 13 Eost 2024 da 14:11 UTCinvestigating

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

2. 13 Eost 2024 da 15:16 UTCmonitoring

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

3. 14 Eost 2024 da 16:07 UTCresolved

   This incident has been resolved.

1. 18 Gouere 2024 da 21:27 UTCinvestigating

   We are currently experiencing an issue with NVD data integration

2. 19 Gouere 2024 da 00:19 UTCmonitoring

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

3. 19 Gouere 2024 da 16:27 UTCresolved

   This incident has been resolved.

1. 18 Gouere 2024 da 13:09 UTCinvestigating

   We are currently investigating this issue.

2. 18 Gouere 2024 da 17:18 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 Gouere 2024 da 17:18 UTCmonitoring

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

4. 18 Gouere 2024 da 19:58 UTCresolved

   This incident has been resolved.