DRACOON Outage History

Started Oct 22, 2026, 11:12 AM UTC· resolved Oct 22, 2026, 11:12 AM UTC

1. resolved Oct 22, 2026, 11:12 AM UTC

   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.

Read the full incident report →

Started Aug 05, 2026, 09:00 PM UTC· resolved Aug 06, 2026, 09:55 AM UTC

1. investigating Aug 06, 2026, 09:54 AM UTC

   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. resolved Aug 06, 2026, 09:55 AM UTC

   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.

Read the full incident report →

Started Jul 15, 2026, 10:05 PM UTC· resolved Jul 15, 2026, 10:30 PM UTC

1. resolved Jul 16, 2026, 07:51 AM UTC

   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.

2. postmortem Jul 16, 2026, 07:54 AM UTC

   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.

Read the full incident report →

Started Jul 01, 2026, 09:32 AM UTC· resolved Jul 01, 2026, 10:26 AM UTC

1. investigating Jul 01, 2026, 09:32 AM UTC

   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. monitoring Jul 01, 2026, 10:11 AM UTC

   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. resolved Jul 01, 2026, 10:26 AM UTC

   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. postmortem Sep 23, 2026, 09:24 AM UTC

   **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.

Read the full incident report →

Started Apr 16, 2026, 11:00 AM UTC· resolved Apr 16, 2026, 08:57 PM UTC

1. investigating Apr 16, 2026, 03:58 PM UTC

   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. resolved Apr 16, 2026, 08:57 PM UTC

   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.

Read the full incident report →

Started Mar 24, 2026, 08:30 AM UTC· resolved Mar 25, 2026, 12:03 PM UTC

1. investigating Mar 24, 2026, 08:48 AM UTC

   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. investigating Mar 24, 2026, 08:51 AM UTC

   We are continuing to investigate this issue.

3. monitoring Mar 24, 2026, 09:42 AM UTC

   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. resolved Mar 25, 2026, 12:03 PM UTC

   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. postmortem Mar 27, 2026, 10:28 AM UTC

   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.

Read the full incident report →

Started Jan 12, 2026, 10:00 AM UTC· resolved Jan 12, 2026, 10:40 AM UTC

1. resolved Jan 12, 2026, 10:42 AM UTC

   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.

Read the full incident report →

Started Nov 27, 2025, 08:30 AM UTC· resolved Nov 27, 2025, 01:58 PM UTC

1. investigating Nov 27, 2025, 08:30 AM UTC

   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. identified Nov 27, 2025, 08:50 AM UTC

   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. monitoring Nov 27, 2025, 12:34 PM UTC

   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. resolved Nov 27, 2025, 01:58 PM UTC

   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.

Read the full incident report →

Started Nov 19, 2025, 08:42 AM UTC· resolved Nov 19, 2025, 11:27 AM UTC

1. investigating Nov 19, 2025, 08:42 AM UTC

   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. identified Nov 19, 2025, 09:55 AM UTC

   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. monitoring Nov 19, 2025, 11:09 AM UTC

   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. resolved Nov 19, 2025, 11:27 AM UTC

   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.

Read the full incident report →

Started Aug 13, 2025, 10:00 AM UTC· resolved Aug 13, 2025, 02:59 PM UTC

1. identified Aug 13, 2025, 10:00 AM UTC

   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. monitoring Aug 13, 2025, 01:45 PM UTC

   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. resolved Aug 13, 2025, 02:59 PM UTC

   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. postmortem Sep 02, 2025, 11:28 AM UTC

   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.

Read the full incident report →

Started Aug 04, 2025, 06:58 AM UTC· resolved Aug 04, 2025, 07:25 AM UTC

1. investigating Aug 04, 2025, 06:58 AM UTC

   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. resolved Aug 04, 2025, 07:25 AM UTC

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

Read the full incident report →

Started Jul 28, 2025, 07:54 AM UTC· resolved Jul 28, 2025, 09:45 AM UTC

1. investigating Jul 28, 2025, 07:54 AM UTC

   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. resolved Jul 28, 2025, 10:58 AM UTC

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

Read the full incident report →

Started Jul 12, 2025, 12:30 PM UTC· resolved Jul 12, 2025, 12:30 PM UTC

1. resolved Jul 16, 2025, 07:31 AM UTC

   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. postmortem Sep 09, 2025, 02:59 PM UTC

   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.

Read the full incident report →

Started Jun 23, 2025, 07:00 AM UTC· resolved Jun 25, 2025, 11:40 AM UTC

1. investigating Jun 23, 2025, 01:14 PM UTC

   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. identified Jun 23, 2025, 01:15 PM UTC

   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. resolved Jun 25, 2025, 11:40 AM UTC

   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. postmortem Sep 09, 2025, 03:33 PM UTC

   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.

Read the full incident report →

Started Feb 17, 2025, 07:24 AM UTC· resolved Feb 17, 2025, 10:16 AM UTC

1. investigating Feb 17, 2025, 07:24 AM UTC

   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. resolved Feb 17, 2025, 10:16 AM UTC

   The issue with our support portal 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.

Read the full incident report →

Started Jan 30, 2025, 08:11 AM UTC· resolved Jan 30, 2025, 08:51 AM UTC

1. investigating Jan 30, 2025, 08:11 AM UTC

   We are currently investigating an issue with the 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. monitoring Jan 30, 2025, 08:25 AM UTC

   The issue with the 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. resolved Jan 30, 2025, 08:51 AM UTC

   The issue with the 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. postmortem Sep 17, 2025, 09:57 AM UTC

   We experienced an issue with the DRACOON Cloud on 30.01.2025 from 09:11 - 9:25. 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? There has been an outage of the DRACOON Cloud during the incident window. Why did this happen? There happened to be some unexpected issues with one of our database servers, which caused the DRACOON Cloud to be unavailable during the incident window. What did we do? Our incident response team quickly started investigating, identified the underlying issue and resolved it by restoring connectivity to the database server. What can we do to improve? We will further investigate the issue and improve our infrastructure to prevent similar issues to occur 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.

Read the full incident report →

Started Jan 29, 2025, 08:10 AM UTC· resolved Jan 29, 2025, 12:02 PM UTC

1. investigating Jan 29, 2025, 08:10 AM UTC

   We are currently investigating an issue with the DRACOON application. 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. monitoring Jan 29, 2025, 08:52 AM UTC

   The issue with the DRACOON application 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. resolved Jan 29, 2025, 12:02 PM UTC

   The issue with the DRACOON application 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. postmortem Sep 17, 2025, 09:58 AM UTC

   We experienced an issue with the DRACOON Cloud on 29.01.2025 from 09:10 - 9:52. 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? There has been an outage of the DRACOON Cloud during the incident window. Why did this happen? There happened to be some unexpected issues with one of our database servers, which caused the DRACOON Cloud to be unavailable druing the incident window. What did we do? Our incident response team quickly started investigating, identified the underlying issue and resolved it by restoring connectivity to the database server. What can we do to improve? We will further investigate the issue and improve our infrastructure to prevent similar issues to occur 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.

Read the full incident report →

Started Jan 16, 2025, 12:23 PM UTC· resolved Jan 16, 2025, 02:29 PM UTC

1. investigating Jan 16, 2025, 12:23 PM UTC

   We are currently investigating an issue with the API. 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. identified Jan 16, 2025, 01:49 PM UTC

   We have identified the issue with the API. Our engineers have already found a resolution and we will perform an emergency maintenance to resolve the problem at 15:00. There might be a downtime of a few minutes.

3. monitoring Jan 16, 2025, 02:09 PM UTC

   The issue with the API 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. resolved Jan 16, 2025, 02:29 PM UTC

   The issue with the API 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. postmortem Sep 17, 2025, 09:58 AM UTC

   We experienced an issue with the API on 16.01.2025 from 13:23 - 15:09. 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? There has been an outage of the API during the incident window. Why did this happen? There happened to be some unexpected issues with one of our backend components, which caused the API to be unavailable druing the incident window. What did we do? Our incident response team quickly started investigating, identified the underlying issue and resolved it by providing a hotfix during an emergency maintenance. What can we do to improve? We will further investigate the issue and improve our infrastructure to prevent similar issues to occur 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.

Read the full incident report →

Started Jan 13, 2025, 02:10 PM UTC· resolved Jan 13, 2025, 03:51 PM UTC

1. investigating Jan 13, 2025, 02:10 PM UTC

   We are currently investigating an issue with Uploads. 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. monitoring Jan 13, 2025, 02:58 PM UTC

   The issue with Uploads 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. resolved Jan 13, 2025, 03:51 PM UTC

   The issue with Uploads 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. postmortem Sep 17, 2025, 10:00 AM UTC

   We experienced an issue with the Upload feature on 13.01.2025 from 15:10 - 15:58. 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? There has been an outage of the Upload feature during the incident window. Why did this happen? There happened to be some unexpected issues with one of our backend components, which caused the Upload feature to be unavailable during the incident window. What did we do? Our incident response team quickly started investigating, identified the underlying issue and resolved it by restoring the failed component to a working state. What can we do to improve? We will further investigate the issue and improve our infrastructure to prevent similar issues to occur 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.

Read the full incident report →

Started Dec 06, 2024, 03:55 PM UTC· resolved Dec 06, 2024, 04:44 PM UTC

1. investigating Dec 06, 2024, 03:55 PM UTC

   We are currently investigating an issue with API (group 1-9). 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. monitoring Dec 06, 2024, 03:59 PM UTC

   The issue with API (group 1-9) 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. resolved Dec 06, 2024, 04:44 PM UTC

   The issue with API (group 1-9) 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. postmortem Sep 17, 2025, 10:01 AM UTC

   We experienced an issue with the DRACOON Cloud on 06.12.2024 from 16:55 - 16:59. 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? There has been an outage of the DRACOON Cloud during the incident window. Why did this happen? There happened to be some unexpected issues with one of our database servers, which caused the DRACOON Cloud to be unavailable during the incident window. What did we do? Our incident response team quickly started investigating, identified the underlying issue and resolved it by restoring connectivity to the database server. What can we do to improve? We will further investigate the issue and improve our infrastructure to prevent similar issues to occur 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.

Read the full incident report →

Started Dec 04, 2024, 12:00 PM UTC· resolved Dec 04, 2024, 03:55 PM UTC

1. investigating Dec 04, 2024, 03:31 PM UTC

   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. monitoring Dec 04, 2024, 03:41 PM UTC

   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. resolved Dec 04, 2024, 03:55 PM UTC

   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.

Read the full incident report →

Started Dec 03, 2024, 03:03 PM UTC· resolved Dec 03, 2024, 03:59 PM UTC

1. investigating Dec 03, 2024, 03:03 PM UTC

   We are currently investigating an issue with API (group 02). 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. identified Dec 03, 2024, 03:04 PM UTC

   We have identified the issue with API (group 02). 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. identified Dec 03, 2024, 03:04 PM UTC

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

4. resolved Dec 03, 2024, 03:59 PM UTC

   The issue with API (group 02) 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.

Read the full incident report →

Started Oct 30, 2024, 01:36 PM UTC· resolved Oct 30, 2024, 01:55 PM UTC

1. investigating Oct 30, 2024, 01:36 PM UTC

   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. monitoring Oct 30, 2024, 01:45 PM UTC

   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. resolved Oct 30, 2024, 01:55 PM UTC

   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.

Read the full incident report →