Aug <var data-var='date'>17</var>, <var data-var='time'>09:10</var> UTC 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. Aug <var data-var='date'>14</var>, <var data-var='time'>12:11</var> UTC Update - 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. Aug <var data-var='date'>13</var>, <var data-var='time'>13:20</var> UTC Update - 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. Aug <var data-var='date'>12</var>, <var data-var='time'>09:08</var> UTC 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. Aug <var data-var='date'>11</var>, <var data-var='time'>11:56</var> UTC 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.

Exposure Management (XM) Performance Degradation and Intermittent Errors

Jul <var data-var='date'>28</var>, <var data-var='time'>12:33</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>27</var>, <var data-var='time'>12:13</var> UTC Monitoring - A corrective fix has been deployed. We are actively monitoring the results to confirm that the issue has been fully resolved and that services remain stable. Jul <var data-var='date'>24</var>, <var data-var='time'>12:46</var> UTC Identified - At this time, the issue does not appear to affect all status update attempts consistently. Our investigation indicates that the issue is related to periods of increased system load and appears to occur more frequently during certain peak usage hours. Our teams remain actively engaged in the investigation, and we will share further updates as soon as we have more information to provide. Jul <var data-var='date'>24</var>, <var data-var='time'>11:13</var> UTC Investigating - We are currently investigating an issue affecting the Elements Security Center and Broad Context Detections. Customers may encounter an error when attempting to change the status of a Broad Context Detection under: Events → Broad Context Detections The following error message may be displayed: Failed to update Broad Context Detection! Example: Broad Context Detection Details, TX-ID: 0000-xxxxxxxxxxx Failed to update Broad Context Detection! Our teams are actively investigating the issue and working to identify the root cause. We will provide further updates as soon as more information becomes available.

Error when updating Broad Context Detection Status in Elements Security Center

Jul <var data-var='date'>20</var>, <var data-var='time'>08:17</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>20</var>, <var data-var='time'>07:27</var> UTC Monitoring - A fix has now been implemented and we are monitoring the results. Jul <var data-var='date'>20</var>, <var data-var='time'>06:57</var> UTC Identified - The issue has been identified and a fix is being implemented. Jul <var data-var='date'>20</var>, <var data-var='time'>06:53</var> UTC Investigating - We're aware of an issue affecting the Firewall settings view in Elements Security Center. Under "WithSecure firewall profiles," existing firewall profiles are not being displayed — the list appears empty, and related tables may show blank or missing rows. We've identified that the firewall profile data isn't being returned correctly to the interface, which is why existing profiles fail to load. Our team is actively working on a fix and validating it in our staging environment before rolling it out to production. We understand this may affect your ability to review or manage firewall profiles, and we appreciate your patience while we work to restore full functionality as quickly as possible. We'll share another update as soon as the fix is verified and rolled out.

Firewall module in Elements profile is empty in the portal

Jun <var data-var='date'>24</var>, <var data-var='time'>07:11</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>17</var>, <var data-var='time'>12:57</var> UTC Monitoring - A solution has been implemented and the service is recovering. We expect a full recovery within the next 24 hours without any action required from Elements administrators. We will continue to monitor the situation closely. Jun <var data-var='date'>17</var>, <var data-var='time'>08:25</var> UTC Investigating - Currently Elements profiles are not being assigned to Endpoint Protection clients in a timely manner. Profile assignments remain in Pending or Update in progress state for extended periods (several hours) preventing administrators from applying profile updates efficiently. Also affected are operations triggered from Elements Portal. The issue impacts European instances of Elements portal We are working on a solution with the highest priority.

Elements profiles are not assigned timely to Endpoint Protection clients

Jun <var data-var='date'>23</var>, <var data-var='time'>02:12</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'> 5</var>, <var data-var='time'>00:36</var> UTC Identified - A temporary fix has been deployed. On some localized pages, the English support page may still be displayed. In the meantime, partners and users can refer to the available content and switch the language manually in certain sections, such as the User Guide. We will continue working on a full resolution as a high priority. Jun <var data-var='date'> 4</var>, <var data-var='time'>10:34</var> UTC Investigating - We have identified an issue where support page is not accessible from withsecure.com corporate page. We are working on a solution with the highest priority. Direct access to English support page https://support.withsecure.com/ is working.

Support page is not accessible from withsecure.com corporate page

Jun <var data-var='date'> 7</var>, <var data-var='time'>20:00</var> UTC Completed - The scheduled maintenance has been completed. Jun <var data-var='date'> 7</var>, <var data-var='time'>18:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'> 2</var>, <var data-var='time'>10:30</var> UTC Scheduled - On Sun 7th June 2026, 18:00 UTC we are planning to upgrade RBAC Access Control System database in the production WithSecure Elements environment. Access control system will be running in read-only mode for up to 2 hours: Changes in the Security Administrators view will not have any effect. All changes will be delayed and applied after upgrade has finished Access Control View (participants of RBAC pilot only) will be available in read-only mode - any change in role assignments, users and security groups will not be possible Other parts and features or the Elements Security Center are not affected Security (cloud) services, agents (clients), and APIs are not affected during this maintenance break. We recommend that Users should plan and execute urgent access control changes prior to the upgrade window.

System Maintenance: Upgrade of RBAC Access Control System database

May <var data-var='date'>22</var>, <var data-var='time'>10:16</var> UTC Resolved - The issue has been resolved. May <var data-var='date'>21</var>, <var data-var='time'>09:14</var> UTC Identified - We have identified an issue where elevating recommendations in WithSecure Elements Exposure Management is failing with an error message. We are working on resolving the issue with the highest priority.

WithSecure Elements Exposure Management: Elevate not available

May <var data-var='date'>18</var>, <var data-var='time'>10:20</var> UTC Resolved - The issue has been resolved. The expiration of all affected orders have been corrected by us, no further action is needed. May <var data-var='date'>18</var>, <var data-var='time'>07:38</var> UTC Update - We are currently testing a fix for the issue. We will update this incident once the fix has been deployed. May <var data-var='date'>15</var>, <var data-var='time'>12:12</var> UTC Identified - We have identified an issue where amendments of Total Volume orders result in expiration of the license. As a WithSecure partner, this issue affects you if you use the Total Volume business model and amend an existing subscription, for example by increasing or decreasing the license amount. In this case, the license is incorrectly set to expire on the day of the order. We have identified and manually updated affected orders, so no further action is needed. We expect to resolve the issue by Monday, 18th of May and ask partners to not place amendment orders until we have resolved the issue.

Total Volume amendments result in expiration of the license

Apr <var data-var='date'>28</var>, <var data-var='time'>13:09</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>28</var>, <var data-var='time'>06:45</var> UTC Update - Placeholder recommendations have been removed. We continue working on removal of incorrect findings and their respective recommendations. Apr <var data-var='date'>27</var>, <var data-var='time'>14:09</var> UTC Identified - Incorrect asset placeholders have been removed for all affected customers. We are updating findings and recommendations, and expect this work to finish by the morning of 28th of April, resolving the issue. Until then, we continue working on the issue with the highest priority. Apr <var data-var='date'>27</var>, <var data-var='time'>11:08</var> UTC Investigating - We are investigating an issue where WithSecure Elements Exposure management reports vulnerabilities, findings and recommendations for non-existent software or devices for some customers. These findings were generated after Saturday, 25th of April.

WithSecure Elements Exposure Management - incorrect findings after 25th of April

Apr <var data-var='date'>23</var>, <var data-var='time'>12:25</var> UTC Resolved - The issue has been resolved. You can submit URL samples again. Thank you for your patience! Apr <var data-var='date'>23</var>, <var data-var='time'>11:08</var> UTC Investigating - We are currently experiencing an issue were submitting URL samples in WithSecure Elements fails with an error "cannot create collaboration request". We are working on a solution with the highest priority.

WithSecure Elements URL sample submission outage

Apr <var data-var='date'>16</var>, <var data-var='time'>14:17</var> UTC Resolved - We have created a hotfix for this issue. We advise all our Business Suite partners and customers to apply this hotfix at the earliest opportunity. The risk can further be mitigated by ensuring that Policy Manager’s Web Reporting interface is not accessible from the internet. This can be done with external firewall configurations. The hotfix can be downloaded from the WithSecure Download Center: https://support.withsecure.com/en/support/download For more information on the Axios vulnerability (CVE-2026-40175) and WithSecure's response, please visit https://community.withsecure.com/announcements-en/kb/articles/32898-cve-2026-40175-for-axios-javascript-library Apr <var data-var='date'>14</var>, <var data-var='time'>14:35</var> UTC Investigating - We have identified that WithSecure Policy Manager (PM) includes a version of the Axios library within the web reporting component that is currently flagged as vulnerable. Based on our assessment, the associated risk is low. As a precautionary measure, we recommend the following: Reviewing the current firewall and network configuration to ensure that the Policy Manager webreporting interface is not accessible from external networks Ensuring restricted access to this component significantly reduces any potential exposure. We are investigating on a fix for the issue.

Axios vulnerability in Policy Manager Webreporting

Mar <var data-var='date'>23</var>, <var data-var='time'>09:05</var> UTC Resolved - This incident has been solved. Mar <var data-var='date'>23</var>, <var data-var='time'>05:34</var> UTC Investigating - We are investigating an issue with our "contact support" webform. Submissions do not reach our ticketing system and no error message is displayed. While we investigate the issue, we ask Partners to submit support requests through Partner Portal. Eligible customers can submit support requests through eService portal. In urgent matters, please give us a call. Our contact numbers and opening hours are listed here: https://support.withsecure.com/en/support/contact-support/call-support

Contact Support form not working

Mar <var data-var='date'> 5</var>, <var data-var='time'>13:58</var> UTC Resolved - We have published a hotfix that fixes the issue. The hotfix is automatically downloaded and applied, no action is required from administrators. Additional information for administrators: The Hotfix ID is 76, Description: Scanning platform initial state calculation and Firewall initial state Mar <var data-var='date'> 5</var>, <var data-var='time'>08:53</var> UTC Update - We continue testing the fix and hope to release it today, but no later than tomorrow (6th of March) Mar <var data-var='date'> 4</var>, <var data-var='time'>07:49</var> UTC Update - We have created a fix, which is currently in testing. We will notify, when the fix is released. Mar <var data-var='date'> 3</var>, <var data-var='time'>13:29</var> UTC Update - We continue working on a fix for the issue. Feb <var data-var='date'>27</var>, <var data-var='time'>13:13</var> UTC Identified - We have identified the issue and are working on a fix. Please note: this issue is cosmetic and clients/servers remain protected. Feb <var data-var='date'>26</var>, <var data-var='time'>13:43</var> UTC Investigating - We are investigating an issue where WithSecure Elements agent might show randomly that Malware Protection is disabled after reboot. We have confirmed that this issue is cosmetic and clients/servers remain protected. We are working on a fix.

WithSecure Elements might incorrectly show "Malware Protection disabled" after reboot

Feb <var data-var='date'>24</var>, <var data-var='time'>10:08</var> UTC Resolved - This incident has been resolved. Feb <var data-var='date'>24</var>, <var data-var='time'>04:19</var> UTC Monitoring - A fix has been deployed. We are monitoring this issue. Feb <var data-var='date'>24</var>, <var data-var='time'>03:56</var> UTC Investigating - We are investigating an issue with our "contact support" webform. Submissions do not reach our ticketing system and no error message is displayed. While we investigate the issue, we ask Partners to submit support requests through Partner Portal. Eligible customers can submit support requests through eService portal. In urgent matters, please give us a call. Our contact numbers and opening hours are listed here: https://support.withsecure.com/en/support/contact-support/call-support

Feb <var data-var='date'>10</var>, <var data-var='time'>07:00</var> UTC Resolved - The issue has been solved. Feb <var data-var='date'>10</var>, <var data-var='time'>06:49</var> UTC Identified - A mitigation was implemented. Checking the solution. Feb <var data-var='date'>10</var>, <var data-var='time'>03:44</var> UTC Investigating - Currently Provisioning API is returning "503 Back-end server is at capacity" error. Visible effects of this is that partners cannot issue new license/change subscription/get license information via Provisioning API.

Provisioning API is returning 503 Back-end server is at capacity error

Feb <var data-var='date'> 3</var>, <var data-var='time'>12:05</var> UTC Completed - The scheduled maintenance has been completed. Feb <var data-var='date'> 3</var>, <var data-var='time'>12:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jan <var data-var='date'>28</var>, <var data-var='time'>11:29</var> UTC Scheduled - We will be performing a small maintenance operation on WithSecure Elements Collaboration Protection on February 3rd, 2026 at 12.00 PM (UTC). This operation is expected to take a maximum of 5 minutes. During the maintenance, users may experience issues logging in to Collaboration Protection or temporary failures while browsing Collaboration Protection portal pages. There is no user action required during this maintenance period. User impact during maintenance: LOW

Minor Maintenance break: Elements Collaboration Protection - 3 February 2026

Feb <var data-var='date'> 2</var>, <var data-var='time'>12:44</var> UTC Resolved - This incident has been resolved. Feb <var data-var='date'> 2</var>, <var data-var='time'>10:47</var> UTC Investigating - We are investigating an issue where profiles in WithSecure Elements portal are shown incorrect settings and can not be saved. Endpoints are not affected, they remain on their existing profile.

WithSecure Elements portal: Profiles show incorrect settings and can not be saved

Jan <var data-var='date'>26</var>, <var data-var='time'>10:08</var> UTC Resolved - The issue has been resolved. If you have submitted a support request and have not received a reply from our system with a case number, your request has not reached us. We kindly ask you to submit your request again. We apologize for the inconvenience caused. Jan <var data-var='date'>26</var>, <var data-var='time'>10:05</var> UTC Monitoring - A fix has been implemented, and we are monitoring the result. Jan <var data-var='date'>26</var>, <var data-var='time'>06:20</var> UTC Investigating - We are investigating an issue with our "contact support" webform. Submissions do not reach our ticketing system and no error message is displayed. While we investigate the issue, we ask Partners to submit support requests through Partner Portal. Eligible customers can submit support requests through eService portal. In urgent matters, please give us a call. Our contact numbers and opening hours are listed here: https://support.withsecure.com/en/support/contact-support/call-support

Jan <var data-var='date'>21</var>, <var data-var='time'>15:31</var> UTC Resolved - The issue has been resolved. If you have submitted a support request and have not received a reply from our system with a case number, your request has not reached us. We kindly ask you to submit your request again. We apologize for the inconvenience caused. Jan <var data-var='date'>21</var>, <var data-var='time'>13:59</var> UTC Investigating - We are investigating an issue with our "contact support" webform. Submissions do not reach our ticketing system and no error message is displayed. While we investigate the issue, we ask Partners to submit support requests through Partner Portal. Eligible customers can submit support requests through eService portal. In urgent matters, please give us a call. Our contact numbers and opening hours are listed here: https://support.withsecure.com/en/support/contact-support/call-support

Jan <var data-var='date'>20</var>, <var data-var='time'>09:52</var> UTC Resolved - This incident has been resolved. Jan <var data-var='date'>19</var>, <var data-var='time'>19:26</var> UTC Monitoring - We have restored the service. You may see outdated information in WithSecure Elements Portal until all data has been updated. We estimate that all data has updated by 04:00 UTC. Jan <var data-var='date'>19</var>, <var data-var='time'>18:37</var> UTC Update - We are actively working on this issue and treating it as a top priority. Jan <var data-var='date'>19</var>, <var data-var='time'>16:17</var> UTC Update - We are continuously working on a fix for this issue. Jan <var data-var='date'>19</var>, <var data-var='time'>14:13</var> UTC Identified - We have identified further symptoms: - Newly registered devices do not appear in the WithSecure Elements Portal. - Removed devices reappear after page refresh. - Assigned or updated profiles do not go through to the devices - Operations sent from the WithSecure Elements Portal not going through to the clients - Unmanaged devices (WithSecure Exposure Management) are not shown or updated We continue working on the issue with the highest priority. Jan <var data-var='date'>19</var>, <var data-var='time'>13:45</var> UTC Investigating - We are investigating an issue where newly registered devices do not appear in WithSecure Elements portal. Further, newly assigned profiles, profile changes do not reach endpoints.

WithSecure Elements Portal: newly registered devices not appearing, profile changes not reaching endpoints

Dec <var data-var='date'>15</var>, <var data-var='time'>10:51</var> UTC Resolved - If you have submitted a support request between yesterday, 14th of December at 14:47 UTC and today, 15th of December 07:49 UTC and have not gotten an automated response with a case number, please submit your request again. We have not received it, and we are sadly unable to recover those. We apologize for the inconvenience. Dec <var data-var='date'>15</var>, <var data-var='time'>08:06</var> UTC Identified - We have recovered the functionality. You can submit new support cases through our webform again. We are investigating recovery options for submissions during the outage. Dec <var data-var='date'>15</var>, <var data-var='time'>07:47</var> UTC Investigating - We are investigating an issue, where using the contact Support webform is not generating Support cases. https://www2.withsecure.com/en/support/contact-support/email-support While we investigate the issue and recovery options, please use alternate means of contacting us. Partners: Please submit a case through Partner Portal Customers with Advanced or Premium Support subscriptions: Please submit a case through eService You can also reach us by phone. Our phone numbers and opening hours are listed here: https://www2.withsecure.com/en/support/contact-support/call-support

WithSecure contact Support webform not creating Support cases

Dec <var data-var='date'>11</var>, <var data-var='time'>12:30</var> UTC Resolved - The issue has been resolved. We no longer experience delays. No operations/data was lost. Dec <var data-var='date'>11</var>, <var data-var='time'>08:49</var> UTC Identified - We are experiencing intermittent delays in WithSecure Elements Endpoints and Countercept for Europe region, which may cause delays in remote operations such as network isolation. We are in the process of investigating the root cause and are working diligently to resolve the issue.

Elements Agent and Countercept experiencing delay to sync and execute remote operations.

Dec <var data-var='date'> 3</var>, <var data-var='time'>04:11</var> UTC Resolved - This issue has been resolved. Dec <var data-var='date'> 3</var>, <var data-var='time'>02:50</var> UTC Investigating - MS domain(aka.ms related domain) is blocked as harmful in Elements Collaboration Protection(ECP). Visible effects of this is that mail sending/receiving are blocked in ECP

MS domain(aka.ms) is blocked as harmful in ECP

Dec <var data-var='date'> 2</var>, <var data-var='time'>11:30</var> UTC Completed - The scheduled maintenance has been completed. Dec <var data-var='date'> 2</var>, <var data-var='time'>11:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Nov <var data-var='date'>27</var>, <var data-var='time'>08:57</var> UTC Scheduled - We will be performing a small maintenance operation on WithSecure Elements Exposure Management on December 2nd, 2025 at 11.00 AM (UTC). This operation is expected to take a maximum of 30 minutes. During the maintenance, there might be delays in accessing the data on Environment -> Network pages. Pages will be available again once maintenance is completed with reorganized Network Assets and Internet tabs. There is no user action required during this maintenance period. User impact during maintenance: LOW https://community.withsecure.com/en/kb/articles/32756-minor-maintenance-break-for-withsecure-exposure-management-2025-12-02

Maintenance break for WithSecure Exposure Management

Dec <var data-var='date'> 2</var>, <var data-var='time'>09:41</var> UTC Resolved - The issue has been resolved. Detections may still occur until the cache has expired. Instructions to clear the cache in WithSecure Elements Endpoint Protection can be found here: https://community.withsecure.com/en/kb/articles/29354-how-to-troubleshoot-security-cloud Dec <var data-var='date'> 2</var>, <var data-var='time'>08:12</var> UTC Investigating - We are investigating reports of Microsoft Teams- and calendar invitation links being falsely detected as malicious.

Is WithSecure services down?

WithSecure services status is UP

Lastest published events

Exposure Management (XM) Performance Degradation and Intermittent Errors

Error when updating Broad Context Detection Status in Elements Security Center

Firewall module in Elements profile is empty in the portal

WithSecure services Services, Components and Regions

Recent WithSecure services events

Exposure Management (XM) Performance Degradation and Intermittent Errors

Error when updating Broad Context Detection Status in Elements Security Center

Firewall module in Elements profile is empty in the portal

Elements profiles are not assigned timely to Endpoint Protection clients

Support page is not accessible from withsecure.com corporate page

System Maintenance: Upgrade of RBAC Access Control System database