Topdesk kesinti geçmişi

1. 21 Temmuz 2026 14:02 UTCmonitoring

   TOPdesk, TOPdesk arayüzünde ürün rehberliğinde tanıtıldı - kısa yürüyüşler, alettipler ve kullanıcıların özelliklerini keşfetmelerine ve TOPdesk'tan daha fazla değer elde etmelerine yardımcı olan geri bildirimler. Bu rehberlik, Kullanıcıpilot, Inc tarafından sağlanan bir platform aracılığıyla teslim edilir. Lütfen, opsiyonel ek-on ürünlerinin aksine, bu rehberlik katmanı tüm TOPdesk SaaS ortamları için geçerlidir; ayrı bir abonelik değildir. Bu değişiklik sizin verileriniz için ne anlama geliyor? Bu rehberliği sunmak için, Kullanıcı pilotu, TOPdesk adına sınırlı bir veri kümesine sahiptir: Interaction metadata - rehberlik elemanının görüldüğü, tamamlanmış, reddedilir veya atılır. Sınırlı bir kullanıcı tanımlayıcıları seti - bu yüzden aynı kılavuz tekrar aynı kullanıcıya gösterilmez. Bu veriler sahtedir. TOPdesk çevrenizden herhangi bir içerik içermiyor - bilet yok, müşteri kayıtları yok ve TOPdesk'a girdiğiniz kişisel veriler yok. Kullanıcı pilotu, TOPdesk adına sınırlı kişisel verilerle (kullanıcı tanımlayıcılar) sınırlı olduğundan, Kullanıcı pilotu GDPR, Birleşik Krallık GDPR ve Brezilya Genel Data Protection Law (LGPD) de dahil olmak üzere, geçerli bir veri koruma yasaları altında tanımlanır. Kullanıcı pilotu tarafından TOPdesk ile bağlantılı olarak yapılan veriler Avrupa Birliği içinde depolanır ve işlenir - özellikle Fransa'da bulunan sunucularda - müşterinin nerede bulunduğuna bakılmaksızın. Sadece yetkili personel için erişilebilir. AB dışında bulunan müşteriler için, bu, Kullanıcı pilotla ilgili verilerin kendi bölgenizde olduğu gibi AB'de işlendiği anlamına gelir. rehberliği doğru şekilde sunmak için, Kullanıcı pilotu son kullanıcının ülkeyi belirlemek için IP adreslerini kullanır; bu IP adresleri kalıcı olarak depolanmaz ve bir kez işlenir. Bu veriler transit ve geri kalanında şifrelenir ve geçerli veri koruma yasasına uygun olarak uygun koruma sağlayan bir Veri İşleme Anlaşması ile kaplıdır. Bu değişiklik 21 Ağustos'ta yürürlüğe girer. Daha fazla ayrıntı ve arka plan bilgisi için, My TOPdesk Knowledge Item: KI 19347 Bu değişiklikle ilgili herhangi bir itirazınız varsa, lütfen TOPdesk Desteğine 30 gün içinde cevap verin: [email protected] veya https://my.topdesk.com. Destek ekibimiz bu değişiklikle ilgili başka herhangi bir soru veya açıklama için de mevcuttur.

2. 21 Temmuz 2026 14:04 UTCmonitoring

   Privacy Q&A: Kullanıcı pilotu TOPdesk Kullanıcı pilotu nedir? Kullanıcı pilotu, TOPdesk'un ürün rehberliğinde göstermesine izin veren bir araçtır - yürüyüşleri, alettipleri ve kısa geri bildirimler gibi şeyler - doğrudan TOPdesk arayüzü içinde. Müşterilerin üründen daha fazla değer almasına yardımcı olmak için TOPdesk tarafından kullanılır. Kullanıcı pilotu verilerimize erişiyor mu? Hayır. Kullanıcı pilotu TOPdesk çevrenizde saklanan herhangi bir şeye erişmiyor. Biletlerinizi, müşteri kayıtlarını, kişisel verilerinizi veya kuruluşunuzun herhangi bir içeriği TOPdesk'e girebildi. Kullanıcı pilotu hangi verileri toplar? Kullanıcı pilot süreçleri sadece: Interaction metadata - bir kullanıcı ile meşgul olup, reddedilir veya bir rehberlik elemanı (örneğin bir yürüyüş veya araçtipi). Kullanıcı metadata - TOPdesk'in gönderdiği sınırlı sayıda tanımlayıcı, bu yüzden aynı kılavuz tekrar aynı kullanıcıya gösterilmez. Bu veriler sahtedir: isimleri, e-posta adreslerini veya TOPdesk çevrenizden herhangi bir içerik içermez. Çünkü sınırlı kullanıcı tanımlayıcıları içerir, GDPR altında kişisel veriler olarak tedavi edilir ve buna göre ele alınır. Veriler nerede depolanır ve işlenir? TOPdesk ile bağlantıdaki Kullanıcı pilotu tarafından yapılan tüm veriler Avrupa Birliği içinde depolanır ve işlenir - özellikle Fransa'da bulunan sunucularda - müşterinin bulunduğu her müşteri için. rehberliği doğru şekilde sunmak için, Kullanıcı pilotu son kullanıcının ülkeyi belirlemek için IP adreslerini kullanır; bu IP adresleri kalıcı olarak depolanmaz ve bir kez işlenir. Kullanıcı pilotu, TOPdesk ile veri işleme anlaşmamız altında bir alt işlemci midir? Evet. Kullanıcı pilotu bir alt işlemci olarak eklendi. Müşteriler bunu ayrı, resmi bir alt işleme veya bildirim yoluyla bilgilendirir (kolay durumu sayfasında yayınlanır), bu, gerekli ayrıntıları ve belirtilen süre içinde itiraz etme hakkını verir. Bu Q&A referans belgesidir ve bu resmi bildirimin kendisi değildir. Kullanıcı pilotu ile bir Data Processing Anlaşması (DPA) var mı? Evet, bir Veri İşleme Anlaşması, TOPdesk ve Userpilot arasında yer almaktadır. Anlaşmanın kendisi partiler arasında gizlidir, bu yüzden bir kopyasını paylaşamıyoruz - ancak verilerinizin nasıl işlendiği ve korunmasıyla ilgili soruları cevaplamaktan mutluluk duyuyoruz. Dışarı çıkabilir miyiz, yoksa verilerimizin silinmesini isteyebilir miyiz? GDPR'nin altında (Madde 17, “dönüm için doğru), bireyler kişisel verilerin silinmesini isteyebilir - örneğin, artık gerekli veya onay alınmadığı zaman. Bu doğruyu kullanmak için, aşağıdaki adreste bizimle iletişime geçin ve istekle çalışacağız. Bu, Kullanıcı pilotunun bir alt işlemeci olarak eklenmesine itiraz etme hakkınızdan ayrıdır, bu da resmi alt işleme veya bildirim prosedürü ve ilgili itiraz süresi ile kaplıdır. Kim daha fazla soru ile iletişim kurabiliriz? Bu değişiklik hakkında genel sorular veya açıklamalar için lütfen TOPdesk Desteğine ulaşın: [email protected] veya https://my.topdesk.com. Özellikle gizlilik veya veri koruması hakkında sorular için, [email protected]'da doğrudan gizlilik ekibimizle iletişime geçebilirsiniz.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 14 Temmuz 2026 08:18 UTCinvestigating

   Şu anda benim TOPdesk portalına giriş ile kesintiler yaşıyoruz. Sorundan haberdarız ve bir çözüm üzerinde çalışıyoruz. Apolojilerimiz rahatsızlık için. Bunu yazma zamanında, çevrenizin mevcut olduğunda size bir tahmin vermeyeceğiz. Bir sonraki güncelleme, konu çözülene kadar olay garantisi olarak verilecektir. E-posta güncelleştirmeleri, konu çözüldüğünde hemen gönderilir. Durum sayfasında (https://status.topdesk.com) ek güncellemeler için abone olabilirsiniz. TOPdesk'i bilgilendirmek için, lütfen https://my.topdesk.com/tas/public/ssp/ . Lütfen TDR26 07 3573 olayına atıfta bulun.

2. 14 Temmuz 2026 10:03 UTCinvestigating

   Size soruşturmanın ilerlemesini güncellemek istiyoruz. Bu anda mühendislerimiz hala sorunu araştırıyor ve henüz sorunu çözemediler. Size çözüm hakkında haberler paylaşılabilirse 3 saat içinde başka bir güncelleme göndereceğiz.

3. 14 Temmuz 2026 11:29 UTCinvestigating

   Bu konuyu araştırmaya devam ediyoruz.

4. 14 Temmuz 2026 12:07 UTCmonitoring

   Sorunları çözdüğümüzü size bildirmekten mutluluk duyuyoruz ve MyTOPdesk'a tekrar giriş yapmanız gerekir. Bu öğleden sonra hizmetin istikrarlı kalmasını sağlamak için durumu yakından izleyeceğiz. Eğer istikrarlı kalırsa, 17.00 hrs CET'de büyükleri kapatacağız.

5. 14 Temmuz 2026 15:25 UTCresolved

   İzlemeden sonra çözümün istikrarlı olduğu sonucuna vardık ve bu büyük olayı kapatacağız. Sabırınız ve anlayışınız için size olan rahatsızlıktan içtenlikle özür dileriz.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 2 Temmuz 2026 09:03 UTCinvestigating

   Şu anda AB1'de barındırılan müşterileri etkileyen rahatsızlıklar yaşıyoruz, performans sorunlarıyla sonuçlanıyoruz. Sonuç olarak, TOPdesk ortamınız yavaş veya geçici olarak kullanılamaz. Sorundan haberdarız ve bir çözüm üzerinde çalışıyoruz. Apolojilerimiz rahatsızlık için. Yazının zamanında, normal hizmet restore edildiğinde bir tahmin sağlamadık. Bu durumu çözinceye kadar her 30 dakikada güncellemeyi amaçlıyoruz. E-posta güncellemeleri, konu çözüldüğünde gönderilir. Durum sayfasında (https://status.topdesk.com) ek güncellemeler için abone olabilirsiniz. TOPdesk'i bilgilendirmek için, lütfen My TOPdesk'ı ziyaret edin.

2. 2 Temmuz 2026 11:42 UTCmonitoring

   Sorunu tespit ettik ve nedeni azaltmak için eylemleri yaptık. EU1co3 şimdi herhangi bir performans sorunları olmadan tam operasyonel duruma geri döndü Hizmetin istikrarlı kalmasını sağlamak için durumu yakından takip etmeye devam edeceğiz.

3. 2 Temmuz 2026 18:57 UTCresolved

   Bu zamanda AB1co3 artık herhangi bir performans sorunu olmadan tam operasyonel duruma geri döndü, bu büyükleri kapatacağız.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 25 Haziran 2026 15:31 UTCinvestigating

   Şu anda CA1 veri merkezimizde sorunlar yaşıyoruz. Sonuç olarak, TOPdesk ortamınız mevcut olmayabilir. Sorundan haberdarız ve bir çözüm üzerinde çalışıyoruz. Apolojilerimiz rahatsızlık için. Bunu yazma zamanında, çevrenizin mevcut olduğunda size bir tahmin vermeyeceğiz. Bir sonraki güncelleme, konu çözülene kadar olay garantisi olarak verilecektir. E-posta güncelleştirmeleri, konu çözüldüğünde hemen gönderilir. Durum sayfasında (https://status.topdesk.com) ek güncellemeler için abone olabilirsiniz. TOPdesk'i bilgilendirmek için, lütfen https://my.topdesk.com/tas/public/ssp/ . Lütfen TDR26 06 8482 olayına atıfta bulun.

2. 25 Haziran 2026 16:03 UTCresolved

   Sorun çözüldü ve tüm örnekler tekrar erişilebilir olmalıdır. Bu konu içsel olarak değerlendirilmiş olduğu sürece bir RCA yayınlayacağız. Hastalıklar için özürlerimiz.

3. 26 Haziran 2026 15:46 UTCpostmortem

   Kanada çevremize planlanan altyapı geliştirmelerinin bir parçası olarak, daha önce ertelenmiş bir yapılandırma değişikliği rutin hizmet güncellemesi sırasında geleneksel olarak uygulandı. Çünkü bu değişiklik henüz Kanada ortamında dağıtılmamış olan altyapıya bağımlıydı, müşteri trafiği doğru bir şekilde rotalanamadı ve hizmet kesintilerine yol açtı. Sorun tespit edildikten sonra, yapılandırma değişikliği hemen geri alındı, normal hizmeti geri restore etti. Ayrıca gelecekte geçici olarak uygulanmamasını engellemek için dağıtım sürecimizi güncelledik.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 19 Haziran 2026 06:11 UTCinvestigating

   Şu anda hizmetlerimizden birinde kesintiler yaşıyoruz. Sonuç olarak, TOPdesk ortamınıza giriş mümkün olmayabilir. Sorundan haberdarız ve bir çözüm üzerinde çalışıyoruz. Apolojilerimiz rahatsızlık için. Bunu yazma zamanında, çevrenizin mevcut olduğunda size bir tahmin vermeyeceğiz. Bir sonraki güncelleme, konu çözülene kadar olay garantisi olarak verilecektir. E-posta güncelleştirmeleri, konu çözüldüğünde hemen gönderilir. Durum sayfasında (https://status.topdesk.com) ek güncellemeler için abone olabilirsiniz. Log in şu anda çalışmıyor TOPdesk'i bilgilendirmek için, lütfen https://my.topdesk.com/tas/public/ssp/ . Lütfen TDR26 06 6038 olayına atıfta bulun.

2. 19 Haziran 2026 07:14 UTCinvestigating

   Şu anda bu sorunun nedenini araştırıyoruz. Daha kısa sürede daha fazla bilgi mevcut olacak şekilde bir güncelleme sağlayacağız ve bundan 3 saatten sonra yok.

3. 19 Haziran 2026 07:48 UTCmonitoring

   Sorunu tespit ettik ve bir düzeltme yaptık. Şimdi beklenen gibi TOPdesk ortamınıza kayıt olabilirsiniz. Hala giriş sorunları yaşıyorsanız lütfen destek ekibimizle iletişime geçin ve bize bildirin. Hizmetin istikrarlı kalmasını sağlamak için durumu yakından takip etmeye devam edeceğiz.

4. 22 Haziran 2026 07:37 UTCresolved

   Sevgili Müşteri, Hafta sonu boyunca daha fazla sorun gözlemlendi ve tüm hizmetler normalde çalışıyor. Büyükleri kapatmak için oradayız. Bu kesintinin kökü tespit edildi ve bir Kök Sebep Analizi bu mevcut olduğu kadar yakında yayınlanacak. Bu sorunun herhangi bir rahatsızlıktan içtenlikle özür dileriz ve bunu çözmeye çalışırken sabrınızı takdir edebilir. Saygılar, TOPdesk Ekibi

5. 24 Haziran 2026 13:43 UTCpostmortem

   **Root Cause Analizi:** Planlanan bir hizmet göçü sırasında, bir hizmet için gerekli bir konfigürasyon güncellemesi kaçırılmıştır. Sonuç olarak, bu hizmet için trafik yanlış yollandı. Çünkü diğer hizmetler etkilenmedi ve genel konfigürasyon geçerli görünüyordu, mevcut izleme sorunu tespit etmedi. Kök nedeni yapılandırma güncelleştirme sürecinde insan hatasıydı. **Proventive Measures:** Benzer konuların riskini azaltmak için, tüm konfigürasyon değişiklikleri için dört göz prensibini sürekli olarak uygulayacağız ve tüm planlanan güncellemelerin tam olarak değerlendirilmeden önce zorunlu bir doğrulama doğrulama doğrulama adımını tanıtacağız.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 10 Haziran 2026 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. 10 Haziran 2026 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. 10 Haziran 2026 07: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. 10 Haziran 2026 13: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. 11 Haziran 2026 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. 19 Haziran 2026 08: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. 9 Haziran 2026 15: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. 10 Haziran 2026 09: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. 10 Haziran 2026 13: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. 11 Haziran 2026 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. 23 Haziran 2026 13: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. 8 Haziran 2026 08: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. 9 Haziran 2026 13: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. 6 Haziran 2026 18:26 UTCinvestigating

   TOPdesk environment unreachable for hosting location in Canada

2. 6 Haziran 2026 18:28 UTCinvestigating

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

3. 6 Haziran 2026 19:51 UTCinvestigating

   We are continuing to investigate this issue.

4. 6 Haziran 2026 20:04 UTCinvestigating

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

5. 6 Haziran 2026 20:19 UTCinvestigating

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

6. 6 Haziran 2026 20:23 UTCmonitoring

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

7. 6 Haziran 2026 20:23 UTCresolved

   This incident has been resolved.

8. 12 Haziran 2026 09: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. 3 Haziran 2026 06: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. 3 Haziran 2026 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. 5 Haziran 2026 07: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. 10 Haziran 2026 14: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. 17 Haziran 2026 07: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. 1 Haziran 2026 07: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. 1 Haziran 2026 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. 1 Haziran 2026 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. 22 Nisan 2026 09: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. 22 Nisan 2026 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. 23 Nisan 2026 06: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. 16 Mart 2026 14: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. 16 Mart 2026 14: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. 16 Mart 2026 18: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. 20 Ocak 2026 09: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. 20 Ocak 2026 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. 20 Ocak 2026 16: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. 16 Ocak 2026 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. 16 Ocak 2026 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. 16 Ocak 2026 13:59 UTCinvestigating

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

4. 16 Ocak 2026 15: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. 24 Aralık 2025 09: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. 24 Aralık 2025 09: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. 24 Aralık 2025 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. 24 Aralık 2025 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. 24 Aralık 2025 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. 24 Aralık 2025 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. 19 Aralık 2025 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. 19 Aralık 2025 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. 19 Aralık 2025 14: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. 5 Aralık 2025 09: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. 5 Aralık 2025 09: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. 5 Aralık 2025 09: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. 19 Aralık 2025 14: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. 20 Kasım 2025 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. 20 Kasım 2025 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. 20 Kasım 2025 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.