Topdesk kesinti geçmişi

We are currently experiencing disruptions in one of our services. As a result logging in to your TOPdesk environment may not be possible. We are aware of the problem and are working on a solution. Our apologies for the inconvenience. At the time of writing this we are not able to give you an estimate on when your environment will be available. The next update will be provided as events warrant until the issue has been resolved. E-mail updates will be sent right away when the issue has been resolved. You can subscribe on the status page (https://status.topdesk.com) for additional updates. Log in is currently not working To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR26 06 6038.

We are currently investigating the cause of this issue. We will provide an update as soon as more information becomes available, and no later than 3 hours from now.

We have identified the issue and implemented a fix. You should now be able to log in to your TOPdesk environment as expected. If you are still experiencing login issues, please contact our support team and let us know. We will continue to closely monitor the situation to ensure the service remains stable.

Dear Customer, Over the weekend no further issues have been observed and all services have been operating normally. We therefor close the major. The root cause of this disruption has been identified and a Root Cause Analysis will be posted as soon as this becomes available. We sincerely apologize for any inconvenience this issue may have caused and appreciate your patience while we worked to resolve it. Kind regards, The TOPdesk Team

We are currently experiencing connectivity issues affecting our Delft office. As a result, myTOPdesk.com and our Support telephone line are currently unavailable. We are investigating the issue and working to restore these services as quickly as possible. We apologize for the inconvenience and will provide updates as more information becomes available.

The issue has been resolved, and all affected services are operating normally again. Thank you for your patience and understanding. If you have any questions, our Support team is happy to help.

We are currently experiencing disruptions with saving incident cards. It may occur that Incident cards that contain an empty action field cannot be saved. An error pops up stating to check the log files. To see if you are affected by this disruption, check if your Incident contains empty action fields, or check the logs for the following error: 'plainText is marked non-null but is null' Development has created a fix that will be introduced in version 16.06.007. A work around is also available for this bug. Work around: ⒈Locate the empty action field ⒉Delete it ⒊If deletion is not yet possible, fill the empty field and then delete or save the card. Our apologies for the inconvenience To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR26 06 1656.

Dear customer, The issue where some incidents with empty action fields cannot be saved has been fixed. The fix will be available in version 16.06.007 Due to the way the TOPdesk release cycle works, it will take some time before you'll notice the fix in your TOPdesk. We will try to keep you updated where possible.

Dear customer, The issue where some incidents with empty action fields cannot be saved has been fixed. The fix will be available in version 16.06.007 A work around is available for this bug. Work around: ⒈Locate the empty action fields of the progress trail. ⒉Fill the field with a dummy value ⒊Submit the correcte action field ⒋Delete the corrected action field ⒌Repeat if more action fields are affected ⒍Save the card The fix will be available in version 16.06.007 Our apologies for the inconvenience. At the time of writing the fix is part of our release cycle.  We cannot yet say when exactly the release will be available. Expected release is start of week 25.

Dear customer, The issue where some incidents with empty action fields cannot be saved has been fixed. The fixed version is 16.06.007 and has been released to all customer environments. This issue will be thoroughly evaluated to prevent these issues in the future. Our apologies for the inconvenience and thank you for you patience.

We are currently experiencing disruptions with incidents that cannot be saved due to empty images in the action field. We are aware of the problem and are working on a solution. Our apologies for the inconvenience. At the time of writing this we are not able to give you an estimate on when this will be solved. To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR26 06 2790.

We are currently experiencing disruptions with saving incident cards. It may occur that Incident cards that contain a "broken image" cannot be saved. An error pops up stating to check the log files. To see if you are affected by this disruption, check if your Incident contains action fields with "broken images" These images look like an empty box with gray border. The logs files state the following error: 'The given index must be of a Image token' The error was introduced in version 16.06.001 A work around is also available for this bug. Work around: ⒈Locate the broken images in the action fields ⒉Delete the broken images ⒊Save the card Development is actively investigating the issue and will produce a fix as soon as possible. Our apologies for the inconvenience

Dear customer, The issue where "broken images" in incidents action fields prevent you from saving the incident card has been fixed by development. The version for this fix has yet to be announced.  We expect this to be known tomorrow. Due to the way the TOPdesk release cycle works, it will take some time before you'll notice the fix in your TOPdesk. We will try to keep you updated where possible.

Dear customer, The issue where "broken images" in incidents action fields prevent you from saving the incident card has been fixed by development. The version for this fix is 16.06.008. A work around is available for this bug. Work around: ⒈Locate the broken images in the action fields of the progress trail. The broken image will look like a square box with a border around it. ⒉Delete the broken images ⒊Submit the correcte action field ⒋Repeat if more action fields are affected ⒌Save the card Our apologies for the inconvenience. At the time of writing the fix is part of our release cycle.  We cannot yet say when exactly the release will be available. Expected release is by the end of week 25.

Dear Customers, as communicated before, a fix for the not savable incidents issue has been released. Due to the TOPdesk release cycle, it took some time to ensure that all environments were updated to the required version. We are pleased to confirm that version 16.06.008 has now been deployed to all TOPdesk environments. This update resolves the issue that prevented operators from saving incidents that contain broken images. We sincerely apologize for any inconvenience this issue may have caused and appreciate your patience while we worked to resolve it. Kind regards, The TOPdesk Team

We are currently experiencing disruptions with access to my.topdesk.com Over the weekend (June 6th to 7th), we scheduled maintenance to update our AD FS and MiM systems. During this process, we encountered several issues that we have not yet resolved. We are actively working to restore access to My TOPdesk as swiftly as possible. Currently, login to My TOPdesk is temporarily unavailable If you would like to register an incident with support, please send an email to support@topdesk.com Our apologies for the inconvenience. At the time of writing this we are not able to give you an estimate on when My TOPdesk will be available. The next update will be provided as events warrant until the issue has been resolved. E-mail updates will be sent right away when the issue has been resolved. You can subscribe on the status page (https://status.topdesk.com) for additional updates.

The access to my.topdesk has been restored. The issues caused by the maintenance on the 6th-7th of June have been resolved. The cause will be evaluated to prevent similar issues in the future. We apologize again for any inconvenience and thank you for your patience.

TOPdesk environment unreachable for hosting location in Canada

We are currently investigation the cause of this outage. We will keep you updates every 30 minutes

We are continuing to investigate this issue.

We have identified an issue in the load balancer for the services cluster. We are working on resolving this issue.

All environments are accessible again. Root cause analysis will be published within a week.

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

This incident has been resolved.

The Azure-managed load balancer unexpectedly removed two port rules due to an azure internal issue in the integration between Kubernetes and Azure’s load balancer management. This resulted in a temporary loss of connectivity for our services. Adding the rules by hand resolved the issue. We are currently investigating how to prevent similar future outages.

We are currently experiencing disruptions with the Adobe PDF plugin version 26.5.2.0  Customers experience issues login in as an Operator. The page will infinitely buffer. Turning off the browser plugin/extension and restarting your browser will resolve the issue for now. We will investigate further and will update you on the fix. Our apologies for the inconvenience.  Please find the latest updates on our TOPdesk Status Page: https://status.topdesk.com To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR26 06 895.

Update: a workaround has been implemented, and the fix will be rolled out with the next release. The next version will usually be release within the next week.

The issue where Operators where unable to use TOPdesk who had the Adobe Extension active in Chrome, is tested and ready. Our fix will be introduced in TOPdesk version 16.06.004. When your TOPdesk has reached this version, you can turn the Extension on again in the Chrome Extension. Our apologies for the inconvenience.

Dear customers, As announced last week, the fix for the Adobe Plugin issue was announced. Due to the way the TOPdesk release cycle works, it will take some time before you'll notice the fix in your TOPdesk. Hopefully most/all update groups will have the correct version on Friday. We will try to keep you updated where possible.

Dear Customers, As communicated last week, a fix for the Adobe Plugin issue has been released. Due to the TOPdesk release cycle, it took some time to ensure that all environments were updated to the required version. We are pleased to confirm that version 16.06.004 has now been deployed to all TOPdesk environments. This update resolves the issue that prevented operators from logging in when the Adobe Plugin was enabled. You may now safely re-enable the Adobe Plugin. We sincerely apologize for any inconvenience this issue may have caused and appreciate your patience while we worked to resolve it. Kind regards, The TOPdesk Team

We are currently experiencing a disruption to the import service on EU1. We are aware of the problem and are working on a solution. Our apologies for the inconvenience. At the time of writing this we are not able to give you an estimate on when your environment will be available. The next update will be provided as events warrant until the issue has been resolved. E-mail updates will be sent right away when the issue has been resolved. You can subscribe on the status page (https://status.topdesk.com) for additional updates. To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR26 06 039.

We have restarted the import service and are seeing improvements in the performance. Imports can now executed again. We will continue to monitor the situation.

We have continued to monitor the import services following the reported issues and have not observed any further occurrences. Everything is operating as expected. As no additional problems have been identified, we will proceed with closing this major.

We are currently experiencing disruptions with our SSP. After clicking on a form in the SSP, the page appears white. Hitting ctrl+F5 (or Cmd + Shift + R for Mac) seems to help as a workaround. Our apologies for the inconvenience. At the time of writing this we are not able to give you an estimate on when your environment will be available. The next update will be provided as events warrant until the issue has been resolved. E-mail updates will be sent right away when the issue has been resolved. You can subscribe on the status page (https://status.topdesk.com) for additional updates. To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR26 04 5630.

Because the problem occurred after the last update, we decided to rollback the update again. Following this rollback, multiple customers have confirmed that the issue has been resolved. Based on this feedback, we are putting this major into monitoring time. If the problem does not recur, we will close the major at around 7 o'clock. At this time, the exact root cause has not yet been fully identified. Our team will continue to investigate to determine the underlying issue and prevent recurrence. Should you experience any further problems, please do not hesitate to contact us. A RCA will be published once ready

As no further issues arose during the monitoring period, we are hereby closing the major and all linked incidents. At this time, the exact root cause has not yet been fully identified. Our team will continue to investigate to determine the underlying issue and prevent recurrence. Should you experience any further problems, please do not hesitate to contact us. A RCA will be published once ready.

We are currently experiencing disruptions with logging in to My TOPdesk. We are aware of the problem and are working on a solution. Our apologies for the inconvenience. At the time of writing this we are not able to give you an estimate on when your environment will be available. The next update will be provided as events warrant until the issue has been resolved. E-mail updates will be sent right away when the issue has been resolved. You can subscribe on the status page (https://status.topdesk.com) for additional updates. To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR26 03 4191.

The issue has been identified and resolved. You can now log in to MyTOPdesk again. We are keeping a close eye on the situation. We apologise for the inconvenience.

The issue has been identified and resolved. You can now log in to MyTOPdesk again. We are keeping a close eye on the situation. We apologise for the inconvenience.

We are currently experiencing disruptions with one of our services. As a result, some or all of the knowledge items in the operator section won't display your written content but .json code. The SSP view seems to be not affected. Only early update groups are impacted. We are aware of the problem and are working on a solution. As a workaround, switching temporarily to the old knowledge base shows the content again. Please stay away from editing and saving knowledge items until the issue is resolved. Our apologies for the inconvenience. At the time of writing this, we are not able to give you an estimate on when your environment will be available. The next update will be provided as events warrant until the issue has been resolved. E-mail updates will be sent right away when the issue has been resolved. You can subscribe on the status page (https://status.topdesk.com) for additional updates. To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR26 01 5257.

We are still experiencing disruptions with one of our services. As a result, some or all of the knowledge items in the operator section won't display your written content but .json code. The SSP view seems to be not affected. Only early update groups are impacted. We will applied fixes to test environments of the early update groups and the applied fixes showed the desired result. To apply these fixes in your production environment, a restart is needed. The restarts will happen after 13:00 CET today. The estimated downtime for each environment is about 5 minutes. As a result of this fix the new knowledge base will be deactivated temporarily and can't be turned on until the underlying issue is resolved. We are also working on a permanent solution for this issue.  Please stay away from editing and saving knowledge items until the issue is resolved. Our apologies for the inconvenience. The current status can be found on our TOPdesk Status Page: https://status.topdesk.com

The major incident has been resolved. For the early update groups, both test and production environments, fixes have been applied and the knowledge base functionality has been restored. That being said, the underlying issue will be resolved in an upcoming TOPdesk version update in the near future. To guarantee stability, the fix won't be applied today; the knowledge base can be used, as you are used to, from now on again. If a rich-text field of a knowledge item was edited edited during the lifetime of this major, from the impacted usergroup, the edited content can't be recovered, even if the final fix is applied. Thank you for your patience.

We are currently experiencing multiple issues related to new rich text functionalities in the Knowledge Management module, specifically when images are included in knowledge items or news items. We are aware of the problem and are working on a solution. Our apologies for the inconvenience. The next update will be provided as events warrant until the issue has been resolved. E-mail updates will be sent right away when the issue has been resolved. You can subscribe on the status page (https://status.topdesk.com) for additional updates. To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR26 01 4577.

Research by our developers is still ongoing. A recent change in our code seems to be the likely cause. We will provide you with further information as soon as we have it.

Our developers are still researching the issue. We will provide you with further information as soon as we have it.

Our development department was able to create a solution for the problem. We have implemented this solution in all environments and have already received positive feedback. However, in order for the solution to work, all images in the affected knowledge articles must be re-uploaded. We apologise for any inconvenience caused.

We are currently experiencing disruptions at our EU1 hosting location, on specific containers. Please contact TOPdesk Support after submitting an incident, so we can store additional logfiles to investigate this. Our apologies for the inconvenience. At the time of writing this we are not able to give you an estimate on when your environment will be available. The current status can be found on our TOPdesk Status Page: https://status.topdesk.com To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR25 12 8094.

We are currently experiencing disruptions at our EU1 hosting location. The disruptions affecting only specific containers and currently have two different outcomes •Sloweness •Not beeing able to download attachements Please contact TOPdesk Support after submitting an incident, so we can store additional logfiles to investigate this. Our apologies for the inconvenience. At the time of writing this we are not able to give you an estimate on when your environment will be working properly again. The current status can be found on our TOPdesk Status Page: https://status.topdesk.com

We are currently experiencing disruptions at our EU1 hosting location. The disruptions affecting only specific containers and currently have the following outcomes •Sloweness •Not beeing able to download attachements •E-Mail Import fails Please contact TOPdesk Support after submitting an incident, so we can store additional logfiles to investigate this. Our apologies for the inconvenience. At the time of writing this we are not able to give you an estimate on when your environment will be working properly again. The current status can be found on our TOPdesk Status Page: https://status.topdesk.com

A fix has been implemented to affected containers; we will monitor the applied changes. It can take up to 15 minutes until the fix is propagated to all affected environments. Please contact TOPdesk Support after submitting an incident, so we can store additional logfiles to investigate this. Our apologies for the inconvenience. The current status can be found on our TOPdesk Status Page: https://status.topdesk.com

The major has been resolved. The applied fixes to specific containers in our EU1-datacenter resolved the following issues: •Slowness •Not being able to upload/download attachments •E-Mail import fails due to file server issues •Registering incidents by the SSP with attachements  Please check all your mail import folders and mail import connectors. It is likely that emails have been moved to your unsuccessful folder. Please move them to your inbox again, mark them as unread, and let the import run again. Thanks for your patience, and happy holidays.

The major has been resolved. The applied fixes to specific containers in our EU1-datacenter resolved the following issues: •Slowness •Not being able to upload/download attachments •E-Mail import fails due to file server issues •Registering incidents by the SSP with attachements  Please check all your mail import folders and mail import connectors. It is likely that emails have been moved to your unsuccessful folder. Please move them to your inbox again, mark them as unread, and let the import run again. Thanks for your patience, and happy holidays.

We are currently experiencing disruptions across multiple hosting locations. As a result, your TOPdesk environment may experience degraded performance or temporary unavailability. We are investigating the issue, which may be related to a disruption at an external service provider. For reference, Cloudflare’s service status can be found here: https://www.cloudflarestatus.com/ Please contact TOPdesk Support after submitting an incident, so we can store additional logfiles to investigate this. Our apologies for the inconvenience. At the time of writing this we are not able to give you an estimate on when your environment will be available. We aim to update this status page every 30 minutes until the issue has been resolved. E-mail updates will be sent when the issue has been resolved. You can subscribe on the status page (https://status.topdesk.com) for additional updates. To inform TOPdesk you are affected by this issue, please visit My TOPdesk .

Cloudflare has implemented a fix for the network performance issues and is monitoring the results. We are also monitoring the situation across our own TOPdesk environments and will provide further updates as they become available.

Cloudflare has closed their incident after confirming that network performance has been restored. We have not observed further impact on TOPdesk environments and have also received positive feedback from customers confirming service stability.

We are currently experiencing disruptions with Cloudflare We are aware of the problem and are working on a solution. Our apologies for the inconvenience. At the time of writing this we are not able to give you an estimate on when your environment will be available. The next update will be provided as events warrant until the issue has been resolved. E-mail updates will be sent right away when the issue has been resolved. You can subscribe on the status page (https://status.topdesk.com) for additional updates. To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR25 12 2484.

Cloudflare has introduced a fix. Environments should be back online  We will keep monitoring and wait for further messaging. Our apologies for the inconvenience.

Cloudflare has resolved the issue on their status page. We have received feedback that TOPdesk is working as expected. This Major incident will be closed since the issue is resolved. We'd like to apologies once more for the inconvenience and will communicate an RCA once it is received

A change made to how Cloudflare's Web Application Firewall parses incoming requests caused Cloudflare's network to be unavailable for several minutes this morning. This change was deployed by Cloudflare's team to help mitigate the industry-wide vulnerability disclosed this week in React Server Components. CloudFlare has issued a detailed statement on this matter here: [https://blog.cloudflare.com/5-december-2025-outage/](https://blog.cloudflare.com/5-december-2025-outage/)

We are currently experiencing disruptions regarding the Asset module and automated actions Automated actions for Asset management are failing. Fields related to ${(_linkAdded["assignment_persons"] and ${(_linkRemoved["assignment_persons"] are affected and no longer give a value. The error message can differ depending on what is being done in the step. Examples are:  {"errors":{"personTopDeskId":["The personTopDeskId field is required."]} {"errors":[{"errorCode":"parse_error","appliesTo":["id"],"errorMessage":"uuid has invalid length"}]} We are aware of the problem and are working on a solution. To help us troubleshoot this issue, please add the following information to your ticket when you are affected by this disruption: - The date and time of the last reproduction of this issue - The username of the user that reproduced this issue - A description of what the user was doing in TOPdesk - Browser activity and network traffic logs in a .HAR file, see KI 11015 on how to gather this information. Please contact TOPdesk Support after submitting an incident, so we can store additional logfiles to investigate this. Our apologies for the inconvenience. At the time of writing this we are not able to give you an estimate on when your environment will be available. The next update will be provided as events warrant until the issue has been resolved. E-mail updates will be sent right away when the issue has been resolved. You can subscribe on the status page (https://status.topdesk.com) for additional updates. To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR25 11 5294.

Dear Customers, We are investigating an issue affecting automated actions in the asset module. Fields related to 'assigned_persons' are affected and no longer return values, potentially breaking action sequences. This could cause issues assigning assets to persons, unassigning assets to persons or retrieving information about assets assigned to a person, using the API. We have been able to reproduce the steps for this behavior and are working actively to mitigate the issue. Please visit my.topdesk and indicate if you are affected in any way. Our apologies for the inconvenience. Please follow www.status.topdesk.com

Dear Customers, Our development team has rolled out a fix, resolving the issue affecting automated actions in the asset module. The solution does have an instant effect in your environments, and no further steps are needed to have this solved. Our apologies for the inconvenience. A Root Cause Analysis (RCA) will be posted on the TOPdesk status page once available.

Dear Customers, We are currently experiencing disruptions with the Self Service Portal. In some cases a white screen is shown for some users in some browsers. Please make sure that your browser version is updated to the most current version and try again. Follow KI 18761 - Blank/white pages in self service portal We have been unable to reproduce the issue on our side. To help us troubleshoot this issue, please add the following information to your ticket when you are affected by this disruption: •The date and time of the last reproduction of this issue •The username of the user that reproduced this issue •A description of what the user was doing in TOPdesk •Browser activity and network traffic logs in a .HAR file, see KI 11015 on how to gather this information. •Browser type and version •Any additional browser extensions/add-ons Please contact TOPdesk Support after submitting an incident, so we can store additional logfiles to investigate this. Our apologies for the inconvenience. Please follow www.status.topdesk.com To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR25 10 6447.

Dear Customers, We are still investigating the issue, We are currently experiencing disruptions with the Self Service Portal. In some cases a white screen is shown for some users in some browsers. Please make sure that your browser version is updated to the most current version and try again. Follow KI 18761 - Blank/white pages in self service portal We have been unable to reproduce the issue on our side. To help us troubleshoot this issue, please add the following information to your ticket when you are affected by this disruption: •The date and time of the last reproduction of this issue •The username of the user that reproduced this issue •A description of what the user was doing in TOPdesk •Browser activity and network traffic logs in a .HAR file, see KI 11015 on how to gather this information. •Browser type and version •Any additional browser extensions/add-ons Please contact TOPdesk Support after submitting an incident, so we can store additional logfiles to investigate this. Our apologies for the inconvenience. Please follow www.status.topdesk.com

Dear customers, We believe to have found the issue concerning the Self Service Portal not loading correctly. The issue seems to be in the language settings of the SSP.  Work-around: Switch your language settings to English, this should resolve the issue for now. We will research the issue and create a fix as soon as possible. Please let us know if the work around fixed this issue for now.

Dear customers, We believe to have found the issue concerning the Self Service Portal not loading correctly. The issue seems to be in the language settings of the browser. Work-around: Switch your browser language settings to English, this should resolve the issue for now. We will research the issue and create a fix as soon as possible. Please let us know if the work around fixed this issue for now.

Dear Customers. Our developers identified a bug in an update to the SSP that we deployed yesterday. This bug causes a 'white screen' if your browser language is set to certain specific languages.  We are trying to deploy a fix, hopefully withing the next hour.

Dear Customers, Our development team has rolled out a fix for the bug that prevented the Self Service Portal from loading successfully. Refreshing or reopening your browser should now allow the page to load as expected. Changing the browser language will no longer be necessary. If the SSP still will not load and show a white screen, please let us know through you registered incidents, so our Support department can have a look. Our apologies for the inconvenience.

The issue where the Self Service Portal would not load for customers with certain browser language settings has been resolved. Development has implemented the fix. The error occurred in the code that solved a different issue for customers using older systems/browsers that did not support Chrome 122 and up. Once the bug was found, development quickly released a fix, solving the issue. They have also adjusted their way of working to prevent similar issues in the future. TOPdesk wants to apologize for the inconvenience.

We are currently experiencing a throttling of our email server in the UK2 datacenter, which may cause delays in sending outgoing emails.  This is caused by multiple customers not configuring their SPF record correctly to include spf.topdesk.net Our support team is actively contacting these customers to resolve the matter as quickly as possible. In the meantime, but also in general, we recommend using your own mail server for outgoing emails, rather than the TOPdesk mail server, to help ensure timely delivery. Thank you for your understanding and cooperation. To inform TOPdesk you are affected by this issue, please visit My TOPdesk .

We are continuing to investigate this issue.

The email delivery issue in our UK2 datacenter has been resolved, and the mail queue is back to normal levels. The issue was related to outgoing emails sent from custom domains without the necessary SPF record configuration. To prevent similar issues in the future and ensure timely delivery, we recommend configuring your SPF records to include spf.topdesk.net if you use the TOPdesk mail server. Alternatively, using your own mail server for outgoing emails is also advised. Thank you for your patience and cooperation.

On September 11, 2025, our UK2 datacenter experienced email delivery delays, due to multiple customers, including a high-volume one, missing the required SPF record. This misconfiguration led to our outgoing email server being throttled, resulting in minor delays for some customers. The issue was quickly resolved by our support team proactively reaching out to all customers without SPF records to recommend proper configuration and temporarily disabling mail functionality for the high-volume customer. To prevent recurrence, we advise all customers to use their own mail server for outgoing email or to ensure correct SPF configuration.

We are currently experiencing disruptions with the mailimport . This is a problem we see on all our data centers. As result you may find that mail imports wil not work anymore.  We are aware of the problem and are working on solving the problem. Our apologies for the inconvenience. At the time of writing this we are not able to give you an estimate on when this issue is solved. The next update will be provided as events warrant until the issue has been resolved. E-mail updates will be sent right away when the issue has been resolved. You can subscribe on the status page (https://status.topdesk.com) for additional updates. To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR25 09 2081.

We are pleased to let you know that the cause of the issue has been identified. A fix was directly made and rolled out. The imports should be working as normal again.  We will monitor this major for a few hours more. If the issue remains resolved, we will close the Major around 17.00 hrs CEST. We apologize again for the inconvenience and thank you for your patience.

As communicated earlier this afternoon, we will now close the major. The disruptions that you have experienced today were caused by a dependency update of a library used in the mail import. This caused connections to Microsoft Exchange servers to fail. This was resolved by downgrading the version of the library. To prevent further issues, the problematic update will not be applied. We apologize again for the inconvenience and thank you for your patience.

We are currently experiencing disruptions with the EU1 hosting location. As a result your TOPdesk environment may not be available. We are aware of the problem and are working on a solution. Our apologies for the inconvenience. At the time of writing this we are not able to give you an estimate on when your environment will be available. The next update will be provided as events warrant until the issue has been resolved. E-mail updates will be sent right away when the issue has been resolved. You can subscribe on the status page (https://status.topdesk.com) for additional updates. To inform TOPdesk you are affected by this issue, please visit https://my.topdesk.com/tas/public/ssp/ . Please refer to incident TDR25 08 4429.

Our engineers are investigating networking issues in the EU1 hosting location. We have opened a support ticket with Microsoft. While some customers can access their environments again, our monitoring still indicates ongoing problems.

Mail import and file uploads may be affected by this major disruption. Some systems have been restarted, and overall system health is improving.

All customer environments, including mail import and file uploads, are now operational. We will continue monitoring the situation and plan to close the incident after successful verification. A root cause analysis (RCA) will be completed and published on the status page. Customers still experiencing issues should contact support.

The EU1 hosting disruption has been resolved. All environments are operating normally, and no further issues have been detected. An RCA will be published once the investigation is complete.

The major incident was caused by intermittent connection issues between the Kubernetes Service Cluster and the TOPdesk application. These connectivity problems led to disrupted access for customer environments, affecting critical services such as file uploads and mail import. Investigation revealed that the underlying issue originated from unstable communication with the application server, specifically related to the handling of temporary data. Although a restart of the affected components resolved the problem, we have identified the need to improve our monitoring. Going forward, we will enhance our monitoring to detect any issues related to temporary data sooner and minimize customer impact.