Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Cronologia delle interruzioni di Dracoon

    55 Dracoon incidents · gennaio 2024 — official updates, affected components, duration and resolution details.

    Torna allo stato attuale

    Estrazione parziale delle notifiche via e-mail

    Inizio 26 ottobre 2026 alle ore 09:29 UTC · 22h 18m

    OutageIncidente maggiore
    Componenti interessati
    Instant messagesSubscribed messages
    1. 26 ottobre 2026 alle ore 09:29 UTCinvestigating

      Stiamo attualmente indagando su un problema con le nostre notifiche via email. Il nostro team sta lavorando per raccogliere più informazioni e risolvere il problema il più rapidamente possibile. Ci scusiamo per qualsiasi inconveniente che questo può causare e fornirà aggiornamenti non appena li abbiamo.

    2. 26 ottobre 2026 alle ore 11:31 UTCinvestigating

      Il nostro team sta ancora lavorando attivamente per risolvere il problema con le notifiche via email. Alcuni clienti le cui organizzazioni utilizzano determinate configurazioni di server di posta potrebbero attualmente non ricevere notifiche via e-mail da DRACOON; stiamo lavorando con il nostro partner di consegna e-mail per risolvere questo il più rapidamente possibile. Ci scusiamo per qualsiasi inconveniente che possa causare e apprezzare la vostra pazienza. Forniremo ulteriori informazioni e aggiornamenti non appena saranno disponibili.

    3. 26 ottobre 2026 alle ore 15:38 UTCmonitoring

      Abbiamo identificato il problema con le notifiche e-mail e abbiamo applicato una correzione per risolverlo. Stiamo monitorando la situazione per garantire che rimanga stabile e per rilevare eventuali problemi aggiuntivi. Negli ultimi giorni, alcuni destinatari potrebbero non aver ricevuto notifiche e-mail da DRACOON. Per lo più interessati sono organizzazioni la cui posta in entrata funziona attraverso alcuni gateway di sicurezza della posta aziendale che includono specifici controlli DNS prima di accettare le mail in arrivo. La causa principale era probabilmente un problema DNS di terze parti che interessa il nostro dominio del mittente di notifica. Le notifiche devono essere consegnate di nuovo normalmente. Stiamo monitorando la consegna da vicino e pubblicheremo un aggiornamento una volta che il problema è completamente risolto. Le notifiche che non sono state consegnate durante questo periodo non saranno risentite automaticamente. Ci scusiamo per qualsiasi inconveniente che potrebbe aver causato e apprezzare la vostra pazienza.

    4. 27 ottobre 2026 alle ore 07:46 UTCresolved

      Il problema con le notifiche Email è stato completamente risolto. Tutti i sistemi sono ora operativi normalmente. Ci scusiamo per qualsiasi inconveniente che potrebbe aver causato e apprezzare la vostra pazienza. Se si continua a sperimentare qualsiasi problema, non esitate a raggiungere il nostro team di supporto per l'assistenza.

    5. 27 ottobre 2026 alle ore 07:49 UTCpostmortem

      **20 - 26 ottobre 2026: Post-Mortem** Abbiamo sperimentato un problema con le notifiche e-mail tra il 20 ottobre e il 26 ottobre 2026. Il nostro team ha lavorato diligentemente per identificare la causa principale e implementare una risoluzione. In questo post-mortem, vogliamo condividere i dettagli di ciò che è successo, perché è successo, ciò che abbiamo fatto per risolverlo, e ciò che faremo per prevenire incidenti simili in futuro. Che e' successo? Durante questo periodo, alcuni destinatari non hanno ricevuto notifiche di posta elettronica da DRACOON. Il problema riguardava principalmente le organizzazioni la cui posta in arrivo passa attraverso alcuni gateway di sicurezza e-mail aziendali. Per questi destinatari, molte notifiche sono state respinte e non consegnate. Tutte le altre funzioni DRACOON non sono state influenzate. Perche' e' successo? Prima di accettare una mail, alcuni gateway di sicurezza e-mail controllano che il dominio del mittente è valido. Un servizio DNS gestito da un provider di terze parti ha iniziato a dare una risposta errata per una parte della configurazione del dominio del mittente di notifica. A causa di questa risposta, questi gateway trattati male il nostro dominio mittente come invalido e respinto le notifiche. La nostra configurazione e il nostro servizio di consegna della posta stavano funzionando correttamente in tutto. Cosa abbiamo fatto? Dopo i primi rapporti dei clienti, abbiamo analizzato i registri di consegna insieme al nostro partner di e-mail di consegna e abbiamo scoperto che i rifiuti hanno seguito un modello chiaro. Li abbiamo rintracciati al problema DNS di terze parti. Il 26 ottobre, abbiamo cambiato la configurazione del nostro dominio del mittente di notifica in modo che non dipende più dal servizio di terze parti interessato. Dopo il cambiamento, la consegna è tornata alla normalità, e abbiamo monitorato attentamente per confermare il problema è stato risolto. Cosa possiamo fare per migliorare? * Stiamo rivedendo le nostre configurazioni relative alle email per rimuovere le dipendenze sui servizi esterni. * Stiamo migliorando il nostro monitoraggio della consegna e-mail, in modo che i tassi di rifiuto insoliti vengono rilevati e indagati prima. Ci scusiamo per qualsiasi inconveniente che questo incidente possa aver causato. Ci impegniamo a garantire la stabilità e l'affidabilità dei nostri servizi e continueremo a prendere misure proattive per evitare che avvengano incidenti simili in futuro. Se avete domande o dubbi, non esitate a contattare il nostro team di assistenza.

    Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

    DRACOON non è interessato da CVE-2026-109618 e CVE-2026-109619

    Inizio 22 ottobre 2026 alle ore 11:12 UTC · 0m

    Pending
    1. 22 ottobre 2026 alle ore 11:12 UTCresolved

      Siamo consapevoli delle vulnerabilità di sicurezza recentemente pubblicate CVE-2026-109618 e CVE-2026-109619 che riguardano PHP. DRACOON non utilizza PHP e quindi non è influenzata da queste vulnerabilità. Nessuna azione è richiesta da parte vostra. Continuiamo a monitorare attentamente i consulenti di sicurezza e vi terremo informati se questo cambiamento di valutazione.

    Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

    Partial Outage of DRACOON Cloud Uploads and Downloads

    Inizio 5 agosto 2026 alle ore 21:00 UTC · 12h 55m

    OutageIncidente maggiore
    Componenti interessati
    DownloadUpload
    1. 6 agosto 2026 alle ore 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 agosto 2026 alle ore 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.

    Estrazione parziale di DRACOON Cloud

    Inizio 15 luglio 2026 alle ore 22:05 UTC · 0m

    Pending
    1. 16 luglio 2026 alle ore 07:51 UTCresolved

      Come risultato di problemi di disponibilità del nostro fornitore di datacenter, abbiamo sperimentato un parziale outage di DRACOON Cloud. I nostri ingegneri sono stati in grado di risolvere i problemi a breve termine applicando una soluzione. Questa disponibilità restaurata e tutti i sistemi sono stati operativi di nuovo in seguito. Ci scusiamo per qualsiasi inconveniente che potrebbe aver causato e apprezzare la vostra pazienza. Se si continua a sperimentare qualsiasi problema, non esitate a raggiungere il nostro team di supporto per l'assistenza.

    2. 16 luglio 2026 alle ore 07:54 UTCpostmortem

      Abbiamo sperimentato un problema con DRACOON Cloud il 2026-07-16 da circa 00:05 a 00:30 CEST. Il nostro team ha lavorato diligentemente per identificare la causa principale e implementare una risoluzione. In questo post-mortem, vogliamo condividere i dettagli di ciò che è successo, perché è successo, ciò che abbiamo fatto per risolverlo, e ciò che faremo per prevenire incidenti simili in futuro. Che e' successo? Il nostro fornitore di datacenter ha sperimentato problemi di disponibilità in una regione e zona di disponibilità, dove alcune nostre infrastrutture DRACOON Cloud sono in esecuzione. Di conseguenza, parti di DRACOON Cloud non erano disponibili o avevano declassato le prestazioni durante l'incidente. Cosa abbiamo fatto? I nostri ingegneri hanno analizzato la situazione e applicato una soluzione tecnica per ripristinare completamente la disponibilità il più velocemente possibile. Ci scusiamo per qualsiasi inconveniente che questo incidente possa aver causato. Ci impegniamo a garantire la stabilità e l'affidabilità dei nostri servizi e continueremo a prendere misure proattive per evitare che avvengano incidenti simili in futuro. Se avete domande o dubbi, non esitate a contattare il nostro team di assistenza.

    Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

    Estrazione di DRACOON

    Inizio 1 luglio 2026 alle ore 09:32 UTC · 54m

    OutageIncidente critico
    Componenti interessati
    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 luglio 2026 alle ore 09:32 UTCinvestigating

      Stiamo indagando su un problema con DRACOON. Il nostro team sta lavorando per raccogliere più informazioni e risolvere il problema il più rapidamente possibile. Ci scusiamo per qualsiasi inconveniente che questo può causare e fornirà aggiornamenti non appena li abbiamo.

    2. 1 luglio 2026 alle ore 10:11 UTCmonitoring

      Il problema con DRACOON è stato risolto, e stiamo monitorando la situazione per garantire che rimanga stabile. Ci scusiamo per qualsiasi inconveniente che potrebbe aver causato e apprezzare la vostra pazienza.

    3. 1 luglio 2026 alle ore 10:26 UTCresolved

      Il problema con DRACOON è stato completamente risolto. Tutti i sistemi sono ora operativi normalmente. Ci scusiamo per qualsiasi inconveniente che potrebbe aver causato e apprezzare la vostra pazienza. Se si continua a sperimentare qualsiasi problema, non esitate a raggiungere il nostro team di supporto per l'assistenza.

    4. 23 settembre 2026 alle ore 09:24 UTCpostmortem

      **Luglio 1, 2026, 11:20 – 12:30 CEST** - Post-Mortem Il 1 luglio 2026, tra le 11:20 e le 12:15 CEST, DRACOON Cloud ha avuto un problema che ha causato un'interruzione di servizio temporanea. Il nostro team ha lavorato per identificare la causa principale e mettere in atto una risoluzione. In questo post-mortem, vogliamo spiegare ciò che è successo, perché è successo, ciò che abbiamo fatto per risolverlo, e ciò che faremo per prevenire incidenti simili in futuro. Che e' successo? Per circa 55 minuti, DRACOON Cloud non era disponibile o solo parzialmente disponibile per gli utenti. Dopo aver ripristinato il servizio, abbiamo continuato a monitorare la piattaforma fino alle 12:30 CEST per assicurarsi che fosse completamente stabile. Nessun dato del cliente è stato perso o compromesso. Perche' e' successo? Abbiamo implementato una modifica di configurazione prevista per l'infrastruttura della piattaforma interna. L'obiettivo del cambiamento era di rafforzare ulteriormente la sicurezza del nostro ambiente. Tuttavia, il cambiamento non si è comportato come previsto nella produzione e ha interessato la comunicazione tra alcuni componenti interni di DRACOON Cloud. Ciò ha causato l'interruzione del servizio. Cosa abbiamo fatto? Il nostro monitoraggio ci ha avvisato del problema, e i nostri ingegneri hanno iniziato a indagare subito \(11:20 CEST\). Hanno tracciato l'interruzione di nuovo al cambiamento di configurazione recente e corretto, che ha ripristinato la comunicazione normale tra i componenti colpiti. DRACOON Cloud è stato nuovamente disponibile alle 12:15 CEST. Abbiamo poi monitorato la piattaforma per confermare che era stabile e dichiarato l'incidente risolto alle 12:30 CEST. Cosa possiamo fare per migliorare? * Espanderemo i nostri test di pre-produzione e la validazione per le modifiche di configurazione delle infrastrutture in modo che meglio corrispondano alle condizioni di produzione reali. * Sbolleremo i cambiamenti di questo tipo in passi più piccoli e graduali, in modo da rilevare presto qualsiasi comportamento inaspettato. * miglioreremo i nostri controlli automatizzati per trovare problemi come questo più velocemente e per consentire un rollback più veloce. Ci scusiamo per qualsiasi inconveniente che questo incidente possa aver causato. Ci impegniamo a mantenere i nostri servizi stabili e affidabili e continueremo a prendere misure proattive per prevenire incidenti simili in futuro. Se avete domande o dubbi, non esitate a contattare il nostro team di assistenza.

    Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

    Degraded Performance of Virus Protection

    Inizio 16 aprile 2026 alle ore 11:00 UTC · 9h 57m

    IssuesIncidente minore
    Componenti interessati
    Virus protection
    1. 16 aprile 2026 alle ore 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 aprile 2026 alle ore 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

    Inizio 24 marzo 2026 alle ore 08:30 UTC · 1d 3h

    OutageIncidente maggiore
    Componenti interessati
    Web App
    1. 24 marzo 2026 alle ore 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 marzo 2026 alle ore 08:51 UTCinvestigating

      We are continuing to investigate this issue.

    3. 24 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 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

    Inizio 12 gennaio 2026 alle ore 10:00 UTC · 40m

    OutageIncidente maggiore
    1. 12 gennaio 2026 alle ore 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

    Inizio 8 gennaio 2026 alle ore 10:00 UTC · 45m

    IssuesIncidente minore
    Componenti interessati
    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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 10:43 UTCidentified

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

    3. 8 gennaio 2026 alle ore 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

    Inizio 27 novembre 2025 alle ore 08:30 UTC · 5h 28m

    OutageIncidente critico
    Componenti interessati
    Virus protection
    1. 27 novembre 2025 alle ore 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 novembre 2025 alle ore 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 novembre 2025 alle ore 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 novembre 2025 alle ore 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

    Inizio 20 novembre 2025 alle ore 13:55 UTC · 0m

    IssuesIncidente minore
    1. 20 novembre 2025 alle ore 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

    Inizio 19 novembre 2025 alle ore 08:42 UTC · 2h 45m

    OutageIncidente critico
    Componenti interessati
    Virus protection
    1. 19 novembre 2025 alle ore 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 novembre 2025 alle ore 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 novembre 2025 alle ore 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 novembre 2025 alle ore 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

    Inizio 13 agosto 2025 alle ore 10:00 UTC · 5h 0m

    IssuesIncidente minore
    Componenti interessati
    Virus protection
    1. 13 agosto 2025 alle ore 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 agosto 2025 alle ore 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 agosto 2025 alle ore 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 settembre 2025 alle ore 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)

    Inizio 4 agosto 2025 alle ore 06:58 UTC · 27m

    Pending
    1. 4 agosto 2025 alle ore 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 agosto 2025 alle ore 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

    Inizio 28 luglio 2025 alle ore 07:54 UTC · 1h 51m

    Pending
    1. 28 luglio 2025 alle ore 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 luglio 2025 alle ore 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

    Inizio 12 luglio 2025 alle ore 12:30 UTC · 0m

    IssuesIncidente minore
    1. 16 luglio 2025 alle ore 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 settembre 2025 alle ore 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

    Inizio 7 luglio 2025 alle ore 10:05 UTC · 1h 5m

    OutageIncidente maggiore
    Componenti interessati
    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 luglio 2025 alle ore 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 luglio 2025 alle ore 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 luglio 2025 alle ore 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 settembre 2025 alle ore 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

    Inizio 23 giugno 2025 alle ore 07:00 UTC · 2d 4h

    IssuesIncidente minore
    1. 23 giugno 2025 alle ore 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 giugno 2025 alle ore 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 giugno 2025 alle ore 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 settembre 2025 alle ore 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

    Inizio 31 marzo 2025 alle ore 05:30 UTC · 3h 26m

    OutageIncidente maggiore
    Componenti interessati
    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 marzo 2025 alle ore 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 marzo 2025 alle ore 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 marzo 2025 alle ore 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 settembre 2025 alle ore 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

    Inizio 12 marzo 2025 alle ore 16:30 UTC · 41m

    Pending
    1. 12 marzo 2025 alle ore 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 marzo 2025 alle ore 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.