Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Istoricul incidentelor Dracoon

    55 incidente Dracoon înregistrate începând din ianuarie 2024, cu actualizări oficiale, componente afectate, durată și informații despre rezolvare.

    Înapoi la starea actuală

    Încălcarea parțială a notificărilor de e-mail

    A început 26 octombrie 2026 la 09:29 UTC · 22h 18m

    OutageIncident major
    Componente afectate
    Instant messagesSubscribed messages
    1. 26 octombrie 2026 la 09:29 UTCinvestigating

      Investigăm în prezent o problemă cu notificările noastre de e-mail. Echipa noastră se străduiește să adune mai multe informații și să rezolve problema cât mai repede posibil. Ne cerem scuze pentru orice neplăceri pe care le-ar putea cauza şi vă vom oferi actualizări imediat ce le avem.

    2. 26 octombrie 2026 la 11:31 UTCinvestigating

      Echipa noastră încă lucrează activ pentru a rezolva problema cu notificări de e-mail. Unii clienţi ale căror organizaţii folosesc anumite configuraţii de servere de e-mail pot să nu primească în prezent notificări de e-mail de la DRACOON; lucrăm cu partenerul nostru de livrare de e-mail pentru a rezolva acest lucru cât mai repede posibil. Ne cerem scuze pentru orice neplăceri pe care le-ar putea cauza şi aprecia răbdarea dumneavoastră. Vom furniza mai multe informații și actualizări de îndată ce acestea devin disponibile.

    3. 26 octombrie 2026 la 15:38 UTCmonitoring

      Am identificat problema cu notificări de e-mail și a aplicat un fix pentru a rezolva problema. Monitorizăm situația pentru a ne asigura că rămâne stabilă și pentru a detecta orice probleme suplimentare. În ultimele zile, este posibil ca unii destinatari să nu fi primit notificări prin e-mail de la DRACOON. Cele mai multe sunt afectate sunt organizații ale căror scrisori de intrare trece prin anumite porți de securitate e-mail corporative care includ controale specifice DNS înainte de a accepta mail-uri primite. Cauza principală a fost, cel mai probabil, o problemă terţă parte DNS care afectează domeniul nostru de notificare expeditor. Notificările ar trebui să fie livrate în mod normal din nou. Monitorizăm îndeaproape livrarea și vom posta o actualizare după rezolvarea completă a problemei. Notificările care nu au fost transmise în această perioadă nu vor fi resentimente în mod automat. Ne cerem scuze pentru orice neplăceri cauzate de acest lucru şi apreciem răbdarea dumneavoastră.

    4. 27 octombrie 2026 la 07:46 UTCresolved

      Problema notificărilor de e-mail a fost pe deplin rezolvată. Toate sistemele funcţionează normal. Ne cerem scuze pentru orice neplăceri cauzate de acest lucru şi apreciem răbdarea dumneavoastră. Dacă continuați să experimentați orice probleme, vă rugăm să nu ezitați să ajungeți la echipa noastră de sprijin pentru asistență.

    5. 27 octombrie 2026 la 07:49 UTCpostmortem

      **20 - 26 octombrie 2026: Post-Mortem** Am avut o problemă cu notificările prin e-mail între 20 octombrie și 26 octombrie 2026. Echipa noastră a lucrat cu sârguinţă pentru a identifica cauza fundamentală şi a implementa o rezoluţie. În acest post-mortem, vrem să împărtășim detaliile a ceea ce sa întâmplat, de ce sa întâmplat, ceea ce am făcut pentru a rezolva, și ce vom face pentru a preveni incidente similare în viitor. Ce s-a întâmplat? În această perioadă, unii destinatari nu au primit notificări prin e-mail de la DRACOON. Problema a afectat în principal organizațiile ale căror mesaje primite circulă prin anumite portaluri de securitate de e-mail corporative. Pentru acești destinatari, numeroase notificări au fost respinse și nu au fost transmise. Toate celelalte funcţii ale DRACOON nu au fost afectate. De ce s-a întâmplat asta? Înainte de a accepta un e-mail, unele portaluri de securitate de e-mail verifica că domeniul expeditorului este valabil. Un serviciu DNS operat de un furnizor terţ a început să ofere un răspuns incorect pentru o parte din configuraţia domeniului expeditorului nostru de notificare. Datorită acestui răspuns, aceste porţi de acces au tratat greşit domeniul expeditorului ca fiind invalid şi au respins notificările. Configuraţia noastră şi serviciul nostru de livrare a corespondenţei au funcţionat corect pe tot parcursul. Ce am făcut? După primele rapoarte ale clienților, am analizat jurnalele de livrare împreună cu partenerul nostru de livrare de e-mail și am constatat că respingerile au urmat un model clar. I-am urmărit până la problema DNS. La 26 octombrie, am schimbat configuraţia domeniului expeditorului nostru de notificare astfel încât să nu mai depindă de serviciul terţ afectat. După schimbare, livrarea a revenit la normal, și l-am monitorizat îndeaproape pentru a confirma problema a fost rezolvată. ** Ce putem face pentru a îmbunătăți?** * Ne revizuim configuraţiile legate de e-mail pentru a elimina dependenţele de servicii externe. * Suntem îmbunătăţi monitorizarea noastră de livrare de e-mail, astfel încât ratele neobişnuite de respingere sunt detectate şi investigate mai devreme. Ne cerem scuze pentru orice neplăceri pe care acest incident le-a cauzat. Ne-am angajat să asigurăm stabilitatea și fiabilitatea serviciilor noastre și vom continua să luăm măsuri proactive pentru a preveni apariția unor incidente similare în viitor. Dacă aveți întrebări sau preocupări, vă rugăm să nu ezitați să ajungeți la echipa noastră de sprijin pentru asistență.

    Traducere automată din actualizarea oficială a incidentului.

    DRACOON nu este afectat de CVE-2026-109618 şi CVE-2026-109619

    A început 22 octombrie 2026 la 11:12 UTC · 0m

    Pending
    1. 22 octombrie 2026 la 11:12 UTCresolved

      Suntem conștienți de vulnerabilitățile de securitate recent publicate CVE-2026-109618 și CVE-2026-109619 care afectează PHP. DRACOON nu utilizează PHP și, prin urmare, nu este afectat de aceste vulnerabilități. Nu este necesară nicio acţiune din partea ta. Continuăm să monitorizăm îndeaproape consilierii de securitate și vă vom ține la curent în cazul în care această evaluare se va schimba.

    Traducere automată din actualizarea oficială a incidentului.

    Partial Outage of DRACOON Cloud Uploads and Downloads

    A început 5 august 2026 la 21:00 UTC · 12h 55m

    OutageIncident major
    Componente afectate
    DownloadUpload
    1. 6 august 2026 la 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 la 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.

    Ieșirea parțială a norului DRACOON

    A început 15 iulie 2026 la 22:05 UTC · 0m

    Pending
    1. 16 iulie 2026 la 07:51 UTCresolved

      Ca urmare a problemelor de disponibilitate ale furnizorului nostru de datecenter, am avut parte de o pană parţială de Cloud DRACOON. Inginerii noştri au reuşit să rezolve problemele pe termen scurt prin aplicarea unei analize. Această disponibilitate restabilită şi toate sistemele funcţionau normal după aceea. Ne cerem scuze pentru orice neplăceri cauzate de acest lucru şi apreciem răbdarea dumneavoastră. Dacă continuați să experimentați orice probleme, vă rugăm să nu ezitați să ajungeți la echipa noastră de sprijin pentru asistență.

    2. 16 iulie 2026 la 07:54 UTCpostmortem

      Am avut o problemă cu DRACOON Cloud pe 2026-07-16 de la aproximativ 00:05 la 00:30 CEST. Echipa noastră a lucrat cu sârguinţă pentru a identifica cauza fundamentală şi a implementa o rezoluţie. În acest post-mortem, vrem să împărtășim detaliile a ceea ce sa întâmplat, de ce sa întâmplat, ceea ce am făcut pentru a rezolva, și ce vom face pentru a preveni incidente similare în viitor. Ce s-a întâmplat? Furnizorul nostru de date a experimentat probleme de disponibilitate într-o regiune și zonă de disponibilitate, în cazul în care unele infrastructura noastră DRACOON Cloud rulează. Ca urmare a acestui fapt, unele părți din Norul DRACOON nu au fost disponibile sau au avut performanțe degradate în timpul incidentului. Ce am făcut? Inginerii noştri au analizat situaţia şi au aplicat o procedură tehnică pentru a restabili disponibilitatea cât mai repede posibil. Ne cerem scuze pentru orice neplăceri pe care acest incident le-a cauzat. Ne-am angajat să asigurăm stabilitatea și fiabilitatea serviciilor noastre și vom continua să luăm măsuri proactive pentru a preveni apariția unor incidente similare în viitor. Dacă aveți întrebări sau preocupări, vă rugăm să nu ezitați să ajungeți la echipa noastră de sprijin pentru asistență.

    Traducere automată din actualizarea oficială a incidentului.

    Ieșirea DRACOON

    A început 1 iulie 2026 la 09:32 UTC · 54m

    OutageIncident critic
    Componente afectate
    DATEVBackground jobs (group 06)API (group 03)API (group 02)AuthenticationWeb AppMonthly reportsBackground jobs (group 01)Virus protectionBackground jobs (group 03)API (group 01)DownloadAPI (group 06)Background jobs (group 09)Background jobs (group 05)Instant messagesUploadBackground jobs (group 07)Preview deliveryOne-Time reportsWebDAVEvent loggingBackground jobs (group 04)SigningBackground jobs (group 02)API (group 09)API (group 04)API (group 08)API (group 05)Background jobs (group 08)WebhooksPreview creationSubscribed messagesAPI (group 07)Branding
    1. 1 iulie 2026 la 09:32 UTCinvestigating

      În prezent investigăm o problemă cu DRACOON. Echipa noastră se străduiește să adune mai multe informații și să rezolve problema cât mai repede posibil. Ne cerem scuze pentru orice neplăceri pe care le-ar putea cauza şi vă vom oferi actualizări imediat ce le avem.

    2. 1 iulie 2026 la 10:11 UTCmonitoring

      Problema cu DRACOON a fost rezolvată și monitorizăm situația pentru a ne asigura că rămâne stabilă. Ne cerem scuze pentru orice neplăceri cauzate de acest lucru şi apreciem răbdarea dumneavoastră.

    3. 1 iulie 2026 la 10:26 UTCresolved

      Problema cu DRACOON a fost pe deplin rezolvată. Toate sistemele funcţionează normal. Ne cerem scuze pentru orice neplăceri cauzate de acest lucru şi apreciem răbdarea dumneavoastră. Dacă continuați să experimentați orice probleme, vă rugăm să nu ezitați să ajungeți la echipa noastră de sprijin pentru asistență.

    4. 23 septembrie 2026 la 09:24 UTCpostmortem

      ** 1 iulie 2026, 11:20 La 1 iulie 2026, între aproximativ 11:20 și 12:15 CEST, DRACOON Cloud a avut o problemă care a cauzat o întrerupere temporară a serviciului. Echipa noastră a lucrat pentru a identifica cauza principală și a pus o rezoluție în vigoare. În acest post-mortem, vrem să explicăm ce s-a întâmplat, de ce s-a întâmplat, ce am făcut pentru a o rezolva, şi ce vom face pentru a preveni incidente similare în viitor. Ce s-a întâmplat? Timp de aproximativ 55 de minute, DRACOON Cloud nu a fost disponibil sau doar parțial disponibil pentru utilizatori. După ce am restabilit serviciul, am continuat să monitorizăm platforma până la 12:30 CEST pentru a ne asigura că este complet stabilă. Nu au fost pierdute sau compromise datele clientului. De ce s-a întâmplat asta? Am lansat o schimbare de configurare planificată a infrastructurii noastre de platformă internă. Scopul schimbării a fost consolidarea în continuare a securității mediului nostru. Cu toate acestea, modificarea nu s-a comportat aşa cum era de aşteptat în producţie şi a afectat comunicarea dintre unele componente interne ale DRACOON Cloud. Asta a cauzat întreruperea serviciului. Ce am făcut? Monitorizarea noastră ne-a alertat asupra problemei, iar inginerii noştri au început să investigheze imediat. Au urmărit întreruperea până la schimbarea recentă a configurației și au corectat-o, ceea ce a restabilit comunicarea normală între componentele afectate. Norul Dragoon a fost din nou disponibil la 12:15 CEST. Apoi am monitorizat platforma pentru a confirma că a fost stabilă și a declarat incidentul rezolvat la 12:30 CEST. ** Ce putem face pentru a îmbunătăți?** * Vom extinde testarea pre-producție și validarea pentru modificările configurației infrastructurii, astfel încât acestea să corespundă mai bine condițiilor reale de producție. * Vom face schimbări de acest fel în paşi mai mici, graduali, astfel încât să detectăm orice comportament neaşteptat mai devreme. * Vom îmbunătăți controalele noastre automate pentru a găsi probleme de acest gen mai repede și pentru a permite o revenire mai rapidă. Ne cerem scuze pentru orice neplăceri pe care acest incident le-a cauzat. Ne angajăm să ne menţinem serviciile stabile şi fiabile şi să continuăm să luăm măsuri proactive pentru a preveni incidente similare în viitor. Dacă aveți întrebări sau preocupări, vă rugăm să nu ezitați să ajungeți la echipa noastră de sprijin pentru asistență.

    Traducere automată din actualizarea oficială a incidentului.

    Degraded Performance of Virus Protection

    A început 16 aprilie 2026 la 11:00 UTC · 9h 57m

    IssuesIncident minor
    Componente afectate
    Virus protection
    1. 16 aprilie 2026 la 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 aprilie 2026 la 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.

    Partial Outage of Web App

    A început 24 martie 2026 la 08:30 UTC · 1d 3h

    OutageIncident major
    Componente afectate
    Web App
    1. 24 martie 2026 la 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 martie 2026 la 08:51 UTCinvestigating

      We are continuing to investigate this issue.

    3. 24 martie 2026 la 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 martie 2026 la 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 martie 2026 la 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.

    Outage of DRACOON service

    A început 12 ianuarie 2026 la 10:00 UTC · 40m

    OutageIncident major
    1. 12 ianuarie 2026 la 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.

    Partial Outage of DRACOON Cloud

    A început 8 ianuarie 2026 la 10:00 UTC · 45m

    IssuesIncident minor
    Componente afectate
    DATEVBackground jobs (group 06)API (group 03)API (group 02)AuthenticationWeb AppMonthly reportsBackground jobs (group 01)Virus protectionBackground jobs (group 03)API (group 01)DownloadAPI (group 06)Background jobs (group 09)Background jobs (group 05)Instant messagesUploadBackground jobs (group 07)Preview deliveryOne-Time reportsWebDAVEvent loggingBackground jobs (group 04)SigningBackground jobs (group 02)API (group 09)API (group 04)API (group 08)API (group 05)Background jobs (group 08)WebhooksPreview creationSubscribed messagesAPI (group 07)Branding
    1. 8 ianuarie 2026 la 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 ianuarie 2026 la 10:43 UTCidentified

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

    3. 8 ianuarie 2026 la 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.

    Outage of Virus Protection Scanning

    A început 27 noiembrie 2025 la 08:30 UTC · 5h 28m

    OutageIncident critic
    Componente afectate
    Virus protection
    1. 27 noiembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 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.

    Partial Outage of DRACOON Cloud

    A început 20 noiembrie 2025 la 13:55 UTC · 0m

    IssuesIncident minor
    1. 20 noiembrie 2025 la 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.

    Outage of DRACOON Virus Protection

    A început 19 noiembrie 2025 la 08:42 UTC · 2h 45m

    OutageIncident critic
    Componente afectate
    Virus protection
    1. 19 noiembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 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.

    Degraded Performance of Virus protection

    A început 13 august 2025 la 10:00 UTC · 5h 0m

    IssuesIncident minor
    Componente afectate
    Virus protection
    1. 13 august 2025 la 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 la 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 la 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 septembrie 2025 la 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.

    Outage of our Support Portal (Dracoon Server)

    A început 4 august 2025 la 06:58 UTC · 27m

    Pending
    1. 4 august 2025 la 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 la 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.

    Outage of our Support Portal

    A început 28 iulie 2025 la 07:54 UTC · 1h 51m

    Pending
    1. 28 iulie 2025 la 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 iulie 2025 la 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.

    Partial Outage of DRACOON

    A început 12 iulie 2025 la 12:30 UTC · 0m

    IssuesIncident minor
    1. 16 iulie 2025 la 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 septembrie 2025 la 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.

    Partial Outage of DRACOON

    A început 7 iulie 2025 la 10:05 UTC · 1h 5m

    OutageIncident major
    Componente afectate
    DATEVAPI (group 03)API (group 02)AuthenticationWeb AppVirus protectionAPI (group 01)API (group 06)WebDAVSigningAPI (group 09)API (group 04)API (group 08)API (group 05)WebhooksAPI (group 07)Branding
    1. 7 iulie 2025 la 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 iulie 2025 la 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 iulie 2025 la 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 septembrie 2025 la 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.

    Outage of OnlyOffice preview

    A început 23 iunie 2025 la 07:00 UTC · 2d 4h

    IssuesIncident minor
    1. 23 iunie 2025 la 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 iunie 2025 la 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 iunie 2025 la 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 septembrie 2025 la 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.

    Partial Outage of DRACOON Cloud

    A început 31 martie 2025 la 05:30 UTC · 3h 26m

    OutageIncident major
    Componente afectate
    API (group 03)API (group 02)API (group 01)API (group 06)API (group 09)API (group 04)API (group 08)API (group 05)API (group 07)
    1. 31 martie 2025 la 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 martie 2025 la 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 martie 2025 la 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 septembrie 2025 la 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.

    Partial Outage of DRACOON Cloud

    A început 12 martie 2025 la 16:30 UTC · 41m

    Pending
    1. 12 martie 2025 la 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 martie 2025 la 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.