Dracoon outage history

We are currently investigating an issue with our Email notifications. 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.

Our team is still actively working to resolve the issue with Email notifications. Some customers whose organizations use certain mail server configurations may currently not receive email notifications from DRACOON; we are working with our email delivery partner to resolve this as quickly as possible. 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.

We identified the issue with Email notifications and applied a fix to resolve it. We are monitoring the situation to ensure it remains stable and to detect any additional issues. In the last few days, some recipients may have not received email notifications from DRACOON. Mostly affected are organizations whose incoming mail runs through certain corporate mail security gateways that include specific DNS checks before accepting incoming mails. The root cause was most likely a third-party DNS issue affecting our notification sender domain. Notifications should be delivered normally again. We are monitoring delivery closely and will post an update once the issue is fully resolved. Notifications that were not delivered during this period will not be resent automatically. We apologize for any inconvenience this may have caused and appreciate your patience.

We are aware of the recently published security vulnerabilities CVE-2026-109618 and CVE-2026-109619 affecting PHP. DRACOON does not use PHP and is therefore not affected by these vulnerabilities. No action is required on your part. We continue to closely monitor security advisories and will keep you informed should this assessment change.

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.

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.

As a result of availability issues of our datacenter provider, we experienced a partial outage of DRACOON Cloud. Our engineers were able to resolve the issues short-term by applying a workaround. This restored availability and all systems were operating normally again afterwards. 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.

We experienced an issue with DRACOON Cloud on 2026-07-16 from around 00:05 to 00:30 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?** Our datacenter provider experienced availability issues in a region and availability zone, where some our DRACOON Cloud infrastructure is running. As a result of that, parts of DRACOON Cloud were unavailable or had degraded performance during the time of the incident. ‌ **What did we do?** Our engineers analyzed the situation and applied a technical workaround to fully restore availability as fast as possible. ‌ 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.

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.

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.

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.

**July 1, 2026, 11:20 – 12:30 CEST** - Post-Mortem On July 1, 2026, between approximately 11:20 and 12:15 CEST, DRACOON Cloud had an issue that caused a temporary service interruption. Our team has worked to identify the root cause and put a resolution in place. In this post-mortem, we want to explain 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?** For about 55 minutes, DRACOON Cloud was unavailable or only partially available for users. After we restored service, we kept monitoring the platform until 12:30 CEST to make sure it was fully stable. No customer data was lost or compromised. **Why did this happen?** We rolled out a planned configuration change to our internal platform infrastructure. The goal of the change was to further strengthen the security of our environment. However, the change did not behave as expected in production and affected communication between some internal components of DRACOON Cloud. This caused the service interruption. **What did we do?** Our monitoring alerted us to the problem, and our engineers began investigating right away \(11:20 CEST\). They traced the interruption back to the recent configuration change and corrected it, which restored normal communication between the affected components. DRACOON Cloud was fully available again at 12:15 CEST. We then monitored the platform to confirm it was stable and declared the incident resolved at 12:30 CEST. **What can we do to improve?** * We will expand our pre-production testing and validation for infrastructure configuration changes so that they better match real production conditions. * We will roll out changes of this kind in smaller, gradual steps, so that we detect any unexpected behavior early. * We will improve our automated checks to find problems like this faster and to allow quicker rollback. We apologize for any inconvenience this incident may have caused. We are committed to keeping our services stable and reliable and will continue to take proactive measures to prevent similar incidents in the future. If you have any questions or concerns, please don't hesitate to reach out to our support team for assistance.

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.

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.

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.

We are continuing to investigate this issue.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.