Dracoon 中断历史

1. 2026年10月26日 UTC 09:29investigating

   我们正在调查一个问题 我们的电子邮件通知。 我们的小组正在努力收集更多信息并尽快解决这一问题。 我们对此可能造成的任何不便表示歉意,并将在得到最新情况后立即提供.

2. 2026年10月26日 UTC 11:31investigating

   我们的团队仍在积极努力,通过电子邮件通知解决这一问题。 一些使用某些邮件服务器配置的客户目前可能没有收到来自DRACOON的电子邮件通知;我们正在同我们的电子邮件发送伙伴合作,尽快解决这个问题。 我们为这可能造成的不便道歉,并赞赏你的耐心。 一旦得到更多信息和最新情况,我们将立即提供.

3. 2026年10月26日 UTC 15:38monitoring

   我们在电子邮件通知中找出了这个问题,并应用了一个解决问题的办法。 我们正在监测局势,以确保局势保持稳定并发现任何其他问题。 在过去几天里,一些收件人可能没有收到DRACOON的电子邮件通知. 受影响最大的组织是其收到的邮件通过某些公司邮件安全网关,其中包括接受收到的邮件之前的具体DNS检查。 根本原因很可能是一个第三方DNS问题,影响我们的通知发送域. 通常应再次发出通知。 我们正在密切监测执行情况,一旦问题得到全面解决,我们将公布最新情况。 在此期间未发出的通知不会自动受到谴责。 我们为这可能造成的不便而道歉,并感谢你的耐心.

4. 2026年10月27日 UTC 07:46resolved

   电子邮件通知的问题已完全解决。 所有系统现在都已正常运行。 我们为这可能造成的不便而道歉,并感谢你的耐心。 如果你继续遇到任何问题, 请不要犹豫 联系我们的支援团队寻求援助.

5. 2026年10月27日 UTC 07:49postmortem

   ** 2020年10月26日:Mortem事件后** 我们在2026年10月20日至10月26日期间遇到电子邮件通知的问题。 我们的团队为找出根源和执行一项决议而辛勤工作。 在这次尸检中,我们想详细谈谈所发生的事,为什么发生,我们为解决这个问题做了些什么,以及我们将如何防止今后发生类似事件. 发生了什么事? 在此期间,一些接收者没有收到DRACOON的电子邮件通知. 这个问题主要影响到那些通过某些公司电子邮件安全网关发送邮件的组织。 对于这些领取者来说,许多通知被拒,没有送达。 DRACOON的所有其他功能都没有受到影响。 为什么这样? 在接受邮件前,一些电子邮件安全网关检查发送者域名是否有效. 一个第三方提供商运行的DNS服务开始对我们的通知发送域的部分配置给出错误的答案. 由于这个答案,这些网关错误地将我们的发件人域视为无效,拒绝了通知. 我们自己的配置和邮件发送服务一直运作正常。 我们做了什么? 在第一次客户报告后,我们与我们的电子邮件发送伙伴一起分析了发送日志,发现拒绝遵循了明确的模式. 我们追踪到第三方的DNS问题 10月26日,我们改变了通知发送域的配置,使其不再依赖受影响的第三方服务。 事变后,交货恢复正常,我们密切监测,确认问题已经解决. ** 我们能做些什么来改进? ** * 我们正在审查与电子邮件有关的配置,以消除对外部服务的依赖。 * 我们正在改进对电子邮件发送的监测,以便更快地发现和调查异常拒绝率。 我们对此事件可能造成的不便表示歉意. 我们致力于确保我们服务的稳定性和可靠性,并将继续采取积极措施,防止今后发生类似事件。 如果你有任何问题或顾虑 请不要犹豫 联系我们的支援小组.

自动翻译自官方事件更新。

1. 2026年10月22日 UTC 11:12resolved

   我们知道最近公布的CVE-2026-109618和CVE-2026-109619的安全弱点影响到PHP. DRACOON没有使用PHP,因此不受这些弱点的影响. 不需要你采取行动。 我们继续密切监测安全建议,并将随时向你们通报评估情况.

自动翻译自官方事件更新。

1. 2026年8月6日 UTC 09:54investigating

   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. 2026年8月6日 UTC 09:55resolved

   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. 2026年7月16日 UTC 07:51resolved

   由于数据中心供应商的可用性问题,我们经历了部分DRACOON Cloud断电。 我们的工程师能够通过采取变通办法短期解决这些问题。 恢复了可用性,此后所有系统都正常运行。 我们为这可能造成的不便而道歉,并感谢你的耐心。 如果你继续遇到任何问题, 请不要犹豫 联系我们的支援团队寻求援助.

2. 2026年7月16日 UTC 07:54postmortem

   我们在2026-07-16年的00:05左右到00:30的CEST上与DRACOON Cloud经历了一个问题. 我们的团队为找出根源和执行一项决议而辛勤工作。 在这次尸检中,我们想详细谈谈所发生的事,为什么发生,我们为解决这个问题做了些什么,以及我们将如何防止今后发生类似事件. ‌ 发生了什么事? 我们的数据中心提供者在一个区域和可用区遇到可用性问题,我们的一些DRACOON Cloud基础设施在那里运行。 因此,DRACOON Cloud的部分内容在事发期间无法使用或者性能已经退化. ‌ 我们做了什么? 我们的工程师分析了情况,并运用了技术方法,以尽快全面恢复可用性。 ‌ 我们对此事件可能造成的不便表示歉意. 我们致力于确保我们服务的稳定性和可靠性,并将继续采取积极措施,防止今后发生类似事件。 如果你有任何问题或顾虑 请不要犹豫 联系我们的支援小组.

自动翻译自官方事件更新。

1. 2026年7月1日 UTC 09:32investigating

   我们正在调查一个与DRACOON的问题。 我们的小组正在努力收集更多信息并尽快解决这一问题。 我们对此可能造成的任何不便表示歉意,并将在得到最新情况后立即提供.

2. 2026年7月1日 UTC 10:11monitoring

   DRACOON的问题已经解决,我们正在监测局势,以确保局势保持稳定。 我们为这可能造成的不便而道歉,并感谢你的耐心.

3. 2026年7月1日 UTC 10:26resolved

   DRACOON的问题已经完全解决。 所有系统现在都已正常运行。 我们为这可能造成的不便而道歉,并感谢你的耐心。 如果你继续遇到任何问题, 请不要犹豫 联系我们的支援团队寻求援助.

4. 2026年9月23日 UTC 09:24postmortem

   ** 2026年7月1日,11:20 — 12:30 CEST** — 后摩腾 2026年7月1日,大约11:20至12:15 CEST,DRACOON Cloud有一个问题,导致临时服务中断。 我们的团队努力找出根源,并制定了一项决议。 在这次尸检中,我们要解释到底发生了什么,为什么发生了,我们做了什么来解决,以及我们将采取什么行动来防止今后发生类似的事件. 发生了什么事? 在大约55分钟的时间里,DRACOON Cloud无法提供或仅部分提供给用户. 恢复服务后,一直对站台进行监控至12:30CEST,以确保站台完全稳定. 没有丢失或泄露客户数据。 为什么这样? 我们对内部平台基础设施进行了计划中的改变。 改革的目的是进一步加强我们环境的安全。 然而,这一变化并没有像预期的那样在生产中发生,并影响了DRACOON Cloud的一些内部组件之间的交流。 这导致服务中断。 我们做了什么? 我们的监控提醒我们这个问题,我们的工程师们马上开始调查\(11:20 CEST\). 他们将中断追溯到最近的配置变化并改正,这恢复了受影响部分之间的正常通信. DRACOON Cloud在12: 15 CEST再次全程可用. 随后我们监控了平台以确认其稳定,并宣布事件在12:30CEST得到解决. ** 我们能做些什么来改进? ** * 我们将扩大基础设施配置变化的预生产测试和验证,使其更好地与实际生产条件相匹配。 * 我们将以较小的渐进步骤推出这种变化,以便及早发现任何出乎意料的行为。 * 我们将改进自动化检查,以更快地发现这样的问题,并更快地回滚。 我们对此事件可能造成的不便表示歉意. 我们致力于保持我们的服务稳定和可靠,并将继续采取积极主动的措施来防止今后发生类似事件。 如果你有任何问题或顾虑 请不要犹豫 联系我们的支援小组.

自动翻译自官方事件更新。

1. 2026年4月16日 UTC 15:58investigating

   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. 2026年4月16日 UTC 20:57resolved

   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. 2026年3月24日 UTC 08:48investigating

   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. 2026年3月24日 UTC 08:51investigating

   We are continuing to investigate this issue.

3. 2026年3月24日 UTC 09:42monitoring

   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. 2026年3月25日 UTC 12:03resolved

   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. 2026年3月27日 UTC 10:28postmortem

   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. 2026年1月12日 UTC 10:42resolved

   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. 2026年1月8日 UTC 10:42identified

   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. 2026年1月8日 UTC 10:43identified

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

3. 2026年1月8日 UTC 10:44resolved

   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. 2025年11月27日 UTC 08:30investigating

   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. 2025年11月27日 UTC 08:50identified

   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. 2025年11月27日 UTC 12:34monitoring

   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. 2025年11月27日 UTC 13:58resolved

   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. 2025年11月20日 UTC 14:52resolved

   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. 2025年11月19日 UTC 08:42investigating

   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. 2025年11月19日 UTC 09:55identified

   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. 2025年11月19日 UTC 11:09monitoring

   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. 2025年11月19日 UTC 11:27resolved

   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. 2025年8月13日 UTC 10:00identified

   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. 2025年8月13日 UTC 13:45monitoring

   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. 2025年8月13日 UTC 14:59resolved

   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. 2025年9月2日 UTC 11:28postmortem

   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. 2025年8月4日 UTC 06:58investigating

   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. 2025年8月4日 UTC 07:25resolved

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

1. 2025年7月28日 UTC 07:54investigating

   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. 2025年7月28日 UTC 10:58resolved

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

1. 2025年7月16日 UTC 07:31resolved

   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. 2025年9月9日 UTC 14:59postmortem

   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. 2025年7月7日 UTC 10:05investigating

   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. 2025年7月7日 UTC 10:59monitoring

   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. 2025年7月7日 UTC 11:10resolved

   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. 2025年9月9日 UTC 15:01postmortem

   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. 2025年6月23日 UTC 13:14investigating

   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. 2025年6月23日 UTC 13:15identified

   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. 2025年6月25日 UTC 11:40resolved

   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. 2025年9月9日 UTC 15:33postmortem

   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. 2025年3月31日 UTC 06:06investigating

   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. 2025年3月31日 UTC 06:11monitoring

   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. 2025年3月31日 UTC 08:56resolved

   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. 2025年9月9日 UTC 15:18postmortem

   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. 2025年3月12日 UTC 17:00investigating

   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. 2025年3月12日 UTC 17:00resolved

   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.