Kenna Security driftsforstyrrelser

1. 19. oktober 2026 kl. 15.54 UTCinvestigating

   Vi undersøger i øjeblikket dette spørgsmål.

2. 19. oktober 2026 kl. 16.18 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål.

3. 20. oktober 2026 kl. 17.43 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

4. 21. oktober 2026 kl. 15.44 UTCidentified

   Vi fortsætter med at arbejde på en løsning på dette problem.

5. 23. oktober 2026 kl. 09.43 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

6. 27. oktober 2026 kl. 10.15 UTCmonitoring

   Vi fortsætter med at overvåge for yderligere spørgsmål.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 28. september 2026 kl. 12.26 UTCinvestigating

   Vi undersøger i øjeblikket dette spørgsmål.

2. 28. september 2026 kl. 19.40 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

3. 30. september 2026 kl. 08.21 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 28. juli 2026 kl. 11.59 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

2. 28. juli 2026 kl. 15.25 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 31. juli 2026 kl. 12.27 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 8. juli 2026 kl. 16.39 UTCinvestigating

   Vi undersøger i øjeblikket dette spørgsmål.

2. 28. juli 2026 kl. 10.31 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 30. juni 2026 kl. 12.11 UTCinvestigating

   We are currently investigating this issue.

2. 1. juli 2026 kl. 14.16 UTCidentified

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

3. 6. juli 2026 kl. 13.36 UTCmonitoring

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

4. 7. juli 2026 kl. 07.52 UTCresolved

   This incident has been resolved.

1. 30. juni 2026 kl. 11.00 UTCinvestigating

   We are currently investigating this issue.

2. 1. juli 2026 kl. 15.35 UTCresolved

   This incident has been resolved.

1. 8. januar 2026 kl. 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. januar 2026 kl. 20.24 UTCidentified

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

3. 8. januar 2026 kl. 21.27 UTCmonitoring

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

4. 9. januar 2026 kl. 17.24 UTCresolved

   This incident has been resolved.

1. 6. oktober 2025 kl. 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. oktober 2025 kl. 21.14 UTCidentified

   The issue has been identified and fix is being implemented.

3. 7. oktober 2025 kl. 19.37 UTCidentified

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

4. 8. oktober 2025 kl. 14.33 UTCmonitoring

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

5. 10. oktober 2025 kl. 16.36 UTCresolved

   This incident has been resolved.

1. 12. juni 2025 kl. 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. juni 2025 kl. 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. juni 2025 kl. 22.12 UTCmonitoring

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

4. 13. juni 2025 kl. 01.30 UTCresolved

   This incident has been resolved.

1. 28. marts 2025 kl. 16.11 UTCinvestigating

   We are currently investigating this issue.

2. 28. marts 2025 kl. 16.12 UTCinvestigating

   We are continuing to investigate this issue.

3. 28. marts 2025 kl. 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. marts 2025 kl. 17.07 UTCmonitoring

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

5. 28. marts 2025 kl. 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. marts 2025 kl. 20.00 UTCresolved

   This incident has been resolved.

1. 6. marts 2025 kl. 13.03 UTCinvestigating

   We are currently investigating the issue

2. 6. marts 2025 kl. 13.40 UTCmonitoring

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

3. 7. marts 2025 kl. 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. marts 2025 kl. 20.14 UTCresolved

   This incident has been resolved.

1. 11. februar 2025 kl. 17.07 UTCinvestigating

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

2. 11. februar 2025 kl. 19.54 UTCmonitoring

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

3. 11. februar 2025 kl. 21.56 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 12. februar 2025 kl. 20.34 UTCresolved

   This incident has been resolved.

1. 16. januar 2025 kl. 20.16 UTCidentified

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

2. 16. januar 2025 kl. 20.19 UTCresolved

   This incident has been resolved.

1. 8. januar 2025 kl. 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. januar 2025 kl. 21.00 UTCmonitoring

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

3. 9. januar 2025 kl. 15.14 UTCresolved

   This incident has been resolved.

1. 30. oktober 2024 kl. 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. oktober 2024 kl. 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. november 2024 kl. 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. november 2024 kl. 15.15 UTCresolved

   This incident has been resolved.

1. 1. oktober 2024 kl. 17.08 UTCidentified

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

2. 1. oktober 2024 kl. 17.48 UTCidentified

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

3. 1. oktober 2024 kl. 17.57 UTCmonitoring

   All impacted environments have the fix and we are monitoring.

4. 1. oktober 2024 kl. 20.35 UTCresolved

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

1. 21. august 2024 kl. 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. august 2024 kl. 16.16 UTCinvestigating

   We are continuing to investigate this issue.

3. 21. august 2024 kl. 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. august 2024 kl. 20.32 UTCidentified

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

5. 22. august 2024 kl. 15.25 UTCmonitoring

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

6. 22. august 2024 kl. 15.43 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 23. august 2024 kl. 14.50 UTCresolved

   This incident has been resolved.

1. 13. august 2024 kl. 14.11 UTCinvestigating

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

2. 13. august 2024 kl. 15.16 UTCmonitoring

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

3. 14. august 2024 kl. 16.07 UTCresolved

   This incident has been resolved.

1. 18. juli 2024 kl. 21.27 UTCinvestigating

   We are currently experiencing an issue with NVD data integration

2. 19. juli 2024 kl. 00.19 UTCmonitoring

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

3. 19. juli 2024 kl. 16.27 UTCresolved

   This incident has been resolved.

1. 18. juli 2024 kl. 13.09 UTCinvestigating

   We are currently investigating this issue.

2. 18. juli 2024 kl. 17.18 UTCinvestigating

   We are continuing to investigate this issue.

3. 18. juli 2024 kl. 17.18 UTCmonitoring

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

4. 18. juli 2024 kl. 19.58 UTCresolved

   This incident has been resolved.