Dracoon kesinti geçmişi

1. 26 Ekim 2026 09:29 UTCinvestigating

   Şu anda e-posta bildirimlerimizle ilgili bir sorunu araştırıyoruz. Ekibimiz daha fazla bilgi toplamak ve sorunu mümkün olduğunca çabuk çözmek için çalışıyor. Bu herhangi bir rahatsızlıktan özür dileriz ve onlara sahip olduğumuz kadar yakında güncellemeler sağlayacaktır.

2. 26 Ekim 2026 11:31 UTCinvestigating

   Ekibimiz hala e-posta bildirimleri ile sorunu çözmeye çalışıyor. Şirketler belirli posta sunucu yapılandırmalarını kullanan bazı müşteriler şu anda DRACOON'dan e-posta bildirimleri almayabilir; bunu mümkün olduğunca çabuk çözmek için e-posta teslimat ortağımızla çalışıyoruz. Bu herhangi bir rahatsızlıktan özür dileriz ve sabrınızı takdir ederiz. Mevcut oldukları sürece daha fazla bilgi ve güncellemeler sağlayacaktır.

3. 26 Ekim 2026 15:38 UTCmonitoring

   E-posta bildirimleri ile sorunu tespit ettik ve bunu çözmek için bir düzeltme uyguladık. Durumu istikrarlı kalmasını ve ek sorunları tespit etmek için izliyoruz. Son birkaç günde, bazı alıcılar DRACOON'dan e-posta bildirimleri almamış olabilir. Çoğu zaman etkilenen şirketler, gelen postaları gelen postaları kabul etmeden önce belirli DNS kontrollerini içeren belirli kurumsal posta güvenlik ağ geçidi aracılığıyla çalışır. Kök nedeni, bildirim gönderileyici alanımızı etkileyen üçüncü taraf DNS meselesiydi. Bildirimler normal olarak tekrar teslim edilmelidir. Teslimatı yakından takip ediyoruz ve konu tamamen çözülecek bir güncelleme yayınlayacağız. Bu dönemde teslim edilmeyen bildirimler otomatik olarak kırılamaz. Bu rahatsızlıktan özür dileriz ve sabrınızı takdir edebilir.

4. 27 Ekim 2026 07:46 UTCresolved

   E-posta bildirimleri ile ilgili sorun tamamen çözülmüştür. Tüm sistemler artık normal olarak çalışıyor. Bu rahatsızlıktan özür dileriz ve sabrınızı takdir edebilir. Herhangi bir sorunu yaşamaya devam edersen lütfen destek ekibimize yardım için ulaşmaya tereddüt etmeyin.

5. 27 Ekim 2026 07:49 UTCpostmortem

   **20 - 26 Ekim 2026: Post-Mortem** 20 Ekim ve 26 Ekim arasındaki e-posta bildirimleri ile bir sorun yaşadık. Ekibimiz kök nedenini tanımlamak ve bir karar uygulamak için titizlikle çalıştı. Bu post-mortem'da, neler olduğunu, neden olduğunu ve gelecekte benzer olayları önlemek için ne yaptığımızı paylaşmak istiyoruz. ** Ne oldu?** Bu dönemde, bazı alıcılar DRACOON'dan e-posta bildirimleri almadılar. Sorun esas olarak, gelen posta belirli kurumsal e-posta güvenlik ağ geçitleri ile çalışan örgütleri etkiledi. Bu alıcılar için birçok bildirim reddedildi ve teslim edilmedi. Diğer tüm DRACOON işlevleri etkilenmedi. **Bu neden oldu? ** Bir postayı kabul etmeden önce, bazı e-posta güvenlik ağ geçidi, gönderileyicinin domainin geçerli olduğunu kontrol eder. Üçüncü taraf sağlayıcı tarafından işletilen bir DNS hizmeti, bildirim gönderileyici domainin konfigürasyonunun bir parçası için yanlış bir cevap vermeye başladı. Bu cevap nedeniyle, bu ağ geçitleri yanlışlıkla gönderen domaini geçersiz olarak tedavi etti ve bildirimleri reddetti. Kendi konfigürasyonumuz ve posta teslimat hizmetimiz sürekli çalışıyor. ** Ne yaptık?** İlk müşteri raporlarından sonra, teslimat oturumlarını e-posta teslimat ortağımızla birlikte analiz ettik ve reddedilmelerin net bir model takip ettiğini bulduk. Onları üçüncü taraf DNS sorununu takip ettik. 26 Ekim'de, bildirim gönderileyici alanımızın konfigürasyonunu değiştirdik, böylece artık etkilenen üçüncü taraf hizmete bağlı değil. Değişimden sonra teslimat normale döndü ve sorunu doğrulamak için yakından takip ettik. ** geliştirmek için ne yapabiliriz?** * E-posta ile ilgili konfigürasyonlarımızı dış hizmetlere bağımlılıkları ortadan kaldırmak için gözden geçiriyoruz. * E-posta teslimatını izlememizi geliştiriyoruz, bu yüzden alışılmadık reddedilme oranları tespit edildi ve daha önce araştırıldı. Bu olayın neden olabileceği herhangi bir rahatsızlıktan özür dileriz. Hizmetlerimizin istikrarı ve güvenilirliğini sağlamak için taahhüt ediyoruz ve gelecekte benzer olayları önlemek için proaktif önlemler almaya devam edeceğiz. Herhangi bir sorunuz veya endişeniz varsa lütfen destek ekibimize yardım için ulaşmaya tereddüt etmeyin.

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

1. 22 Ekim 2026 11:12 UTCresolved

   Son zamanlarda yayınlanan güvenlik açıklarından haberdarız CVE-2026-109618 ve CVE-2026-109619 PHP'yi etkiliyor. DRACOON bu açıklardan etkilenmez. Hiçbir eylem sizin tarafınızda gerekli değildir. Güvenlik danışmanlarını yakından takip etmeye devam ediyoruz ve size bu değerlendirme değişikliğinden haberdar olmaya devam edeceğiz.

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

1. 6 Ağustos 2026 09:54 UTCinvestigating

   We have identified an issue with uploads and downloads on DRACOON Cloud. Our engineers are working on a resolution and we are confident that we will have a fix in place soon. We will provide more information and updates as soon as they become available.

2. 6 Ağustos 2026 09:55 UTCresolved

   The issue with uploads and downloads on DRACOON Cloud has been fully resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and appreciate your patience. If you continue to experience any issues, please don't hesitate to reach out to our support team for assistance.

1. 16 Temmuz 2026 07:51 UTCresolved

   Veri merkezi sağlayıcımızın kullanılabilirlik sorunları sonucunda, DRACOON Cloud'un kısmi bir kesintisini yaşadık. Mühendislerimiz kısa vadeli sorunları bir iş etrafında uygulayarak çözebilirdi. Bu restore edilebilirlik ve tüm sistemler daha sonra normal olarak çalışıyorlardı. Bu rahatsızlıktan özür dileriz ve sabrınızı takdir edebilir. Herhangi bir sorunu yaşamaya devam edersen lütfen destek ekibimize yardım için ulaşmaya tereddüt etmeyin.

2. 16 Temmuz 2026 07:54 UTCpostmortem

   DRACOON Cloud ile 2026-07-16'da yaklaşık 00:05'den 00:30'a kadar bir sorun yaşadık. Ekibimiz kök nedenini tanımlamak ve bir karar uygulamak için titizlikle çalıştı. Bu post-mortem'da, neler olduğunu, neden olduğunu ve gelecekte benzer olayları önlemek için ne yaptığımızı paylaşmak istiyoruz. ** Ne oldu?** Veri merkezi sağlayıcımız bir bölgede ve kullanılabilirlik alanında deneyimli kullanılabilirlik sorunları yaşadı, DRACOON Bulut altyapısının nerede çalıştığı. Bunun sonucunda, DRACOON Cloud'un parçaları mevcut değildi veya olay sırasında bozuldu. ** Ne yaptık?** Mühendislerimiz durumu analiz etti ve mümkün olduğunca hızlı bir şekilde kullanılabilirliği tamamen restore etmek için teknik bir çalışma uyguladı. Bu olayın neden olabileceği herhangi bir rahatsızlıktan özür dileriz. Hizmetlerimizin istikrarı ve güvenilirliğini sağlamak için taahhüt ediyoruz ve gelecekte benzer olayları önlemek için proaktif önlemler almaya devam edeceğiz. Herhangi bir sorunuz veya endişeniz varsa lütfen destek ekibimize yardım için ulaşmaya tereddüt etmeyin.

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

1. 1 Temmuz 2026 09:32 UTCinvestigating

   Şu anda DRACOON ile bir sorunu araştırıyoruz. Ekibimiz daha fazla bilgi toplamak ve sorunu mümkün olduğunca çabuk çözmek için çalışıyor. Bu herhangi bir rahatsızlıktan özür dileriz ve onlara sahip olduğumuz kadar yakında güncellemeler sağlayacaktır.

2. 1 Temmuz 2026 10:11 UTCmonitoring

   DRACOON ile ilgili sorun çözüldü ve bunun istikrarlı kalmasını sağlamak için durumu izliyoruz. Bu rahatsızlıktan özür dileriz ve sabrınızı takdir edebilir.

3. 1 Temmuz 2026 10:26 UTCresolved

   DRACOON ile ilgili sorun tamamen çözülmüştür. Tüm sistemler artık normal olarak çalışıyor. Bu rahatsızlıktan özür dileriz ve sabrınızı takdir edebilir. Herhangi bir sorunu yaşamaya devam edersen lütfen destek ekibimize yardım için ulaşmaya tereddüt etmeyin.

4. 23 Eylül 2026 09:24 UTCpostmortem

   ** 1 Temmuz 2026, 11:20 - 12:30 CEST** - Post-Mortem 1 Temmuz 2026, yaklaşık 11:20 ve 12:15 CEST arasında, DRACOON Bulut geçici bir servis kesintisine neden olan bir sorun vardı. Ekibimiz kök nedenini tanımlamak ve yerinde bir karar koymak için çalıştı. Bu post-mortem'da, ne olduğunu açıklamak istiyoruz, neden oldu, bunu çözmek için ne yaptık ve gelecekte benzer olayları önlemek için ne yapacağız. ** Ne oldu?** Yaklaşık 55 dakika boyunca, DRACOON Cloud kullanıcıları için sadece kısmen mevcut değildi. Hizmeti restore ettikten sonra, platformu 12:30 CEST'e kadar tamamen istikrarlı olduğundan emin olmaya devam ettik. Hiçbir müşteri verileri kayboldu veya uzlaşmadı. **Bu neden oldu? ** İç platform altyapısımıza planlanan bir yapılandırma değişikliği yaptık. Değişimin amacı, çevremizin güvenliğini daha da güçlendirmekti. Bununla birlikte, değişim, DRACOON Cloud'un bazı iç bileşenleri arasında üretimde ve etkilenen iletişimde beklendiği gibi davranmadı. Bu, servis kesintisine neden oldu. ** Ne yaptık?** İzlememiz bizi probleme uyarmıştı ve mühendislerimiz hemen \(11:20 CEST\) araştırmaya başladı. Son yapılandırma değişikliğine geri dönük kesintiyi takip ettiler ve etkilenen bileşenler arasında normal iletişimi restore ettiler. DRACOON Cloud 12:15 CEST'de tekrar tamamen mevcuttu. Daha sonra platformu istikrarlı olduğunu ve olayı 12:30 CEST'de çözüldüğünü ilan ettik. ** geliştirmek için ne yapabiliriz?** * Sınıf yapılandırma değişiklikleri için pre-prodüksiyon testlerimizi genişleteceğiz, böylece gerçek üretim koşullarını daha iyi eşleştirecekler. * Bu tür değişiklikleri daha küçük, kademeli adımlarla atacağız, bu yüzden erken beklenmedik bir davranışı tespit edeceğiz. * Otomatik çeklerimizi bu gibi sorunları daha hızlı bulmak ve daha hızlı geri dönmemize izin vermek için geliştireceğiz. Bu olayın neden olabileceği herhangi bir rahatsızlıktan özür dileriz. Hizmetlerimizi istikrarlı ve güvenilir tutmak için taahhüt ediyoruz ve gelecekte benzer olayları önlemek için proaktif önlemler almaya devam edeceğiz. Herhangi bir sorunuz veya endişeniz varsa lütfen destek ekibimize yardım için ulaşmaya tereddüt etmeyin.

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

1. 16 Nisan 2026 15:58 UTCinvestigating

   We are currently investigating an issue with our Virus Protection feature. Our team is working to gather more information and resolve the issue as quickly as possible. We apologize for any inconvenience this may cause and will provide updates as soon as we have them.

2. 16 Nisan 2026 20:57 UTCresolved

   The issue with Virus Protection has been fully resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and appreciate your patience. If you continue to experience any issues, please don't hesitate to reach out to our support team for assistance.

1. 24 Mart 2026 08:48 UTCinvestigating

   We are currently investigating an issue with Web App. Our team is working to gather more information and resolve the issue as quickly as possible. We apologize for any inconvenience this may cause and will provide updates as soon as we have them.

2. 24 Mart 2026 08:51 UTCinvestigating

   We are continuing to investigate this issue.

3. 24 Mart 2026 09:42 UTCmonitoring

   The issue with Web App has been temporarily resolved, and we are monitoring the situation to ensure it remains stable. We apologize for any inconvenience this may have caused and appreciate your patience.

4. 25 Mart 2026 12:03 UTCresolved

   The issue with our Web App has been fully resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and appreciate your patience. If you continue to experience any issues, please don't hesitate to reach out to our support team for assistance.

5. 27 Mart 2026 10:28 UTCpostmortem

   We experienced an issue with our WebApp on 2026-03-24 from around 9:30 to 11:00 CET. Our team has worked diligently to identify the root cause and implement a resolution. In this post-mortem, we want to share the details of what happened, why it happened, what we did to resolve it, and what we will do to prevent similar incidents in the future. **What happened?** We experienced service instability caused by a bug in a third-party dependency. This resulted in intermittent errors and degraded performance of the Web App. **Why did this happen?** A bug in a third-party dependency caused unexpected errors in our Web App, leading to occasional crashes. This issue was triggered under specific conditions that were not caught in prior testing. **What did we do?** We resolved the issue temporarily by implementing a safeguard and later by properly solving the issue with this dependency. Stability was restored once the temporary fix was deployed, with full recovery at around 10:40 CET. **What can we do to improve?** We will expand our test coverage to better capture edge cases, ensuring that unusual or unexpected scenarios, especially those that lead to this incident, are identified and prevented before deployment. We apologize for any inconvenience this incident may have caused. We are committed to ensuring the stability and reliability of our services and will continue to take proactive measures to prevent similar incidents from happening in the future. If you have any questions or concerns, please don't hesitate to reach out to our support team for assistance.

1. 12 Ocak 2026 10:42 UTCresolved

   We have been experiencing issues with our DRACOON service from 11:00 to 11:40 on 2026-01-12. Our team was working to resolve the issue as quickly as possible. We apologize for any inconvenience this may have caused.

1. 8 Ocak 2026 10:42 UTCidentified

   We have identified an issue with DRACOON Cloud. Our engineers are working on a resolution and we are confident that we will have a fix in place soon. We will provide more information and updates as soon as they become available.

2. 8 Ocak 2026 10:43 UTCidentified

   We are continuing to work on a fix for this issue.

3. 8 Ocak 2026 10:44 UTCresolved

   The issue with DRACOON Cloud has been fully resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and appreciate your patience. If you continue to experience any issues, please don't hesitate to reach out to our support team for assistance.

1. 27 Kasım 2025 08:30 UTCinvestigating

   Our team is still actively working to resolve the issue with Virus Protection Scanning. We apologize for any inconvenience this may cause and appreciate your patience. We will provide more information and updates as soon as they become available.

2. 27 Kasım 2025 08:50 UTCidentified

   We have identified the issue with Virus Protection Scanning. Our engineers are working on a resolution and we are confident that we will have a fix in place soon. We will provide more information and updates as soon as they become available.

3. 27 Kasım 2025 12:34 UTCmonitoring

   The issue with Virus Protection Scanning has been resolved, and we are monitoring the situation to ensure it remains stable. We apologize for any inconvenience this may have caused and appreciate your patience.

4. 27 Kasım 2025 13:58 UTCresolved

   The issue with Virus Protection Scanning has been fully resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and appreciate your patience. If you continue to experience any issues, please don't hesitate to reach out to our support team for assistance.

1. 20 Kasım 2025 14:52 UTCresolved

   From 14:55 to 15:05 today, we experienced some issues and a partial outages of DRACOON Cloud. Our team quickly identified and resolved the issue. We apologize for any inconvenience this may have caused.

1. 19 Kasım 2025 08:42 UTCinvestigating

   We are currently investigating an issue with DRACOON Virus Protection. Our team is working to gather more information and resolve the issue as quickly as possible. We apologize for any inconvenience this may cause and will provide updates as soon as we have them.

2. 19 Kasım 2025 09:55 UTCidentified

   We have identified the issue with DRACOON Virus Protection. Our engineers are working on a resolution and we are confident that we will have a fix in place soon. We will provide more information and updates as soon as they become available.

3. 19 Kasım 2025 11:09 UTCmonitoring

   The issue with DRACOON Virus Protection has been resolved, all pending scans should be completed within the next few minutes. We are monitoring the situation to ensure it remains stable. We apologize for any inconvenience this may have caused and appreciate your patience.

4. 19 Kasım 2025 11:27 UTCresolved

   The issue with DRACOON Virus Protection has been fully resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and appreciate your patience. If you continue to experience any issues, please don't hesitate to reach out to our support team for assistance.

1. 13 Ağustos 2025 10:00 UTCidentified

   We have identified an issue with degraded performance of our virus protection feature for some customers. Our engineers are working on a resolution and we are confident that we will have a fix in place soon. We will provide more information and updates as soon as they become available.

2. 13 Ağustos 2025 13:45 UTCmonitoring

   The issue with degraded performance of our virus protection feature has been resolved, and we are monitoring the situation to ensure it remains stable. We apologize for any inconvenience this may have caused and appreciate your patience.

3. 13 Ağustos 2025 14:59 UTCresolved

   The issue with degraded performance of our virus protection feature has been fully resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and appreciate your patience. If you continue to experience any issues, please don't hesitate to reach out to our support team for assistance.

4. 2 Eylül 2025 11:28 UTCpostmortem

   We experienced an issue with our Virus Protection feature on 13.08.2025 at around 12:00 CEST. Our team has worked diligently to identify the root cause and implement a resolution. In this post-mortem, we want to share the details of what happened, why it happened, what we did to resolve it, and what we will do to prevent similar incidents in the future. **What happened?** At 12:00 CEST, monitoring alerted the team about increased latency in the Virus Protection service. Investigation revealed that unusually high load from a spike in file scanning requests overwhelmed the systems processing capacity, leading to degraded performance for a subset of customers. **Why did this happen?** The Virus Protection service was able to keep up with the increased load for scanning files, but the responses were not processed fast enough by another service, leading to missing/delayed verdicts for the files that had to be scanned. **What did we do?** The team manually scaled out the service to restore capacity. At 15:45, latency metrics returned to normal and the functionality was fully restored. **What can we do to improve?** We are investigating the root cause of the slow response processing and will reconfigure the service in question to make sure to eliminate the bottleneck. We apologize for any inconvenience this incident may have caused. We are committed to ensuring the stability and reliability of our services and will continue to take proactive measures to prevent similar incidents from happening in the future. If you have any questions or concerns, please don't hesitate to reach out to our support team for assistance.

1. 4 Ağustos 2025 06:58 UTCinvestigating

   We are currently investigating an issue with our Support Portal (Dracoon Server). Our team is working to gather more information and resolve the issue as quickly as possible. We apologize for any inconvenience this may cause and will provide updates as soon as we have them.

2. 4 Ağustos 2025 07:25 UTCresolved

   The issue with our Support Portal has been fully resolved. We apologize for any inconvenience this may have caused and appreciate your patience.

1. 28 Temmuz 2025 07:54 UTCinvestigating

   We are currently investigating an issue with our Support Portal. Our team is working to gather more information and resolve the issue as quickly as possible. We apologize for any inconvenience this may cause and will provide updates as soon as we have them.

2. 28 Temmuz 2025 10:58 UTCresolved

   The issue with our Support Portal has been fully resolved. We apologize for any inconvenience this may have caused and appreciate your patience.

1. 16 Temmuz 2025 07:31 UTCresolved

   There was an issue with DRACOON on 2025-07-12 from around 14:30 to 15:40. Our team worked to gather information and resolved the issue as quickly as possible. We apologize for any inconvenience this may have caused.

2. 9 Eylül 2025 14:59 UTCpostmortem

   We experienced an issue with DRACOON Cloud on 2025-07-12 from around 14:30 to 15:40. Our team has worked diligently to identify the root cause and implement a resolution. In this post-mortem, we want to share the details of what happened, why it happened, what we did to resolve it, and what we will do to prevent similar incidents in the future. What happened? DRACOON Cloud experienced performance degradation. Some users reported slow response times and connection timeouts during the incident window. Why did this happen? The incident was caused by increased load and scaling issues. A part of the system was unable to handle the traffic volume, leading to resource exhaustion and subsequent service degradation. What did we do? Our team immediately identified the scaling bottleneck and implemented emergency load balancing measures. We scaled up the infrastructure resources to restore normal service levels by 15:40. What can we do to improve? We will implement automated scaling policies to handle traffic spikes, enhance monitoring and alerting systems for early detection of load issues, and conduct regular capacity planning reviews to prevent similar incidents. We apologize for any inconvenience this incident may have caused. We are committed to ensuring the stability and reliability of our services and will continue to take proactive measures to prevent similar incidents from happening in the future. If you have any questions or concerns, please don't hesitate to reach out to our support team for assistance.

1. 7 Temmuz 2025 10:05 UTCinvestigating

   We are currently investigating an issue with DRACOON. Our team is working to gather more information and resolve the issue as quickly as possible. We apologize for any inconvenience this may cause and will provide updates as soon as we have them.

2. 7 Temmuz 2025 10:59 UTCmonitoring

   The issue with DRACOON has been resolved, and we are monitoring the situation to ensure it remains stable. We apologize for any inconvenience this may have caused and appreciate your patience.

3. 7 Temmuz 2025 11:10 UTCresolved

   The issue with DRACOON has been fully resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and appreciate your patience. If you continue to experience any issues, please don't hesitate to reach out to our support team for assistance.

4. 9 Eylül 2025 15:01 UTCpostmortem

   We experienced an issue with DRACOON Cloud on 2025-07-07 from around 12:00 to 13:00. Our team has worked diligently to identify the root cause and implement a resolution. In this post-mortem, we want to share the details of what happened, why it happened, what we did to resolve it, and what we will do to prevent similar incidents in the future. What happened? DRACOON Cloud experienced performance degradation. Some users reported slow response times and connection timeouts during the incident window. Why did this happen? The incident was caused by increased load and scaling issues. A part of the system was unable to handle the traffic volume, leading to resource exhaustion and subsequent service degradation. What did we do? Our team immediately identified the scaling bottleneck and implemented emergency load balancing measures. We scaled up the infrastructure resources to restore normal service levels by 13:00. What can we do to improve? We will implement automated scaling policies to handle traffic spikes, enhance monitoring and alerting systems for early detection of load issues, and conduct regular capacity planning reviews to prevent similar incidents. We apologize for any inconvenience this incident may have caused. We are committed to ensuring the stability and reliability of our services and will continue to take proactive measures to prevent similar incidents from happening in the future. If you have any questions or concerns, please don't hesitate to reach out to our support team for assistance.

1. 23 Haziran 2025 13:14 UTCinvestigating

   Our team is actively working to resolve the issue with the OnlyOffice preview. We apologize for any inconvenience this may cause and appreciate your patience. We will provide more information and updates as soon as they become available.

2. 23 Haziran 2025 13:15 UTCidentified

   We have identified the issue with the OnlyOffice preview. Our engineers are working on a resolution and we are confident that we will have a fix in place soon. We will provide more information and updates as soon as they become available.

3. 25 Haziran 2025 11:40 UTCresolved

   The issue with the OnlyOffice preview has been fully resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and appreciate your patience. If you continue to experience any issues, please don't hesitate to reach out to our support team for assistance.

4. 9 Eylül 2025 15:33 UTCpostmortem

   We experienced an issue with Office file previews on 2025-06-25 from around 09:00 to 13:40. Our team has worked diligently to identify the root cause and implement a resolution. In this post-mortem, we want to share the details of what happened, why it happened, what we did to resolve it, and what we will do to prevent similar incidents in the future. What happened? We experienced an issue with office file previews, making the feature unavailable for all users. Why did this happen? A recent update of the license key used by our backend service responsible for the office previews did not work as expected, even though the same update has been working on our Staging environment. What did we do? We immediately investigated and identified that the updated license key was causing authentication failures in production. We got in contact with the service provider to solve the issue as quickly as possible. What can we do to improve? We identified the issue that lead to the discrepancy between production and staging environment and made sure this will not happen again in the future. We apologize for any inconvenience this incident may have caused. We are committed to ensuring the stability and reliability of our services and will continue to take proactive measures to prevent similar incidents from happening in the future. If you have any questions or concerns, please don't hesitate to reach out to our support team for assistance.

1. 31 Mart 2025 06:06 UTCinvestigating

   We are currently investigating an issue with DRACOON Cloud. Our team is working to gather more information and resolve the issue as quickly as possible. We apologize for any inconvenience this may cause and will provide updates as soon as we have them.

2. 31 Mart 2025 06:11 UTCmonitoring

   The issue with DRACOON Cloud has been resolved, and we are monitoring the situation to ensure it remains stable. We apologize for any inconvenience this may have caused and appreciate your patience.

3. 31 Mart 2025 08:56 UTCresolved

   The issue with DRACOON Cloud has been fully resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and appreciate your patience. If you continue to experience any issues, please don't hesitate to reach out to our support team for assistance.

4. 9 Eylül 2025 15:18 UTCpostmortem

   We experienced an issue with DRACOON Cloud on 2025-03-31 from around 07:30 to 08:15. Our team has worked diligently to identify the root cause and implement a resolution. In this post-mortem, we want to share the details of what happened, why it happened, what we did to resolve it, and what we will do to prevent similar incidents in the future. What happened? DRACOON Cloud experienced performance degradation during early usage hours, affecting user access and normal operation. Why did this happen? Application containers hit memory limits during high traffic periods, causing automatic restarts and service interruptions as the container orchestration system cycled through unhealthy instances. The memory limits were set too conservatively and hadn't been updated to account for certain traffic spikes. What did we do? Our engineering team quickly identified the container restart pattern through application logs and monitoring dashboards. We immediately increased the memory limits for affected services and scaled up the number of container replicas to distribute the load. What can we do to improve? We will improve our monitoring, update memory limits based on actual usage patterns, and create automated scaling policies that proactively increase resources before hitting limits. We apologize for any inconvenience this incident may have caused. We are committed to ensuring the stability and reliability of our services and will continue to take proactive measures to prevent similar incidents from happening in the future. If you have any questions or concerns, please don't hesitate to reach out to our support team for assistance.

1. 12 Mart 2025 17:00 UTCinvestigating

   We are currently investigating an issue with DRACOON Cloud. Our team is working to gather more information and resolve the issue as quickly as possible. We apologize for any inconvenience this may cause and will provide updates as soon as we have them.

2. 12 Mart 2025 17:00 UTCresolved

   The issue with DRACOON Cloud has been fully resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and appreciate your patience. If you continue to experience any issues, please don't hesitate to reach out to our support team for assistance.