Topdesk 장애 기록

1. 2026년 7월 21일 PM 2:02 UTCmonitoring

   TOPdesk는 TOPdesk 인터페이스 내의 제품 안내를 소개하고 있습니다. 짧은 워크루프, 툴팁 및 사용자의 기능을 발견하고 TOPdesk에서 더 많은 가치를 얻으십시오. 이 지도는 Userpilot, Inc.가 제공하는 플랫폼을 통해 전달됩니다. 옵션 애드온 제품과는 달리, 이 가이드 레이어는 모든 TOPdesk SaaS 환경에 적용됩니다. 별도의 구독이 아닙니다. 이 변경은 귀하의 데이터에 대해 의미합니까? 이 지도를 전달하기 위해 Userpilot은 TOPdesk의 대신 데이터 세트를 처리합니다. Interaction metadata - 지도 요소가 보일지 여부, 완료, 해고, 건너뛰기. 사용자 식별자의 제한 세트 - 같은 지침은 반복적으로 동일한 사용자에게 표시되지 않습니다. 이 데이터는 익명입니다. 그것은 당신의 TOPdesk 환경에서 어떤 내용이 포함되지 않습니다 - 티켓 없음, 고객 기록 없음, 그리고 당신이 TOPdesk에 입력 한 개인 데이터. Userpilot 프로세스는 GDPR, 영국 GDPR 및 브라질 일반 데이터 보호법 (LGPD)을 포함한 적용 가능한 데이터 보호법에 따라 정의된 하위 프로세스로 행동합니다. Topdesk와의 연결에서 Userpilot에 의해 처리 된 데이터는 유럽 연합 (EU) 내에서 저장되고 처리됩니다. 특히 France에 위치한 서버에서 고객에 상관없이 모든 고객을 위해 위치합니다. 인증된 인력만 이용할 수 있습니다. 유럽 연합 (EU) 외의 고객을 위해, 이것은 당신의 Userpilot 관련 자료가 유럽 연합 (EU)에서 처리됩니다. UXPA(사용자경험전문가협회)는 제품 및 서비스 UX를 리서치, 디자인, 평가하는 인력을 지원한다. 이 데이터는 해당 데이터 보호법에 따라 적절한 안전장치를 제공하는 Data Processing Agreement에 의해 해당됩니다. 이 변화는 8 월 21 일에 영향을받습니다. 자세한 내용 및 배경 정보, 내 TOPdesk 지식 항목 참조 : KI 19347 이 변경에 대한 모든 물체가있을 경우, Topdesk 지원으로 30 일 이내에 회신하십시오. [email protected] 또는 https://my.topdesk.com. 우리의 지원 팀은 또한 이 변화에 관하여 다른 질문 또는 말든지를 위해 유효합니다.

2. 2026년 7월 21일 PM 2:04 UTCmonitoring

   개인 정보 보호 Q & A : TOP 데스크에서 Userpilot Userpilot은 무엇입니까? Userpilot은 TOPdesk에서 제품 지도를 표시할 수 있게 해주는 도구입니다. - 온보드 워크루즈, 툴팁, 짧은 피드백 프롬프트와 같은 것들은 TOPdesk 인터페이스에서 직접 확인할 수 있습니다. Topdesk에 의해 사용되어 고객이 제품에 더 많은 가치를 얻을 수 있도록합니다. Userpilot은 데이터에 접근해야 합니까? 이름 * Userpilot은 TOPdesk 환경에 저장되지 않습니다. 귀하의 티켓, 고객 기록, 개인 데이터, 또는 귀하의 조직이 TOPdesk에 입력한 내용을 볼 수 없습니다. Userpilot은 어떤 데이터를 수집합니까? Userpilot 프로세스만: Interaction metadata - 사용자가 참여 여부, 해체, 또는 지침 요소를 완료 (예 : walkthrough or tooltip). User metadata - topdesk가 동일한 지시가 동일한 사용자에게 반복적으로 표시되지 않도록 식별자의 제한 세트. 이 데이터는 익명입니다: 그것은 이름, 이메일 주소, 또는 당신의 TOPdesk 환경에서 어떤 내용 포함하지 않습니다. 제한된 사용자 식별자가 포함되기 때문에 GDPR의 개인 데이터로 처리되며 이에 따라 처리됩니다. 저장된 데이터는 어디에 있습니까? Topdesk와의 연결에 Userpilot이 처리한 모든 데이터는 유럽 연합 (EU) 내에서 저장되고 처리됩니다. 프랑스에 위치한 서버에서 특히 고객이 어디에 있는지 여부에 관계없이 모든 고객을 위해. UXPA(사용자경험전문가협회)는 제품 및 서비스 UX를 리서치, 디자인, 평가하는 인력을 지원한다. Userpilot은 topdesk와 함께 데이터 처리 계약에 따라 하위 처리기를합니까? 예. Userpilot은 하위 프로세서로 추가되었습니다. 고객은 별도의 형식의 서브프로세서 알림(SaaS 상태 페이지에 게시)을 통해 이 정보를 알 수 있으며, 명시된 기간 내에 필요한 세부 사항과 목표를 설정할 수 있습니다. 이 Q&A는 참고 문서이고 형식적인 통보가 아닙니다. Data Processing Agreement (DPA)가 Userpilot과 함께 있습니까? 예, 데이터 처리 계약은 TOPdesk와 Userpilot 사이에 있습니다. 계약 자체는 당사자 간의 기밀이므로 사본을 공유 할 수 없습니다. 그러나 귀하의 데이터가 처리되고 보호되는 방법에 대한 질문에 대한 답변을 드리겠습니다. 우리는 옵트 아웃 할 수 있습니다, 또는 삭제 될 우리의 데이터를 요청? GDPR(Article 17, the "right to erasure")에 따라 개인은 더 이상 필요하다거나 동의가 철회되지 않은 경우 예를 들어 개인 데이터를 요청할 수 있습니다. 이 권리를 행사하려면 아래 주소로 문의하십시오. 우리는 요청을 처리 할 것입니다. 이 객체는 형식의 하위 처리기 알림 절차 및 관련 목표 기간에 의해 커버되는 하위 처리기로 Userpilot의 추가에 해당합니다. 궁금한 점이 있으신가요? 이 변경에 대한 일반적인 질문이나 말에 대해서는, TOPdesk Support: [email protected] 또는 https://my.topdesk.com으로 문의하시기 바랍니다. 개인 정보 보호 또는 데이터 보호에 대해 궁금한 점이 있으시면 [email protected]으로 문의하시기 바랍니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 14일 AM 8:18 UTCinvestigating

   현재 My TOPdesk 포털에 로그인하여 중단을 경험하고 있습니다. 우리는 문제의 aware이고 해결책에 일하고 있습니다. 불편을 드려 죄송합니다. 이 글을 쓰는 시점에서 우리는 당신의 환경을 사용할 때 견적을 제공 할 수 없습니다. 다음 업데이트는 문제가 해결 될 때까지 이벤트 보증으로 제공됩니다. E-mail 업데이트는 문제가 해결되었을 때 즉시 발송됩니다. 추가 업데이트에 대한 상태 페이지 (https://status.topdesk.com)에 가입할 수 있습니다. 이 문제점에 의해 영향을 받는 Topdesk를 알리려면 https://my.topdesk.com/tas/public/ssp/ 를 방문하십시오. TDR26 07 3573를 참조하시기 바랍니다.

2. 2026년 7월 14일 AM 10:03 UTCinvestigating

   우리는 조사의 진행 상황을 업데이트하고 싶습니다. 이 순간에 우리의 엔지니어는 아직도 문제점을 조사하고 문제점을 아직 해결할 수 없었습니다. 해결책에 관하여 뉴스가 공유될 수 있는 경우에 3 시간 안에 또 다른 갱신을 또는 이전 보낼 것입니다.

3. 2026년 7월 14일 AM 11:29 UTCinvestigating

   이 문제를 조사하고 있습니다.

4. 2026년 7월 14일 PM 12:07 UTCmonitoring

   우리는 우리가 문제를 해결하고 MyTOPdesk에 다시 로그인 할 수 있도록 알려 드리겠습니다. 우리는 서비스가 안정적으로 유지되도록이 오후를 밀접하게 상황을 모니터링 할 것입니다. 안정된 경우에, 우리는 17.00 hrs CET에 중요한 닫힐 것입니다.

5. 2026년 7월 14일 PM 3:25 UTCresolved

   모니터링 후 우리는 솔루션이 안정적이며, 우리는 따라서이 주요 사건을 닫을 것입니다. 우리는 진심으로 불편을 끼쳐 드려 죄송합니다. 당신의 인내와 이해에 감사드립니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 2일 AM 9:03 UTCinvestigating

   우리는 현재 EU1에서 호스팅 된 고객에 영향을 미치는 붕괴를 경험하고 있으며 성능 문제 발생. 결과적으로, 당신의 TOPdesk 환경은 느리거나 일시적으로 사용할 수 있습니다. 우리는 문제의 aware이고 해결책에 일하고 있습니다. 불편을 드려 죄송합니다. 쓰기의 시간에, 우리는 정상 서비스가 복원 될 때 견적을 제공 할 수 없습니다. 문제 해결까지 30 분마다이 상태 페이지를 업데이트하는 것을 목표로합니다. E-mail 업데이트는 문제가 해결되었을 때 발송됩니다. 추가 업데이트에 대한 상태 페이지 (https://status.topdesk.com)에 가입할 수 있습니다. 이 문제에 의해 영향을 받는 Topdesk를 알려주세요. My TOPdesk를 방문하십시오.

2. 2026년 7월 2일 AM 11:42 UTCmonitoring

   우리는 문제를 확인하고 원인을 완화하기 위해 작업을 만들었습니다. EU1co3는 이제 성능 문제없이 전체 운영 상태로 돌아갑니다. 우리는 서비스가 안정적으로 유지되도록 상황을 모니터링 할 것입니다.

3. 2026년 7월 2일 PM 6:57 UTCresolved

   이때 EU1co3는 이제 모든 성능 문제없이 전체 운영 상태로 돌아갑니다. 우리는이 중요한 것을 닫을 것입니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 25일 PM 3:31 UTCinvestigating

   현재 CA1 데이터 센터에 문제가 있습니다. TOPdesk 환경의 결과로 사용할 수 없습니다. 우리는 문제의 aware이고 해결책에 일하고 있습니다. 불편을 드려 죄송합니다. 이 글을 쓰는 시점에서 우리는 당신의 환경을 사용할 때 견적을 제공 할 수 없습니다. 다음 업데이트는 문제가 해결 될 때까지 이벤트 보증으로 제공됩니다. E-mail 업데이트는 문제가 해결되었을 때 즉시 발송됩니다. 추가 업데이트에 대한 상태 페이지 (https://status.topdesk.com)에 가입할 수 있습니다. 이 문제점에 의해 영향을 받는 Topdesk를 알리려면 https://my.topdesk.com/tas/public/ssp/ 를 방문하십시오. TDR26 06 8482 사건을 참고하십시오.

2. 2026년 6월 25일 PM 4:03 UTCresolved

   문제는 해결되고, 모든 인스턴스는 다시 도달해야합니다. 우리는 RCA를 내부적으로 평가 한대로 곧 게시합니다. 불편을 끼쳐 드려 죄송합니다.

3. 2026년 6월 26일 PM 3:46 UTCpostmortem

   캐나다 환경에 계획된 인프라 개선의 일환으로, 이전에 연기된 구성 변경은 일상적인 서비스 업데이트 중 적용되지 않았습니다. 이 변화가 캐나다 환경에서 배포되지 않은 인프라에 의존했기 때문에 고객 트래픽은 제대로 처리되지 않을 수 있으므로 서비스 중단으로 인한. 문제가 확인되면 구성 변경이 즉시 압연되었습니다. 정상적인 서비스. 우리는 또한 우리의 배포 프로세스를 업데이트하여 postponed 구성 변경에서 적용되지 않은 미래에.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 19일 AM 6:11 UTCinvestigating

   우리는 현재 우리의 서비스 중 하나에 혼란을 경험하고있다. 상단데스크 환경에 로그인하면 불가능할 수 있습니다. 우리는 문제의 aware이고 해결책에 일하고 있습니다. 불편을 드려 죄송합니다. 이 글을 쓰는 시점에서 우리는 당신의 환경을 사용할 때 견적을 제공 할 수 없습니다. 다음 업데이트는 문제가 해결 될 때까지 이벤트 보증으로 제공됩니다. E-mail 업데이트는 문제가 해결되었을 때 즉시 발송됩니다. 추가 업데이트에 대한 상태 페이지 (https://status.topdesk.com)에 가입할 수 있습니다. 로그인은 현재 작동하지 않습니다. 이 문제점에 의해 영향을 받는 Topdesk를 알리려면 https://my.topdesk.com/tas/public/ssp/ 를 방문하십시오. TDR26 06 6038 사건을 참고하십시오.

2. 2026년 6월 19일 AM 7:14 UTCinvestigating

   우리는 현재이 문제의 원인을 조사하고 있습니다. 우리는 더 많은 정보가 사용 가능한 한 빨리 업데이트를 제공 할 것이며, 지금부터 3 시간 이상.

3. 2026년 6월 19일 AM 7:48 UTCmonitoring

   우리는 문제를 확인하고 수정을 구현했습니다. TOPdesk 환경에 로그인할 수 있어야 합니다. 로그인 문제가 발생하면 지원팀에 연락하여 알려주세요. 우리는 서비스가 안정적으로 유지되도록 상황을 모니터링 할 것입니다.

4. 2026년 6월 22일 AM 7:37 UTCresolved

   고객 여러분, 주말에 더 이상 문제가 관찰되지 않았고 모든 서비스는 일반적으로 운영되었습니다. 우리는 주요 가까이에 있습니다. 이 붕괴의 뿌리 원인은 확인되었으며 루트 원인 분석은 곧이 사용 될 것으로 게시됩니다. 우리는 진심으로이 문제가 발생하고 우리가 그것을 해결하는 동안 당신의 인내심을 평가 할 수 있습니다 불편에 대해 사과합니다. 회사 소개 TOP 데스크 팀

5. 2026년 6월 24일 PM 1:43 UTCpostmortem

   ** 루트 원인 분석 : ** 계획된 서비스 이용 중, 1개의 서비스에 대한 필수 구성 업데이트가 놓았습니다. 결과적으로 해당 서비스의 트래픽은 잘못되었습니다. 다른 서비스가 비공개되지 않았기 때문에 전체 구성은 유효하지 않았기 때문에 기존의 모니터링은 문제가 발견되지 않았습니다. 루트 원인은 구성 업데이트 과정에서 인간의 오류였다. **Preventive 측정:** 이러한 문제의 위험을 줄이기 위해, 우리는 지속적으로 모든 구성 변경에 4 눈 원칙을 적용하고 변경이 완료되기 전에 모든 의도 된 업데이트가 올바르게 적용되었는지 확인하기 위해 필수 포스트 간단한 검증 단계를 소개합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 10일 AM 10:15 UTCinvestigating

   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일 AM 11:18 UTCresolved

   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일 AM 7:38 UTCinvestigating

   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일 PM 1:57 UTCinvestigating

   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일 AM 10:42 UTCinvestigating

   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일 AM 8:19 UTCresolved

   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일 PM 3:06 UTCinvestigating

   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일 AM 9:16 UTCinvestigating

   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일 PM 1:59 UTCinvestigating

   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일 PM 12:38 UTCinvestigating

   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일 PM 1:26 UTCresolved

   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일 AM 8:11 UTCinvestigating

   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일 PM 1:23 UTCresolved

   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일 PM 6:26 UTCinvestigating

   TOPdesk environment unreachable for hosting location in Canada

2. 2026년 6월 6일 PM 6:28 UTCinvestigating

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

3. 2026년 6월 6일 PM 7:51 UTCinvestigating

   We are continuing to investigate this issue.

4. 2026년 6월 6일 PM 8:04 UTCinvestigating

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

5. 2026년 6월 6일 PM 8:19 UTCinvestigating

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

6. 2026년 6월 6일 PM 8:23 UTCmonitoring

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

7. 2026년 6월 6일 PM 8:23 UTCresolved

   This incident has been resolved.

8. 2026년 6월 12일 AM 9:28 UTCpostmortem

   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일 AM 6:53 UTCinvestigating

   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일 AM 11:42 UTCinvestigating

   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일 AM 7:54 UTCinvestigating

   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일 PM 2:01 UTCinvestigating

   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일 AM 7:56 UTCresolved

   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일 AM 7:15 UTCinvestigating

   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일 AM 11:12 UTCmonitoring

   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일 PM 12:12 UTCresolved

   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일 AM 9:55 UTCinvestigating

   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일 PM 12:45 UTCmonitoring

   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일 AM 6:29 UTCresolved

   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일 PM 2:08 UTCinvestigating

   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일 PM 2:24 UTCmonitoring

   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일 PM 6:09 UTCresolved

   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일 AM 9:58 UTCinvestigating

   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일 AM 11:28 UTCinvestigating

   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일 PM 4:16 UTCresolved

   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일 AM 11:41 UTCinvestigating

   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일 PM 12:55 UTCinvestigating

   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일 PM 1:59 UTCinvestigating

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

4. 2026년 1월 16일 PM 3:25 UTCresolved

   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일 AM 9:00 UTCinvestigating

   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일 AM 9:34 UTCinvestigating

   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일 AM 10:38 UTCinvestigating

   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일 AM 11:00 UTCinvestigating

   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일 PM 12:34 UTCinvestigating

   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일 PM 12:34 UTCresolved

   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일 PM 12:26 UTCinvestigating

   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일 PM 12:42 UTCmonitoring

   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일 PM 2:28 UTCresolved

   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일 AM 9:09 UTCinvestigating

   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일 AM 9:16 UTCmonitoring

   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일 AM 9:43 UTCresolved

   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일 PM 2:59 UTCpostmortem

   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일 AM 10:14 UTCinvestigating

   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일 AM 10:19 UTCinvestigating

   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일 PM 12:08 UTCresolved

   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.