История сбоев Dracoon

1. 6 августа 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 августа 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 июля 2026 г. в 07:51 UTCresolved

   В результате проблем с доступностью нашего поставщика центров обработки данных мы столкнулись с частичным отключением DRACOON Cloud. Наши инженеры смогли решить проблемы в краткосрочной перспективе, применив обходной путь. Это восстановило доступность, и все системы снова работали нормально. Мы приносим извинения за любые неудобства, которые это могло вызвать, и ценим ваше терпение. Если вы продолжаете испытывать какие-либо проблемы, пожалуйста, не стесняйтесь обращаться к нашей команде поддержки за помощью.

2. 16 июля 2026 г. в 07:54 UTCpostmortem

   Мы столкнулись с проблемой с DRACOON Cloud в 2026-07-16 примерно с 00:05 до 00:30 CEST. Наша команда усердно работала над выявлением первопричины и реализацией резолюции. В этом посмертном докладе мы хотим поделиться подробностями того, что произошло, почему это произошло, что мы сделали, чтобы разрешить это, и что мы будем делать, чтобы предотвратить подобные инциденты в будущем. ** Что случилось? ** Наш поставщик центров обработки данных столкнулся с проблемами доступности в регионе и зоне доступности, где работает часть нашей инфраструктуры DRACOON Cloud. В результате части DRACOON Cloud были недоступны или ухудшили производительность во время инцидента. ** Что мы сделали? ** Наши инженеры проанализировали ситуацию и применили технические обходные пути для максимально быстрого восстановления доступности. Мы приносим извинения за любые неудобства, которые мог причинить этот инцидент. Мы стремимся обеспечить стабильность и надежность наших услуг и будем продолжать принимать активные меры для предотвращения подобных инцидентов в будущем. Если у вас есть какие-либо вопросы или проблемы, пожалуйста, не стесняйтесь обращаться к нашей команде поддержки за помощью.

Автоматический перевод официального обновления инцидента.

1. 1 июля 2026 г. в 09:32 UTCinvestigating

   В настоящее время мы расследуем вопрос с DRACOON. Наша команда работает над тем, чтобы собрать больше информации и решить проблему как можно быстрее. Мы приносим извинения за любые неудобства, которые это может вызвать, и предоставим обновления, как только они у нас будут.

2. 1 июля 2026 г. в 10:11 UTCmonitoring

   Вопрос с DRACOON решен, и мы следим за ситуацией, чтобы она оставалась стабильной. Мы приносим извинения за любые неудобства, которые это могло вызвать, и ценим ваше терпение.

3. 1 июля 2026 г. в 10:26 UTCresolved

   Вопрос с DRACOON полностью решен. Сейчас все системы работают нормально. Мы приносим извинения за любые неудобства, которые это могло вызвать, и ценим ваше терпение. Если вы продолжаете испытывать какие-либо проблемы, пожалуйста, не стесняйтесь обращаться к нашей команде поддержки за помощью.

Автоматический перевод официального обновления инцидента.

1. 16 апреля 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 апреля 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 марта 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 марта 2026 г. в 08:51 UTCinvestigating

   We are continuing to investigate this issue.

3. 24 марта 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 марта 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 марта 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 января 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 января 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 января 2026 г. в 10:43 UTCidentified

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

3. 8 января 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 ноября 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 ноября 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 ноября 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 ноября 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 ноября 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 ноября 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 ноября 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 ноября 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 ноября 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 августа 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 августа 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 августа 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 сентября 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 августа 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 августа 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 июля 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 июля 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 июля 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 сентября 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 июля 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 июля 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 июля 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 сентября 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 июня 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 июня 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 июня 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 сентября 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 марта 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 марта 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 марта 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 сентября 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 марта 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 марта 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.

1. 17 февраля 2025 г. в 07:24 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. 17 февраля 2025 г. в 10:16 UTCresolved

   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.

1. 30 января 2025 г. в 08:11 UTCinvestigating

   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. 30 января 2025 г. в 08:25 UTCmonitoring

   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. 30 января 2025 г. в 08:51 UTCresolved

   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. 17 сентября 2025 г. в 09:57 UTCpostmortem

   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.