Topdesk 中断历史

1. 2026年7月21日 UTC 14:02monitoring

   Topdesk在Topdesk接口内引入了产品内部指导——短路走通,工具提示,以及偶尔的反馈提示,帮助用户发现特性并从Topdesk获得更多的价值. 本指导通过用户驾驶员公司提供的平台提供. 请注意,与可选添加产品不同,这个指导层适用于所有TOPdesk SaaS环境;它不是一个单独的订阅. 这改变对你的数据意味着什么? 为了提供这一指导,用户驾驶员代表Topdesk处理一组有限的数据: 相互作用元数据——无论是看到、完成、取消还是跳过一个指导要素。 有限的一套用户标识符——使用后,同样的指向不会被反复显示给同一个用户. 此数据为假名. 它不包括您Topdesk环境中的任何内容——没有门票,没有客户记录,也没有您输入到Topdesk的个人数据. 由于用户驾驶员代表TOPdesk处理限制个人数据(用户识别器),因此用户驾驶员作为可适用数据保护法定义的子处理器,包括GDPR,英国GDPR,和巴西通用数据保护法(LGPD). 用户驾驶员处理的与Topdesk有关的数据在欧洲联盟内部、特别是在位于法国的服务器上储存和处理,供所有客户使用,无论客户在哪里。 只有经授权的人员才能使用。 对于欧盟以外的客户,这意味着您的用户驾驶员相关数据是在欧盟而不是在您所在区域处理的. 为了正确提供指导,Userpilot使用IP地址来确定最终用户的国家;这些IP地址不是永久存储,一旦处理就被丢弃. 这些数据在中途和休息时被加密,并受《数据处理协定》管辖,该协定根据适用的数据保护法提供了适当的保障。 这一变化于8月21日生效。 详情和背景资料,见My Topdesk知识项目:KI 19347. 如果您对更改有任何异议,请在30天内回复Topdesk Support:[email protected]或https://my.topdesk.com。 我们的支助小组也愿意听取关于这一变化的任何其他问题或意见.

2. 2026年7月21日 UTC 14:04monitoring

   隐私 QQA: Topdesk 中的用户驾驶员 什么是用户驾驶员? 用户驾驶是允许Topdesk直接在Topdesk接口内显示产品内引导的工具——诸如登机行走,工具提示和短反馈提示等. 它被Topdesk用来帮助客户从产品中获得更多的价值. 用户驾驶员可以访问我们的数据吗? 没有 用户驾驶员无法访问存储在您的 Topdesk 环境中的任何东西 。 它不能看到你的门票,你的客户记录,你的个人数据, 或任何内容 你的组织已经输入到Topdesk。 用户驾驶员收集什么数据? 只有用户驾驶程序 : 交互元数据——无论是用户参与,解职,还是完成一个指导元素(如走行道或工具提示). 用户元数据——Topdesk发送的有限一组标识符,因此同一指向不会被反复显示给同一个用户. 此数据为假名: 不包括姓名、 电子邮件地址或您 Topdesk 环境中的任何内容 。 由于它涉及有限的用户识别特征,因此在GDPR下被作为个人数据处理并相应处理. 数据储存和处理在何处? 用户驾驶员处理的与Topdesk有关的所有数据都储存和处理在欧洲联盟内部,特别是存放在位于法国的服务器上,供所有客户使用,而不论客户在哪里。 为了正确提供指导,Userpilot使用IP地址来确定最终用户的国家;这些IP地址不是永久存储,一旦处理就被丢弃. 用户驾驶员是否是我们与Topdesk的数据处理协议下的子处理器? 对 用户驾驶器已被添加为子处理器 。 客户通过单独的正式子处理器通知(公布于我们的SaaS状态网页)得知这一情况,该通知规定了所需细节和您在规定期限内提出异议的权利。 本附件是一份参考文件,并非正式通知。 是否与用户驾驶员签订了数据处理协议? 是的,Topdesk和用户驾驶员之间有一项数据处理协议。 协议本身在各方之间是保密的,所以我们无法分享一份副本——但我们高兴地回答关于你的数据如何处理和保护的问题. 我们可以选择退出,还是要求删除我们的数据? 根据GDPR("删除权"第17条),个人可以要求删除其个人数据——例如,当不再有必要或已经撤回同意时. 为了行使这一权利,在下面的地址与我们联系,我们将处理请求。 这与您反对增加Userpic作为子处理器的权利是分开的,它包含在正式子处理器通知程序和相关反对期中. 我们能与谁接触进一步的问题? 关于这一变动的一般性问题或评论,请联系Topdesk Support:[email protected]或https://my.topdesk.com。 有关隐私或数据保护的特定问题,您可通过隐私@topdesk.com直接与我们的隐私团队联系.

自动翻译自官方事件更新。

1. 2026年7月14日 UTC 08:18investigating

   目前,我们的Topdesk门户网站的登录中断。 我们意识到这一问题,并正在寻求解决办法。 我们为不便而道歉。 在撰写本报告时,我们无法估计您何时可进入环境。 在问题得到解决之前,将根据情况需要提供下一次最新情况。 问题解决后,将立即发送电子邮件更新。 您可以在状态页面(https://status.topdesk.com)上订阅附加更新. 请访问https://my.topdesk.com/tas/public/ssp/.。 请参见事件TDR26 07 3573.

2. 2026年7月14日 UTC 10:03investigating

   我们想向你介绍调查的最新进展。 此时,我们的工程师仍在调查这个问题,还没有能够解决这个问题。 如果可以分享解决方案的消息,我们将在3小时或更早的时间内再次向您发送最新消息.

3. 2026年7月14日 UTC 11:29investigating

   我们正在继续调查这一问题.

4. 2026年7月14日 UTC 12:07monitoring

   我们高兴地通知你,我们已经解决问题了,你应该能够再次登录MyTop桌面。 我们今天下午将密切监测局势,以确保服务保持稳定。 如果保持稳定,我们将在17: 00CET关闭少校.

5. 2026年7月14日 UTC 15:25resolved

   经过监测,我们得出结论,解决办法是稳定的,因此我们将结束这一重大事件。 我们对所造成的不便表示诚挚的歉意并感谢你的耐心和理解.

自动翻译自官方事件更新。

1. 2026年7月2日 UTC 09:03investigating

   我们目前正在经历影响欧盟1国客户的中断,造成业绩问题。 因此,您的桌面环境可能缓慢或暂时无法使用 。 我们意识到这一问题,并正在寻求解决办法。 我们为不便而道歉。 在编写本报告时,我们无法估计何时将恢复正常服务。 我们的目标是每30分钟更新这一状况网页,直到这个问题得到解决。 问题解决后,将发送电子邮件更新。 您可以在状态页面(https://status.topdesk.com)上订阅附加更新. 请访问我的Topdesk.

2. 2026年7月2日 UTC 11:42monitoring

   我们查明了这一问题,并采取行动来减轻这一根源。 EU1co3现已恢复全面运行状态,没有任何性能问题 我们将继续密切监测局势,以确保服务保持稳定.

3. 2026年7月2日 UTC 18:57resolved

   此时,欧盟1co3已完全恢复运行状态,没有任何性能问题,我们将关闭这个主要项目.

自动翻译自官方事件更新。

1. 2026年6月25日 UTC 15:31investigating

   我们的CA1数据中心目前遇到问题。 因此您的桌面环境可能无法使用 。 我们意识到这一问题,并正在寻求解决办法。 我们为不便而道歉。 在撰写本报告时,我们无法估计您何时可进入环境。 在问题得到解决之前,将根据情况需要提供下一次最新情况。 问题解决后,将立即发送电子邮件更新。 您可以在状态页面(https://status.topdesk.com)上订阅附加更新. 请访问https://my.topdesk.com/tas/public/ssp/.。 请参看TDR26 06 8482事件.

2. 2026年6月25日 UTC 16:03resolved

   这个问题已经解决,所有情况都应能够再次达到。 一旦对此事进行了内部评估,我们将立即公布一份RCA。 我们为不便而道歉.

3. 2026年6月26日 UTC 15:46postmortem

   作为计划改善加拿大环境的基础设施的一部分,在例行服务更新过程中无意中采用了先前推迟的配置变化。 由于这一变化取决于尚未在加拿大环境中部署的基础设施,客户流量无法正确路由,导致服务中断。 一旦问题确定,配置变化立即回滚,恢复正常服务. 我们还更新了部署程序,以防止今后无意地采用被推迟的配置变化.

自动翻译自官方事件更新。

1. 2026年6月19日 UTC 06:11investigating

   我们的其中一项服务目前受到干扰。 因此无法登录到您的桌面环境 。 我们意识到这一问题,并正在寻求解决办法。 我们为不便而道歉。 在撰写本报告时,我们无法估计您何时可进入环境。 在问题得到解决之前,将根据情况需要提供下一次最新情况。 问题解决后,将立即发送电子邮件更新。 您可以在状态页面(https://status.topdesk.com)上订阅附加更新. 登录当前不工作 请访问https://my.topdesk.com/tas/public/ssp/.。 请参见"TDR26"06 6038事件.

2. 2026年6月19日 UTC 07:14investigating

   我们目前正在调查这一问题的原因。 一旦获得更多信息,我们将立即提供最新情况,最晚不超过3小时.

3. 2026年6月19日 UTC 07:48monitoring

   我们已查明了这一问题,并落实了一项解决办法。 您现在应该能够按预期登录您的 Topdesk 环境 。 如果你们仍然遇到登录问题,请联系我们的支援小组并通知我们。 我们将继续密切监测局势,以确保服务保持稳定.

4. 2026年6月22日 UTC 07:37resolved

   亲爱的客户 周末没有看到其他问题,所有服务都正常运行。 因此,我们关闭了少校。 已查明造成这种干扰的根本原因,一旦得到《根源分析》,将立即公布。 我们对该问题在我们努力解决这一问题时可能造成的任何不便表示诚挚的歉意并赞赏你的耐心。 敬请 服务台小组

5. 2026年6月24日 UTC 13:43postmortem

   ** Root 原因分析:** 在计划服务路线迁移期间,错过了一项服务所需的配置更新。 因此,这项服务的交通路线不正确。 由于其他服务没有受到影响,而且总体配置似乎有效,现有的监测没有发现这一问题。 根源是配置更新过程中的人为错误. ‌ ** 预防措施:** 为了减少类似问题的风险,我们将对所有配置变化始终适用 " 四眼 " 原则,并引入强制性实施后核查步骤,以确保在认为变化完成之前正确应用所有预期更新.

自动翻译自官方事件更新。

1. 2026年6月10日 UTC 10:15investigating

   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.

2. 2026年6月10日 UTC 11:18resolved

   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.

1. 2026年6月10日 UTC 07:38investigating

   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.

2. 2026年6月10日 UTC 13:57investigating

   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.

3. 2026年6月11日 UTC 10:42investigating

   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.

4. 2026年6月19日 UTC 08:19resolved

   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.

1. 2026年6月9日 UTC 15:06investigating

   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.

2. 2026年6月10日 UTC 09:16investigating

   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

3. 2026年6月10日 UTC 13:59investigating

   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.

4. 2026年6月11日 UTC 12:38investigating

   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.

5. 2026年6月23日 UTC 13:26resolved

   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

1. 2026年6月8日 UTC 08:11investigating

   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 [email protected] 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.

2. 2026年6月9日 UTC 13:23resolved

   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.

1. 2026年6月6日 UTC 18:26investigating

   TOPdesk environment unreachable for hosting location in Canada

2. 2026年6月6日 UTC 18:28investigating

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

3. 2026年6月6日 UTC 19:51investigating

   We are continuing to investigate this issue.

4. 2026年6月6日 UTC 20:04investigating

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

5. 2026年6月6日 UTC 20:19investigating

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

6. 2026年6月6日 UTC 20:23monitoring

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

7. 2026年6月6日 UTC 20:23resolved

   This incident has been resolved.

8. 2026年6月12日 UTC 09:28postmortem

   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.

1. 2026年6月3日 UTC 06:53investigating

   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.

2. 2026年6月3日 UTC 11:42investigating

   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.

3. 2026年6月5日 UTC 07:54investigating

   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.

4. 2026年6月10日 UTC 14:01investigating

   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.

5. 2026年6月17日 UTC 07:56resolved

   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

1. 2026年6月1日 UTC 07:15investigating

   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.

2. 2026年6月1日 UTC 11:12monitoring

   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.

3. 2026年6月1日 UTC 12:12resolved

   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.

1. 2026年4月22日 UTC 09:55investigating

   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.

2. 2026年4月22日 UTC 12:45monitoring

   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

3. 2026年4月23日 UTC 06:29resolved

   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.

1. 2026年3月16日 UTC 14:08investigating

   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.

2. 2026年3月16日 UTC 14:24monitoring

   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.

3. 2026年3月16日 UTC 18:09resolved

   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.

1. 2026年1月20日 UTC 09:58investigating

   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.

2. 2026年1月20日 UTC 11:28investigating

   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

3. 2026年1月20日 UTC 16:16resolved

   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.

1. 2026年1月16日 UTC 11:41investigating

   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.

2. 2026年1月16日 UTC 12:55investigating

   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.

3. 2026年1月16日 UTC 13:59investigating

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

4. 2026年1月16日 UTC 15:25resolved

   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.

1. 2025年12月24日 UTC 09:00investigating

   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.

2. 2025年12月24日 UTC 09:34investigating

   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

3. 2025年12月24日 UTC 10:38investigating

   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

4. 2025年12月24日 UTC 11:00investigating

   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

5. 2025年12月24日 UTC 12:34investigating

   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.

6. 2025年12月24日 UTC 12:34resolved

   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.

1. 2025年12月19日 UTC 12:26investigating

   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 .

2. 2025年12月19日 UTC 12:42monitoring

   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.

3. 2025年12月19日 UTC 14:28resolved

   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.

1. 2025年12月5日 UTC 09:09investigating

   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.

2. 2025年12月5日 UTC 09:16monitoring

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

3. 2025年12月5日 UTC 09:43resolved

   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

4. 2025年12月19日 UTC 14:59postmortem

   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/)

1. 2025年11月20日 UTC 10:14investigating

   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.

2. 2025年11月20日 UTC 10:19investigating

   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

3. 2025年11月20日 UTC 12:08resolved

   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.