Störungsverlauf von Dracoon

1. 26. Oktober 2026 um 09:29 UTCinvestigating

   Wir untersuchen derzeit ein Problem mit unseren E-Mail-Benachrichtigungen. Unser Team arbeitet daran, mehr Informationen zu sammeln und das Problem so schnell wie möglich zu lösen. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursachen kann, und werden Updates bereitstellen, sobald wir sie haben.

2. 26. Oktober 2026 um 11:31 UTCinvestigating

   Unser Team arbeitet immer noch aktiv daran, das Problem mit E-Mail-Benachrichtigungen zu lösen. Einige Kunden, deren Unternehmen bestimmte E-Mail-Server-Konfigurationen verwenden, erhalten derzeit möglicherweise keine E-Mail-Benachrichtigungen von DRACOON; wir arbeiten mit unserem E-Mail-Zustellpartner zusammen, um dies so schnell wie möglich zu beheben. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursachen kann, und schätzen Ihre Geduld. Wir werden weitere Informationen und Updates bereitstellen, sobald sie verfügbar sind.

3. 26. Oktober 2026 um 15:38 UTCmonitoring

   Wir haben das Problem mit E-Mail-Benachrichtigungen identifiziert und einen Fix angewendet, um es zu beheben. Wir beobachten die Situation, um sicherzustellen, dass sie stabil bleibt und um zusätzliche Probleme zu erkennen. In den letzten Tagen haben einige Empfänger möglicherweise keine E-Mail-Benachrichtigungen von DRACOON erhalten. Am meisten betroffen sind Organisationen, deren eingehende E-Mails durch bestimmte Sicherheits-Gateways für Unternehmensmails laufen, die spezifische DNS-Checks enthalten, bevor sie eingehende E-Mails annehmen. Die Ursache war höchstwahrscheinlich ein DNS-Problem von Drittanbietern, das unsere Benachrichtigungs-Sender-Domain betraf. Benachrichtigungen sollten wieder normal zugestellt werden. Wir überwachen die Lieferung genau und werden ein Update veröffentlichen, sobald das Problem vollständig gelöst ist. Benachrichtigungen, die in diesem Zeitraum nicht zugestellt wurden, werden nicht automatisch erneut gesendet. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte, und schätzen Ihre Geduld.

4. 27. Oktober 2026 um 07:46 UTCresolved

   Das Problem mit E-Mail-Benachrichtigungen wurde vollständig gelöst. Alle Systeme arbeiten jetzt normal. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte, und schätzen Ihre Geduld. Wenn Sie weiterhin Probleme haben, zögern Sie bitte nicht, sich an unser Support-Team zu wenden.

5. 27. Oktober 2026 um 07:49 UTCpostmortem

   **20 - 26. Oktober 2026: Post-Mortem** Wir haben zwischen dem 20. Oktober und dem 26. Oktober 2026 ein Problem mit E-Mail-Benachrichtigungen festgestellt. Unser Team hat fleißig daran gearbeitet, die Ursache zu identifizieren und eine Lösung umzusetzen. In diesem Post-Mortem möchten wir die Details darüber teilen, was passiert ist, warum es passiert ist, was wir getan haben, um es zu lösen, und was wir tun werden, um ähnliche Vorfälle in Zukunft zu verhindern. **Was ist passiert?** Während dieser Zeit erhielten einige Empfänger keine E-Mail-Benachrichtigungen von DRACOON. Das Problem betraf vor allem Organisationen, deren eingehende E-Mails über bestimmte Sicherheits-Gateways von Unternehmen laufen. Für diese Empfänger wurden viele Mitteilungen abgelehnt und nicht zugestellt. Alle anderen DRACOON-Funktionen waren nicht betroffen. **Warum ist das passiert?** Vor der Annahme einer E-Mail überprüfen einige E-Mail-Sicherheitsgateways, ob die Domain des Absenders gültig ist. Ein DNS-Dienst, der von einem Drittanbieter betrieben wird, begann eine falsche Antwort für einen Teil der Konfiguration unserer Benachrichtigungs-Absender-Domain zu geben. Aufgrund dieser Antwort haben diese Gateways unsere Absender-Domain zu Unrecht als ungültig behandelt und die Benachrichtigungen abgelehnt. Unsere eigene Konfiguration und unser Postzustelldienst funktionierten durchgehend korrekt. ** Was haben wir gemacht?** Nach den ersten Kundenberichten haben wir die Zustellprotokolle zusammen mit unserem E-Mail-Zustellpartner analysiert und festgestellt, dass die Ablehnungen einem klaren Muster folgten. Wir haben sie auf das drittanbieter-dns-problem zurückgeführt. Am 26. Oktober haben wir die Konfiguration unserer Benachrichtigungs-Absender-Domain so geändert, dass sie nicht mehr von dem betroffenen Drittanbieterdienst abhängt. Nach der Änderung wurde die Lieferung wieder normalisiert, und wir haben sie genau überwacht, um zu bestätigen, dass das Problem behoben wurde. **Was können wir tun, um uns zu verbessern?** * Wir überprüfen unsere E-Mail-bezogenen Konfigurationen, um Abhängigkeiten von externen Diensten zu entfernen. * Wir verbessern unsere Überwachung der E-Mail-Zustellung, so dass ungewöhnliche Ablehnungsraten früher erkannt und untersucht werden. Wir entschuldigen uns für alle Unannehmlichkeiten, die dieser Vorfall verursacht haben könnte. Wir verpflichten uns, die Stabilität und Zuverlässigkeit unserer Dienste zu gewährleisten und werden weiterhin proaktive Maßnahmen ergreifen, um ähnliche Vorfälle in Zukunft zu verhindern. Wenn sie fragen oder bedenken haben, zögern sie bitte nicht, sich an unser support-team zu wenden.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. Oktober 2026 um 11:12 UTCresolved

   Wir sind uns der kürzlich veröffentlichten Sicherheitslücken CVE-2026-109618 und CVE-2026-109619 bewusst, die PHP betreffen. DRACOON verwendet PHP nicht und ist daher nicht von diesen Sicherheitslücken betroffen. Ihrerseits sind keine Maßnahmen erforderlich. Wir überwachen die Sicherheitshinweise weiterhin genau und werden Sie auf dem Laufenden halten, sollte sich diese Einschätzung ändern.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 6. August 2026 um 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. August 2026 um 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. Juli 2026 um 07:51 UTCresolved

   Aufgrund von Verfügbarkeitsproblemen unseres Rechenzentrumsanbieters haben wir einen teilweisen Ausfall der DRACOON Cloud erlebt. Unsere Ingenieure konnten die Probleme kurzfristig durch einen Workaround lösen. Dadurch wurde die Verfügbarkeit wiederhergestellt und alle Systeme arbeiteten danach wieder normal. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte, und schätzen Ihre Geduld. Wenn Sie weiterhin Probleme haben, zögern Sie bitte nicht, sich an unser Support-Team zu wenden.

2. 16. Juli 2026 um 07:54 UTCpostmortem

   Wir hatten ein Problem mit DRACOON Cloud am 2026-07-16 von etwa 00:05 bis 00:30 Uhr MESZ. Unser Team hat fleißig daran gearbeitet, die Ursache zu identifizieren und eine Lösung umzusetzen. In diesem Post-Mortem möchten wir die Details darüber teilen, was passiert ist, warum es passiert ist, was wir getan haben, um es zu lösen, und was wir tun werden, um ähnliche Vorfälle in Zukunft zu verhindern. **Was ist passiert?** Unser Rechenzentrumsanbieter hatte Probleme mit der Verfügbarkeit in einer Region und einer Verfügbarkeitszone, in der einige unserer DRACOON Cloud-Infrastruktur ausgeführt werden. Infolgedessen waren Teile der DRACOON Cloud während des Vorfalls nicht verfügbar oder hatten eine verschlechterte Leistung. ** Was haben wir gemacht?** Unsere Ingenieure analysierten die Situation und wandten einen technischen Workaround an, um die Verfügbarkeit so schnell wie möglich vollständig wiederherzustellen. Wir entschuldigen uns für alle Unannehmlichkeiten, die dieser Vorfall verursacht haben könnte. Wir verpflichten uns, die Stabilität und Zuverlässigkeit unserer Dienste zu gewährleisten und werden weiterhin proaktive Maßnahmen ergreifen, um ähnliche Vorfälle in Zukunft zu verhindern. Wenn sie fragen oder bedenken haben, zögern sie bitte nicht, sich an unser support-team zu wenden.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 1. Juli 2026 um 09:32 UTCinvestigating

   Wir untersuchen derzeit ein Problem mit DRACOON. Unser Team arbeitet daran, mehr Informationen zu sammeln und das Problem so schnell wie möglich zu lösen. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursachen kann, und werden Updates bereitstellen, sobald wir sie haben.

2. 1. Juli 2026 um 10:11 UTCmonitoring

   Das Problem mit DRACOON wurde gelöst, und wir überwachen die Situation, um sicherzustellen, dass sie stabil bleibt. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte, und schätzen Ihre Geduld.

3. 1. Juli 2026 um 10:26 UTCresolved

   Das Problem mit DRACOON wurde vollständig gelöst. Alle Systeme arbeiten jetzt normal. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte, und schätzen Ihre Geduld. Wenn Sie weiterhin Probleme haben, zögern Sie bitte nicht, sich an unser Support-Team zu wenden.

4. 23. September 2026 um 09:24 UTCpostmortem

   **Juli 1, 2026, 11:20 – 12:30 CEST** - Post-Mortem Am 1. Juli 2026, zwischen ca. 11:20 und 12:15 Uhr MESZ, DRACOON Cloud hatte ein Problem, das eine vorübergehende Serviceunterbrechung verursachte. Unser Team hat daran gearbeitet, die Ursache zu identifizieren und eine Lösung zu finden. In diesem Post-Mortem wollen wir erklären, was passiert ist, warum es passiert ist, was wir getan haben, um es zu lösen, und was wir tun werden, um ähnliche Vorfälle in Zukunft zu verhindern. **Was ist passiert?** Etwa 55 Minuten lang war DRACOON Cloud nicht oder nur teilweise für Benutzer verfügbar. Nachdem wir den Service wiederhergestellt hatten, überwachten wir die Plattform bis 12:30 Uhr MESZ, um sicherzustellen, dass sie vollständig stabil war. Es wurden keine Kundendaten verloren oder kompromittiert. **Warum ist das passiert?** Wir haben eine geplante Konfigurationsänderung für unsere interne Plattforminfrastruktur eingeführt. Ziel des Wandels war es, die Sicherheit unserer Umwelt weiter zu stärken. Die Änderung verhielt sich jedoch nicht wie erwartet in der Produktion und beeinflusste die Kommunikation zwischen einigen internen Komponenten von DRACOON Cloud. Dies führte zu einer Unterbrechung des Dienstes. ** Was haben wir gemacht?** Unsere Überwachung machte uns auf das Problem aufmerksam, und unsere Ingenieure begannen sofort mit der Untersuchung (11:20 Uhr MESZ). Sie verfolgten die Unterbrechung auf die jüngste Konfigurationsänderung zurück und korrigierten sie, wodurch die normale Kommunikation zwischen den betroffenen Komponenten wiederhergestellt wurde. DRACOON Cloud war um 12:15 Uhr wieder voll verfügbar. Wir überwachten dann die Plattform, um zu bestätigen, dass sie stabil war, und erklärten den Vorfall um 12:30 Uhr MESZ für behoben. **Was können wir tun, um uns zu verbessern?** * Wir werden unsere Vorproduktionstests und -validierung für Änderungen der Infrastrukturkonfiguration erweitern, damit sie den realen Produktionsbedingungen besser entsprechen. * Wir werden Änderungen dieser Art in kleineren, schrittweisen Schritten durchführen, damit wir unerwartetes Verhalten frühzeitig erkennen. * Wir werden unsere automatisierten Überprüfungen verbessern, um Probleme wie diese schneller zu finden und ein schnelleres Rollback zu ermöglichen. Wir entschuldigen uns für alle Unannehmlichkeiten, die dieser Vorfall verursacht haben könnte. Wir sind bestrebt, unsere Dienste stabil und zuverlässig zu halten und werden weiterhin proaktive Maßnahmen ergreifen, um ähnliche Vorfälle in Zukunft zu verhindern. Wenn sie fragen oder bedenken haben, zögern sie bitte nicht, sich an unser support-team zu wenden.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. April 2026 um 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. April 2026 um 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. März 2026 um 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. März 2026 um 08:51 UTCinvestigating

   We are continuing to investigate this issue.

3. 24. März 2026 um 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. März 2026 um 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. März 2026 um 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. Januar 2026 um 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. Januar 2026 um 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. Januar 2026 um 10:43 UTCidentified

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

3. 8. Januar 2026 um 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. November 2025 um 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. November 2025 um 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. November 2025 um 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. November 2025 um 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. November 2025 um 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. November 2025 um 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. November 2025 um 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. November 2025 um 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. November 2025 um 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. August 2025 um 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. August 2025 um 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. August 2025 um 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. September 2025 um 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. August 2025 um 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. August 2025 um 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. Juli 2025 um 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. Juli 2025 um 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. Juli 2025 um 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. September 2025 um 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. Juli 2025 um 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. Juli 2025 um 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. Juli 2025 um 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. September 2025 um 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. Juni 2025 um 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. Juni 2025 um 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. Juni 2025 um 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. September 2025 um 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. März 2025 um 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. März 2025 um 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. März 2025 um 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. September 2025 um 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. März 2025 um 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. März 2025 um 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.