WithSecure Outage History

WithSecure degraded · 1 active incident View live status →

WithSecure had 45 outages in the last 2 years totaling 989h 24m of downtime — averaging 1.8 incidents per month.

There were 45 WithSecure outages since February 18, 2025 totaling 989h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.withsecure.com

Critical September 25, 2025

WithSecure new Partner Portal ordering outage

Detected by Pingoru
Sep 25, 2025, 02:01 PM UTC
Resolved
Sep 25, 2025, 02:22 PM UTC
Duration
21m
Affected: Ordering
Timeline · 2 updates
  1. investigating Sep 25, 2025, 02:01 PM UTC

    We are currently investigating an issue where the quoting tool in the new WithSecure Partner Portal is not working. Therefore, no new orders can be placed. We are working on this issue with the highest priority and ask our partners to hold orders until the portal is restored. Please follow this incident for updates.

  2. resolved Sep 25, 2025, 02:22 PM UTC

    The issue has been resolved. New orders can be filed again. We apologize for the outage.

Read the full incident report →

Minor September 12, 2025

Elements Security Center doesn't respond properly when adding/deleting/managing devices, creating admin, showing devices, etc

Detected by Pingoru
Sep 12, 2025, 12:44 AM UTC
Resolved
Sep 12, 2025, 11:16 AM UTC
Duration
10h 32m
Affected: Portal
Timeline · 4 updates
  1. investigating Sep 12, 2025, 12:44 AM UTC

    Currently Elements Security Center doesn't respond properly when adding/deleting/managing devices, creating admin, showing devices, etc. A temporary fix was applied, however root cause is still under investigation. --Symptom 1 Installing EPP to new device, then the device won’t show up in Elements Security Center. --symptom 2 Existing devices are shown multiple n Elements Security Center. --Symptom 3 Register new license with admin user from Self-registration site(Or adding new admin user from existing company account in Elements Security Center), then the error is shown. Next Steps are to finding out the root cause for this issue. Products/Customers affected by this incident are Elements Security Center Admin/Users. Visible effects of this are instability device management in Elements Security Center

  2. investigating Sep 12, 2025, 03:20 AM UTC

    Updated configurations in backend as mitigation. The performance degradation is slowly improving after that. The investigation for root cause is still ongoing.

  3. investigating Sep 12, 2025, 03:49 AM UTC

    Mitigation action seems to be successful. Next step is investigating root cause in standard business hours and monitoring the situation 24/7.

  4. resolved Sep 12, 2025, 11:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 13, 2025

Submit Support Request from support pages not working

Detected by Pingoru
Aug 13, 2025, 08:01 AM UTC
Resolved
Aug 15, 2025, 07:28 AM UTC
Duration
1d 23h
Affected: Email Support Form
Timeline · 5 updates
  1. investigating Aug 13, 2025, 08:01 AM UTC

    We are currently investigating an issue where submitting a support request from our support pages does not work. There is no error message on the webform. If you have submitted a support request and have not received an automated response with a case number, you are affected. Partners: Please submit your support request from the Partner Portal Customers with advanced or premium support: Please submit your support request from the eService portal Other customers: Please submit your support request again, once the issue is resolved. In urgent cases, please give us a call. Our phone numbers and opening hours: https://www.withsecure.com/en/support/contact-support/call-support Login to Partner Portal and eService: https://www.withsecure.com/en/login

  2. identified Aug 13, 2025, 09:53 AM UTC

    We have identified and resolved the issue, new Support Requests created from our webform are again reaching us. When submitting a case, you will get an automatic response with a case number. https://www.withsecure.com/en/support/contact-support/email-support We are currently investigating recovery options for submitted Support Requests that did not reach us and will update this incident with more information, as it becomes available.

  3. monitoring Aug 14, 2025, 12:44 AM UTC

    The main issue has been solved. WithSecure support page can accept new support requests. Next Steps are to recover the dropped cases.

  4. identified Aug 14, 2025, 06:33 AM UTC

    We are currently investigating recovery options for submitted Support Requests that did not reach us and will update this incident with more information, as it becomes available.

  5. resolved Aug 15, 2025, 07:28 AM UTC

    If you have submitted a support request between Monday, 11th of August and Wednesday, 13th of August and have not received an automatic response with a support case ID, please contact us again. In urgent cases, please give us a call. We apologize for the inconvenience caused.

Read the full incident report →

Minor July 3, 2025

Cosmos in degraded state due to heavy queries

Detected by Pingoru
Jul 03, 2025, 10:01 AM UTC
Resolved
Jul 11, 2025, 11:59 AM UTC
Duration
8d 1h
Affected: PortalBusiness SuiteEndpoint Protection
Timeline · 3 updates
  1. investigating Jul 03, 2025, 10:01 AM UTC

    Cosmos is currently experiencing a degraded state due to high query volume, which may be causing delays in remote operations via PUSH. We are actively investigating the cause of the issue and will provide updates as soon as it's identified.

  2. monitoring Jul 04, 2025, 12:43 AM UTC

    The root cause has been identified and a fix has been applied. The situation is now back to normal. As of 12:00 UTC, Cosmos is still processing the backlog of PUSH notifications.

  3. resolved Jul 11, 2025, 11:59 AM UTC

    This incident is now resolved.

Read the full incident report →

Minor June 12, 2025

WithSecure Elements: Creation of Broad Context Detections delayed

Detected by Pingoru
Jun 12, 2025, 12:13 PM UTC
Resolved
Jun 12, 2025, 01:59 PM UTC
Duration
1h 45m
Affected: Endpoint Detection and Response
Timeline · 2 updates
  1. investigating Jun 12, 2025, 12:13 PM UTC

    We are investigating a delay in the creation of Broad Context Detections (BCD) in WithSecure Elements Endpoint Detection and Response. BCDs appear with a delay of up to 40 Minutes in the WithSecure Elements portal. We are working to reduce the delay with the highest priority.

  2. resolved Jun 12, 2025, 01:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 28, 2025

WithSecure Elements & WithSecure Business Suite remote operations delayed

Detected by Pingoru
May 28, 2025, 11:19 AM UTC
Resolved
May 28, 2025, 02:35 PM UTC
Duration
3h 15m
Affected: PortalBusiness SuiteEndpoint Protection
Timeline · 2 updates
  1. investigating May 28, 2025, 11:19 AM UTC

    We are investigating an issue where remote operations in WithSecure Elements Endpoint Protection, Endpoint Detection and Response, Managed Detection and Response as well as Business Suite Client Security and Server Security are executed with a delay. Push notifications from clients may also arrive with a delay to the WithSecure Elements portal.

  2. resolved May 28, 2025, 02:35 PM UTC

    The issue is now resolved as of 14:27 UTC

Read the full incident report →

Minor May 13, 2025

Elements Collaboration Protection Teams and Sharepoint connections

Detected by Pingoru
May 13, 2025, 11:35 AM UTC
Resolved
May 13, 2025, 02:55 PM UTC
Duration
3h 19m
Timeline · 2 updates
  1. investigating May 13, 2025, 11:35 AM UTC

    We are investigating an issue with WithSecure Elements Collaboration Protection. When a cloud connection is newly established or refreshed, despite the UI showing "connected", there will be no SharePoint sites or Teams Channel listed as protected. The Exchange functionality and One Drive are working as expected. We are working on resolving the issue.

  2. resolved May 13, 2025, 02:55 PM UTC

    We have found the root cause of the issue and a fix was done in production. However a refresh of permissions for sharepoint is required for Elements collaboration protection. The refresh can be completed with the following steps: 1: Logging in to the Elements security Center 2: Navigating to the Collaboration Protection section 3: Select Cloud Services from the left hand menu 4: From the Cloud Services pages select the Tenant an action menu will become visible and select "Refresh permissions to Sharepoint" a new permission consent will be requested, including all the necessary permissions This must be completed by all Elements Collaboration Protection users to maintain Sharepoint and Teams coverage.

Read the full incident report →

Minor May 8, 2025

Microsoft Sentinel connector is not receiving security event data from WithSecure Elements

Detected by Pingoru
May 08, 2025, 11:27 AM UTC
Resolved
May 15, 2025, 08:26 AM UTC
Duration
6d 20h
Affected: Portal
Timeline · 3 updates
  1. investigating May 08, 2025, 11:27 AM UTC

    We are currently investigating an issue where the Microsoft Sentinel connector is not receiving security event data from WithSecure Elements. Affected are all customers using the Sentinel connector.

  2. identified May 12, 2025, 12:24 PM UTC

    We are in the process of releasing a new version that resolves this issue. This version is currently pending Microsoft approval. In the meantime, you can manually upgrade the WithSecure Elements API connector for Microsoft Sentinel (deployed from Azure Marketplace) by following these steps: Login to Azure CLI az login Download the Fixed Version of the Connector App from: https://github.com/WithSecureOpenSource/elements-api/releases/download/1.0.1/connector.zip Run the Function App Deployment (Modify the MyResourceGroupName and MyFunctionAppName as needed): az functionapp deployment source config-zip --resource-group MyResourceGroupName --name MyFunctionAppName --src ./connector.zip

  3. resolved May 15, 2025, 08:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 23, 2025

WithSecure Elements Endpoint Detection and Response Linux sensor may stop running

Detected by Pingoru
Apr 23, 2025, 01:49 PM UTC
Resolved
Apr 28, 2025, 11:25 AM UTC
Duration
4d 21h
Affected: Endpoint Detection and Response
Timeline · 3 updates
  1. investigating Apr 23, 2025, 01:49 PM UTC

    We are investigating an issue where WithSecure Elements Endpoint Detection and Response Linux sensor as well as the response components may stop running after a reboot. Other platforms are not affected. To workaround the issue, execute the master-switch off command, followed by master-switch on on the affected host. This will restore full functionality on the host. We are working on resolving the issue for all affected hosts.

  2. identified Apr 25, 2025, 02:24 PM UTC

    We have released a fix for the issue to our Early Access program. We expect to release it to all clients early next week. We recommend assigning a small number of endpoints to participate in the Early Access program. Selected workstations and servers receive updates prior to the general availability. You can configure the Early Access in the profile in the WithSecure Elements Portal by navigating to - Security Configurations - Profiles - Linux - Edit profile - General - Early access to client software - Save and publish

  3. resolved Apr 28, 2025, 11:25 AM UTC

    We have published a fix today. This will be automatically taken into use and resolve the issue.

Read the full incident report →

Major April 17, 2025

WithSecure Exposure management findings inconsistent

Detected by Pingoru
Apr 17, 2025, 07:16 AM UTC
Resolved
Apr 22, 2025, 06:39 AM UTC
Duration
4d 23h
Timeline · 4 updates
  1. investigating Apr 17, 2025, 07:16 AM UTC

    We are investigating an issue where WithSecure Exposure Management findings for identities are inconsistent. The portal may falsely report "no issues found", hence previously visible recommendations related to Identities might be missing. Any new issues will continue to be detected and recommendations given for.

  2. identified Apr 17, 2025, 01:12 PM UTC

    We have identified the issue and are gradually restoring identity findings.

  3. monitoring Apr 18, 2025, 06:57 AM UTC

    The process of recreating the Identity findings was successfully completed overnight. Please note that the calculation process may take some time before the results are fully available.

  4. resolved Apr 22, 2025, 06:39 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 10, 2025

WithSecure Elements Endpoint Protection automated tasks do not start

Detected by Pingoru
Apr 10, 2025, 11:16 AM UTC
Resolved
Apr 14, 2025, 09:12 AM UTC
Duration
3d 21h
Affected: Endpoint Protection
Timeline · 3 updates
  1. investigating Apr 10, 2025, 11:16 AM UTC

    We are investigating an issue where WithSecure Elements Endpoint Protection automated tasks do not start. Affected platforms are Windows Client & Server as well as Mac. Symptoms are: Software Updater automatic installation does not work at all File scanning task, which is configured via Automated Tasks, does not start Shutdown, restart, and other automated tasks do not start 3 or more fshoster32.exe processes are running

  2. identified Apr 10, 2025, 01:36 PM UTC

    We have identified the issue and are working on a solution. We aim to publish a fix early next week (week from 14th of April).

  3. resolved Apr 14, 2025, 09:12 AM UTC

    We have published a fix to the issue. The fix is taken into use automatically, no administrator or user action is needed. If you wish, you can verify the installation in the WithSecure Elements portal under Environment - Devices - Computers. The latest installed hotfixed client version will show 25.1.85.0 If the hotfix version is not visible in the table, click "select columns" and search for "hotfix".

Read the full incident report →

Minor April 7, 2025

WithSecure Elements EDR - response action might fail when using portal in other language than English

Detected by Pingoru
Apr 07, 2025, 02:02 PM UTC
Resolved
Apr 08, 2025, 07:12 AM UTC
Duration
17h 10m
Timeline · 2 updates
  1. investigating Apr 07, 2025, 02:02 PM UTC

    We are investigating an issue were WithSecure Elements Endpoint Detection and Response (EDR) response actions might fail when using non-english portal localization. We recommend to switch to English if you encounter the issue until we have resolved it. We apologize for the inconvenience.

  2. resolved Apr 08, 2025, 07:12 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 6, 2025

Cannot log in to the Elements Security Center

Detected by Pingoru
Mar 06, 2025, 01:02 PM UTC
Resolved
Mar 06, 2025, 01:46 PM UTC
Duration
43m
Affected: Portal
Timeline · 3 updates
  1. investigating Mar 06, 2025, 01:02 PM UTC

    We are currently investigating an issue where logging in to WithSecure Elements security Center fails.

  2. monitoring Mar 06, 2025, 01:14 PM UTC

    The service has now been restored, logging in to Elements Security Center working correctly.

  3. resolved Mar 06, 2025, 01:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 5, 2025

WithSecure Elements Endpoint Protection profile editor for mobile profiles not saving changes

Detected by Pingoru
Mar 05, 2025, 10:02 AM UTC
Resolved
Mar 05, 2025, 01:12 PM UTC
Duration
3h 9m
Affected: Portal
Timeline · 3 updates
  1. investigating Mar 05, 2025, 10:02 AM UTC

    We are investigating reports that the WithSecure Elements Endpoint Protection profile editor for mobile profiles is not working correctly. Changes can not be saved.

  2. identified Mar 05, 2025, 12:47 PM UTC

    We have deployed changes that resolve the issue for all but one use case. Currently. when changing Allow custom DNS server(s) in End User Rights section, the profile can not be saved. We continue working on this with the highest priority.

  3. resolved Mar 05, 2025, 01:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 4, 2025

WithSecure Partner Portal ordering disruption

Detected by Pingoru
Mar 04, 2025, 01:08 PM UTC
Resolved
Mar 04, 2025, 02:40 PM UTC
Duration
1h 32m
Affected: Ordering
Timeline · 2 updates
  1. investigating Mar 04, 2025, 01:08 PM UTC

    We are investigating an issue where ordering is not available in WithSecure Partner Portal. We are asking our partners to follow this incident and file orders once the service is restored.

  2. resolved Mar 04, 2025, 02:40 PM UTC

    This incident has been resolved. Ordering functionality is restored. We apologize for the disruption.

Read the full incident report →

Critical February 28, 2025

WithSecure Elements Collaboration Protection outage

Detected by Pingoru
Feb 28, 2025, 12:51 PM UTC
Resolved
Feb 28, 2025, 01:43 PM UTC
Duration
52m
Affected: Collaboration Protection
Timeline · 2 updates
  1. investigating Feb 28, 2025, 12:51 PM UTC

    We are investigating a major outage of WithSecure Elements Collaboration Protection. We estimate that a significant portion of mailboxes are not protected. Also Sharepoint, OneDrive and Teams protection are partially affected. We work with the highest priority on this issue.

  2. resolved Feb 28, 2025, 01:43 PM UTC

    We have restored the service. The downtime lasted from 09:30 UTC to 13:15 UTC in which significant portion of content was not scanned.

Read the full incident report →

Major February 28, 2025

WithSecure Partner Portal ordering functionality partially unavailable

Detected by Pingoru
Feb 28, 2025, 09:53 AM UTC
Resolved
Feb 28, 2025, 10:55 AM UTC
Duration
1h 2m
Affected: Ordering
Timeline · 2 updates
  1. investigating Feb 28, 2025, 09:53 AM UTC

    We are investigating an issue where the ordering functionality in WithSecure Partner Portal is unavailable for some partners. We are working with the highest priority on restoring the functionality. Please refrain from submitting manual orders.

  2. resolved Feb 28, 2025, 10:55 AM UTC

    We apologize for an error in our recent communication regarding access to the Partner Portal Extension. Due to a technical issue, you received an email stating that you have been granted access to the Partner portal extension on Thursday 27.2. or Friday 28.2. Unfortunately, this message was sent to you by mistake, and you do not currently have access to the Partner Portal Extension. We sincerely apologize for any confusion or inconvenience this may have caused. Please rest assured that we are taking steps to prevent such errors in the future. Please be aware that some partners will receive a similar message over the weekend of 1st-2nd March and this message is correct.

Read the full incident report →

Minor February 21, 2025

Elements Exposure Management Identities view does not contain data after successful scan

Detected by Pingoru
Feb 21, 2025, 08:45 AM UTC
Resolved
Feb 21, 2025, 01:08 PM UTC
Duration
4h 23m
Timeline · 2 updates
  1. investigating Feb 21, 2025, 08:45 AM UTC

    The Identities view in Elements Exposure Management fails to display data after a successful scan for newly onboarded customers. The message displayed will be "No identities found."

  2. resolved Feb 21, 2025, 01:08 PM UTC

    Scan results may take 36 hours to populate and we are working on further improvements in the future, reducing (initial) scanning time. For more information, please visit https://community.withsecure.com/en/kb/articles/31640-after-onboarding-a-new-elements-exposure-management-customer-to-the-cloud-account-the-identities-view-in-the-elements-security-center-does-not-populate-data

Read the full incident report →

Notice February 19, 2025

Devices may not be visible in the WithSecure Elements Security Center despite devices being protected and licenses are taken into use

Detected by Pingoru
Feb 19, 2025, 02:04 PM UTC
Resolved
Feb 27, 2025, 07:29 AM UTC
Duration
7d 17h
Affected: Portal
Timeline · 4 updates
  1. investigating Feb 19, 2025, 02:04 PM UTC

    We are investigating an issue where some installed WithSecure Elements devices may not be visible in the Elements Security Center despite devices being protected and licenses are taken into use.

  2. investigating Feb 20, 2025, 02:27 PM UTC

    We have limited the impact to a small set of customers. Affected customers may experience also an TX-ID error when elevating a BCD from an affected device. In this case, please reach out to Technical Support with the BCD ID. https://www.withsecure.com/en/support/contact-support/call-support We continue working on this issue.

  3. identified Feb 24, 2025, 10:14 AM UTC

    We have resolved the issue for the vast majority of affected customers and devices and continue to work on the issue.

  4. resolved Feb 27, 2025, 07:29 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 18, 2025

WithSecure Elements Exposure Management network scans using cloud scan nodes remain at 0%

Detected by Pingoru
Feb 18, 2025, 01:51 PM UTC
Resolved
Feb 19, 2025, 08:20 AM UTC
Duration
18h 29m
Affected: Exposure Management
Timeline · 2 updates
  1. investigating Feb 18, 2025, 01:51 PM UTC

    We are investigating an issue where some WithSecure Elements Exposure Management network scans using cloud scan nodes remain at 0% even after sufficient wait time.

  2. resolved Feb 19, 2025, 08:20 AM UTC

    This incident has been resolved.

Read the full incident report →