WithSecure services Status

Resolved: This incident has been resolved. All affected services are operating normally.

Monitoring: The deployed fix was performed as expected, and portal performance has returned to normal levels. The backlog of queued items has been fully processed and cleared.

At this time, we are not observing any widespread impact on the service. We will continue to monitor the environment closely to ensure ongoing stability and verify that no further issues arise.

Thank you for your patience while we worked to resolve this issue.

Identified: Service recovery continues to make steady progress following the deployment of the fix.

The backlog of scans and reports is being processed successfully, and we continue to observe improvements in overall service performance and availability. We expect the situation to normalize during the weekend.

Thank you for your patience and continued understanding while we work towards full recovery.

Identified: Recovery continues to progress as expected, with the backlog of scans and reports steadily decreasing. We are seeing ongoing improvement across the service.

Thank you for your continued patience and understanding in this matter.

Identified: We have identified an issue affecting the database, which has resulted in a backlog in scan and report processing.

A fix has been deployed, and the service is now recovering. We expect it to take up to 96 hours for the backlog of scans and reports to be fully processed and for normal operation to resume.

We apologize for any inconvenience this may cause and will continue to monitor the situation closely.

Investigating: We are currently investigating reports of performance degradation affecting WithSecure Elements Exposure Management (XM).

Affected users may experience:

• Slow response times across the XM portal • Errors when accessing Vulnerability Management (VM) scan groups • "Failed to fetch tags" error messages • "Failed to fetch scheduling templates" error messages • Scans remaining in a Queued or Running state for extended periods • Multiple HTTP 4xx error responses • Intermittent issues impacting scan-related functionality and workflows

Our teams are actively investigating and working to restore normal service. Further updates will be provided as they become available.

We apologize for the inconvenience and thank you for your patience.

Resolved: This incident has been resolved. All affected services are operating normally.

Monitoring: The deployed fix was performed as expected, and portal performance has returned to normal levels. The backlog of queued items has been fully processed and cleared.

At this time, we are not observing any widespread impact on the service. We will continue to monitor the environment closely to ensure ongoing stability and verify that no further issues arise.

Thank you for your patience while we worked to resolve this issue.

Identified: Service recovery continues to make steady progress following the deployment of the fix.

The backlog of scans and reports is being processed successfully, and we continue to observe improvements in overall service performance and availability. We expect the situation to normalize during the weekend.

Thank you for your patience and continued understanding while we work towards full recovery.

Identified: Recovery continues to progress as expected, with the backlog of scans and reports steadily decreasing. We are seeing ongoing improvement across the service.

Thank you for your continued patience and understanding in this matter.

Identified: We have identified an issue affecting the database, which has resulted in a backlog in scan and report processing.

A fix has been deployed, and the service is now recovering. We expect it to take up to 96 hours for the backlog of scans and reports to be fully processed and for normal operation to resume.

We apologize for any inconvenience this may cause and will continue to monitor the situation closely.

Investigating: We are currently investigating reports of performance degradation affecting WithSecure Elements Exposure Management (XM).

Affected users may experience:

• Slow response times across the XM portal • Errors when accessing Vulnerability Management (VM) scan groups • "Failed to fetch tags" error messages • "Failed to fetch scheduling templates" error messages • Scans remaining in a Queued or Running state for extended periods • Multiple HTTP 4xx error responses • Intermittent issues impacting scan-related functionality and workflows

Our teams are actively investigating and working to restore normal service. Further updates will be provided as they become available.

We apologize for the inconvenience and thank you for your patience.