Histórico de interrupções do Dracoon

1. 26 Here 2026 da 09:29 UTCinvestigating

   Atualmente estamos investigando um problema com nossas notificações de email. Nossa equipe está trabalhando para reunir mais informações e resolver o problema o mais rápido possível. Pedimos desculpas por qualquer inconveniente que isso possa causar e forneceremos atualizações assim que as tivermos.

2. 26 Here 2026 da 11:31 UTCinvestigating

   Nossa equipe ainda está trabalhando ativamente para resolver o problema com notificações de Email. Alguns clientes cujas organizações usam certas configurações de servidor de e-mail podem atualmente não receber notificações de e-mail da DRACOON; estamos trabalhando com nosso parceiro de entrega de e-mail para resolver isso o mais rápido possível. Pedimos desculpas por qualquer inconveniente que isso possa causar e apreciar a sua paciência. Forneceremos mais informações e atualizações assim que estiverem disponíveis.

3. 26 Here 2026 da 15:38 UTCmonitoring

   Identificamos o problema com notificações de Email e aplicamos uma correção para resolvê-lo. Estamos a acompanhar a situação para garantir a sua estabilidade e detectar quaisquer outras questões. Nos últimos dias, alguns destinatários podem não ter recebido notificações por e-mail da DRACOON. A maioria das organizações afetadas são as organizações cujo e-mail de entrada passa por certos gateways de segurança de correio corporativo que incluem verificações DNS específicas antes de aceitar e-mails de entrada. A causa raiz foi provavelmente uma questão DNS de terceiros que afeta nosso domínio remetente de notificação. Notificações devem ser entregues normalmente novamente. Estamos monitorando a entrega de perto e vamos postar uma atualização quando o problema estiver totalmente resolvido. Notificações que não foram entregues durante este período não serão ressentidas automaticamente. Pedimos desculpa por qualquer inconveniente que isto possa ter causado e apreciamos a sua paciência.

4. 27 Here 2026 da 07:46 UTCresolved

   O problema com notificações de Email foi totalmente resolvido. Todos os sistemas estão a funcionar normalmente. Pedimos desculpa por qualquer inconveniente que isto possa ter causado e apreciamos a sua paciência. Se você continuar a experimentar quaisquer problemas, por favor, não hesite em contactar nossa equipe de suporte para obter assistência.

5. 27 Here 2026 da 07:49 UTCpostmortem

   **20 - 26 de outubro de 2026: Pós-Morte** Tivemos um problema com notificações por e-mail entre 20 de outubro e 26 de outubro de 2026. Nossa equipe tem trabalhado diligentemente para identificar a causa raiz e implementar uma resolução. Nesta autópsia, queremos partilhar os detalhes do que aconteceu, porque aconteceu, o que fizemos para resolvê-lo e o que faremos para evitar incidentes semelhantes no futuro. O que aconteceu? Durante este período, alguns destinatários não receberam notificações por e-mail da DRACOON. O problema afetou principalmente as organizações cujo e-mail de entrada passa por certos gateways de segurança de email corporativos. Para estes destinatários, muitas notificações foram rejeitadas e não foram entregues. Todas as outras funções do DRACOON não foram afetadas. Por que isso aconteceu? Antes de aceitar um e-mail, alguns gateways de segurança de e-mail verificam se o domínio do remetente é válido. Um serviço DNS operado por um provedor de terceiros começou a dar uma resposta incorreta para parte da configuração do nosso domínio de envio de notificações. Por causa dessa resposta, esses gateways trataram mal nosso domínio remetente como inválido e rejeitaram as notificações. Nossa própria configuração e nosso serviço de entrega de e-mail estavam funcionando corretamente em toda. O que fizemos? Após os primeiros relatórios de clientes, analisamos os registros de entrega junto com nosso parceiro de entrega de e-mail e descobrimos que as rejeições seguiram um padrão claro. Seguimo-los até à questão do DNS de terceiros. Em 26 de outubro, mudamos a configuração do nosso domínio de remetente de notificação para que não mais dependesse do serviço de terceiros afetado. Após a mudança, o parto voltou ao normal, e o monitoramos de perto para confirmar que o problema estava resolvido. ** O que podemos fazer para melhorar?** * Estamos revisando nossas configurações relacionadas ao email para remover dependências de serviços externos. * Estamos melhorando nosso monitoramento da entrega de e-mail, de modo que taxas de rejeição incomuns são detectadas e investigadas mais cedo. Pedimos desculpa por qualquer inconveniente que este incidente possa ter causado. Estamos empenhados em garantir a estabilidade e a fiabilidade dos nossos serviços e continuaremos a tomar medidas proactivas para evitar que incidentes semelhantes aconteçam no futuro. Se tiver alguma dúvida ou preocupação, não hesite em contactar a nossa equipa de apoio para obter assistência.

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Here 2026 da 11:12 UTCresolved

   Estamos cientes das vulnerabilidades de segurança recentemente publicadas CVE-2026-109618 e CVE-2026-109619 que afetam o PHP. A DRACOON não usa PHP e, portanto, não é afetada por essas vulnerabilidades. Nenhuma ação é necessária de sua parte. Continuamos a acompanhar de perto os conselhos de segurança e vamos mantê-lo informado caso esta avaliação mude.

Traduzido automaticamente da atualização oficial do incidente.

1. 6 Eost 2026 da 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 Eost 2026 da 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 Gouere 2026 da 07:51 UTCresolved

   Como resultado de problemas de disponibilidade do nosso fornecedor de datacenters, nós experimentamos uma falha parcial da DRACOON Cloud. Nossos engenheiros foram capazes de resolver as questões a curto prazo, aplicando uma solução alternativa. Esta disponibilidade restaurada e todos os sistemas estavam funcionando normalmente novamente depois. Pedimos desculpa por qualquer inconveniente que isto possa ter causado e apreciamos a sua paciência. Se você continuar a experimentar quaisquer problemas, por favor, não hesite em contactar nossa equipe de suporte para obter assistência.

2. 16 Gouere 2026 da 07:54 UTCpostmortem

   Tivemos um problema com a Dracoon Cloud em 2026-07-16 de cerca de 00:05 a 00:30 CEST. Nossa equipe tem trabalhado diligentemente para identificar a causa raiz e implementar uma resolução. Nesta autópsia, queremos partilhar os detalhes do que aconteceu, porque aconteceu, o que fizemos para resolvê-lo e o que faremos para evitar incidentes semelhantes no futuro. □ O que aconteceu? Nosso provedor de datacenter experimentou problemas de disponibilidade em uma região e zona de disponibilidade, onde algumas de nossas infraestruturas da DRACOON Cloud estão funcionando. Como resultado disso, partes da DRACOON Cloud não estavam disponíveis ou tiveram desempenho degradado durante o tempo do incidente. □ O que fizemos? Nossos engenheiros analisaram a situação e aplicaram uma solução técnica para restaurar totalmente a disponibilidade o mais rápido possível. □ Pedimos desculpa por qualquer inconveniente que este incidente possa ter causado. Estamos empenhados em garantir a estabilidade e a fiabilidade dos nossos serviços e continuaremos a tomar medidas proactivas para evitar que incidentes semelhantes aconteçam no futuro. Se tiver alguma dúvida ou preocupação, não hesite em contactar a nossa equipa de apoio para obter assistência.

Traduzido automaticamente da atualização oficial do incidente.

1. 1 Gouere 2026 da 09:32 UTCinvestigating

   Estamos a investigar um problema com a Dracoon. Nossa equipe está trabalhando para reunir mais informações e resolver o problema o mais rápido possível. Pedimos desculpas por qualquer inconveniente que isso possa causar e forneceremos atualizações assim que as tivermos.

2. 1 Gouere 2026 da 10:11 UTCmonitoring

   A questão com o DRACOON foi resolvida, e estamos a acompanhar a situação para garantir a sua estabilidade. Pedimos desculpa por qualquer inconveniente que isto possa ter causado e apreciamos a sua paciência.

3. 1 Gouere 2026 da 10:26 UTCresolved

   A questão com a Dracoon foi totalmente resolvida. Todos os sistemas estão a funcionar normalmente. Pedimos desculpa por qualquer inconveniente que isto possa ter causado e apreciamos a sua paciência. Se você continuar a experimentar quaisquer problemas, por favor, não hesite em contactar nossa equipe de suporte para obter assistência.

4. 23 Gwengolo 2026 da 09:24 UTCpostmortem

   ** 1 de Julho de 2026, 11:20 - 12:30 CEST** - Pós-Mortem Em 1 de julho de 2026, entre aproximadamente 11:20 e 12:15 CEST, DRACOON Cloud teve um problema que causou uma interrupção temporária do serviço. Nossa equipe tem trabalhado para identificar a causa raiz e colocar uma resolução em vigor. Nesta autópsia, queremos explicar o que aconteceu, por que aconteceu, o que fizemos para resolvê-lo e o que faremos para evitar incidentes semelhantes no futuro. O que aconteceu? Por cerca de 55 minutos, a DRACOON Cloud estava indisponível ou apenas parcialmente disponível para usuários. Após restaurarmos o serviço, mantivemos o monitoramento da plataforma até as 12:30 CEST para garantir que estivesse totalmente estável. Nenhum dado do cliente foi perdido ou comprometido. Por que isso aconteceu? Fizemos uma mudança de configuração planejada para nossa infraestrutura interna de plataforma. O objectivo da mudança era reforçar ainda mais a segurança do nosso ambiente. No entanto, a mudança não se comportou como esperado na produção e afetou a comunicação entre alguns componentes internos da DRACOON Cloud. Isso causou a interrupção do serviço. O que fizemos? Nosso monitoramento nos alertou para o problema, e nossos engenheiros começaram a investigar imediatamente \(11:20 CEST\). Eles rastrearam a interrupção até a recente mudança de configuração e a corrigiram, o que restaurou a comunicação normal entre os componentes afetados. DRACOON Cloud estava totalmente disponível novamente às 12:15 CEST. Seguimos a plataforma para confirmar que estava estável e declaramos o incidente resolvido às 12:30 CEST. ** O que podemos fazer para melhorar?** * Expandiremos nosso teste e validação de pré-produção para mudanças de configuração de infraestrutura para que melhor correspondam às condições reais de produção. * Vamos rolar mudanças deste tipo em passos menores e graduais, para que possamos detectar qualquer comportamento inesperado cedo. * Vamos melhorar nossas verificações automatizadas para encontrar problemas como este mais rápido e permitir um retorno mais rápido. Pedimos desculpa por qualquer inconveniente que este incidente possa ter causado. Estamos empenhados em manter os nossos serviços estáveis e fiáveis e continuaremos a tomar medidas proactivas para evitar incidentes semelhantes no futuro. Se tiver alguma dúvida ou preocupação, não hesite em contactar a nossa equipa de apoio para obter assistência.

Traduzido automaticamente da atualização oficial do incidente.

1. 16 Ebrel 2026 da 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 Ebrel 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 08:51 UTCinvestigating

   We are continuing to investigate this issue.

3. 24 Meurzh 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 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 Genver 2026 da 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 Genver 2026 da 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 Genver 2026 da 10:43 UTCidentified

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

3. 8 Genver 2026 da 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 Du 2025 da 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 Du 2025 da 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 Du 2025 da 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 Du 2025 da 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 Du 2025 da 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 Du 2025 da 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 Du 2025 da 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 Du 2025 da 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 Du 2025 da 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 Eost 2025 da 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 Eost 2025 da 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 Eost 2025 da 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 Gwengolo 2025 da 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 Eost 2025 da 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 Eost 2025 da 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 Gouere 2025 da 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 Gouere 2025 da 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 Gouere 2025 da 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 Gwengolo 2025 da 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 Gouere 2025 da 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 Gouere 2025 da 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 Gouere 2025 da 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 Gwengolo 2025 da 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 Mezheven 2025 da 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 Mezheven 2025 da 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 Mezheven 2025 da 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 Gwengolo 2025 da 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 Meurzh 2025 da 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 Meurzh 2025 da 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 Meurzh 2025 da 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 Gwengolo 2025 da 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 Meurzh 2025 da 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 Meurzh 2025 da 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.