Historial de interrupciones de Dracoon

1. 26 de octubre de 2026 a las 9:29 UTCinvestigating

   Actualmente estamos investigando un problema con nuestras notificaciones de Email. Nuestro equipo está trabajando para reunir más información y resolver el problema lo antes posible. Nos disculpamos por cualquier inconveniente que esto pueda causar y proporcionará actualizaciones tan pronto como los tengamos.

2. 26 de octubre de 2026 a las 11:31 UTCinvestigating

   Nuestro equipo sigue trabajando activamente para resolver el problema con notificaciones de correo electrónico. Algunos clientes cuyas organizaciones utilizan ciertas configuraciones del servidor de correos pueden no recibir notificaciones de correo electrónico de DRACOON; estamos trabajando con nuestro socio de correo electrónico para resolver esto lo más rápido posible. Nos disculpamos por cualquier inconveniente que esto pueda causar y apreciar su paciencia. Proporcionaremos más información y actualizaciones tan pronto como estén disponibles.

3. 26 de octubre de 2026 a las 15:38 UTCmonitoring

   Identificamos el problema con notificaciones de correo electrónico y aplicamos una solución para resolverlo. Estamos monitoreando la situación para asegurar que siga estable y para detectar cualquier problema adicional. En los últimos días, algunos receptores pueden no haber recibido notificaciones por correo electrónico de DRACOON. La mayoría de los afectados son organizaciones cuyo correo entrante corre a través de ciertos portales de seguridad de correo corporativo que incluyen cheques DNS específicos antes de aceptar correos entrantes. La causa raíz era muy probable que una emisión DNS de terceros afectara nuestro dominio del remitente de notificación. Las notificaciones deben enviarse normalmente de nuevo. Estamos monitoreando la entrega de cerca y publicaremos una actualización una vez que la cuestión esté totalmente resuelta. Las notificaciones que no fueron entregadas durante este período no serán resentidas automáticamente. Nos disculpamos por cualquier inconveniente que esto pueda haber causado y apreciar su paciencia.

Traducido automáticamente desde la actualización oficial del incidente.

1. 22 de octubre de 2026 a las 11:12 UTCresolved

   Somos conscientes de las vulnerabilidades de seguridad publicadas recientemente CVE-2026-109618 y CVE-2026-109619 que afectan a PHP. DRACOON no utiliza PHP y por lo tanto no se ve afectada por estas vulnerabilidades. No se requiere acción por su parte. Seguimos monitoreando de cerca las asesorías de seguridad y le mantendremos informado si este cambio de evaluación.

Traducido automáticamente desde la actualización oficial del incidente.

1. 6 de agosto de 2026 a las 9:54 UTCinvestigating

   Hemos identificado un problema con subidas y descargas en DRACOON Cloud. Nuestros ingenieros están trabajando en una resolución y estamos seguros de que tendremos una solución pronto. Proporcionaremos más información y actualizaciones tan pronto como estén disponibles.

2. 6 de agosto de 2026 a las 9:55 UTCresolved

   El problema con cargas y descargas en DRACOON Cloud se ha resuelto completamente. Todos los sistemas están operando normalmente. Nos disculpamos por cualquier inconveniente que esto pueda haber causado y apreciar su paciencia. Si sigues experimentando algún problema, por favor no dudes en contactar con nuestro equipo de apoyo para recibir asistencia.

Traducido automáticamente desde la actualización oficial del incidente.

1. 16 de julio de 2026 a las 7:51 UTCresolved

   Como resultado de los problemas de disponibilidad de nuestro proveedor de datos, experimentamos una pérdida parcial de DRACOON Cloud. Nuestros ingenieros pudieron resolver los problemas a corto plazo aplicando una solución de trabajo. Esta disponibilidad restaurada y todos los sistemas funcionaban normalmente después. Nos disculpamos por cualquier inconveniente que esto pueda haber causado y apreciar su paciencia. Si sigues experimentando algún problema, por favor no dudes en contactar con nuestro equipo de apoyo para recibir asistencia.

2. 16 de julio de 2026 a las 7:54 UTCpostmortem

   Experimentamos un problema con DRACOON Cloud en 2026-07-16 de alrededor de 00:05 a 00:30 CEST. Nuestro equipo ha trabajado diligentemente para identificar la causa raíz y aplicar una resolución. En esta post-mortem, queremos compartir los detalles de lo que pasó, por qué sucedió, lo que hicimos para resolverlo, y lo que haremos para evitar incidentes similares en el futuro. ¿Qué pasó? Nuestro proveedor de datos experimentó problemas de disponibilidad en una región y zona de disponibilidad, donde se está ejecutando alguna infraestructura de DRACOON Cloud. As a result of that, parts of DRACOON Cloud were unavailable or had degraded performance during the time of the incident. ¿Qué hicimos? Nuestros ingenieros analizaron la situación y aplicaron una solución técnica para restaurar la disponibilidad lo más rápido posible. Nos disculpamos por cualquier inconveniente que este incidente pueda haber causado. Nos comprometemos a garantizar la estabilidad y fiabilidad de nuestros servicios y seguiremos adoptando medidas proactivas para evitar que ocurran incidentes similares en el futuro. Si tiene alguna pregunta o preocupación, por favor no dude en contactar con nuestro equipo de apoyo para recibir asistencia.

Traducido automáticamente desde la actualización oficial del incidente.

1. 1 de julio de 2026 a las 9:32 UTCinvestigating

   Actualmente estamos investigando un problema con DRACOON. Nuestro equipo está trabajando para reunir más información y resolver el problema lo antes posible. Nos disculpamos por cualquier inconveniente que esto pueda causar y proporcionará actualizaciones tan pronto como los tengamos.

2. 1 de julio de 2026 a las 10:11 UTCmonitoring

   Se ha resuelto la cuestión con el DRACOON y estamos monitoreando la situación para asegurar que siga siendo estable. Nos disculpamos por cualquier inconveniente que esto pueda haber causado y apreciar su paciencia.

3. 1 de julio de 2026 a las 10:26 UTCresolved

   La cuestión con DRACOON se ha resuelto plenamente. Todos los sistemas están operando normalmente. Nos disculpamos por cualquier inconveniente que esto pueda haber causado y apreciar su paciencia. Si sigues experimentando algún problema, por favor no dudes en contactar con nuestro equipo de apoyo para recibir asistencia.

4. 23 de septiembre de 2026 a las 9:24 UTCpostmortem

   **Julio 1, 2026, 11:20 – 12:30 CEST** - Post-Mortem El 1 de julio de 2026, entre aproximadamente 11:20 y 12:15 CEST, DRACOON Cloud tenía un problema que causó una interrupción temporal del servicio. Nuestro equipo ha trabajado para identificar la causa raíz y poner en marcha una resolución. En esta post-mortem, queremos explicar lo que sucedió, por qué sucedió, lo que hicimos para resolverlo, y lo que haremos para evitar incidentes similares en el futuro. ¿Qué pasó? Durante unos 55 minutos, DRACOON Cloud no estaba disponible o sólo parcialmente disponible para los usuarios. Después de restaurar el servicio, seguimos monitoreando la plataforma hasta las 12:30 CEST para asegurarnos de que fuera totalmente estable. No se perdieron ni se comprometieron datos de clientes. ¿Por qué sucedió esto? Realizamos un cambio de configuración previsto en nuestra infraestructura de plataforma interna. El objetivo del cambio era fortalecer aún más la seguridad de nuestro medio ambiente. Sin embargo, el cambio no se comportaba como se esperaba en la producción y afectaba la comunicación entre algunos componentes internos de DRACOON Cloud. Esto causó la interrupción del servicio. ¿Qué hicimos? Nuestro monitoreo nos alertó sobre el problema, y nuestros ingenieros comenzaron a investigar de inmediato \(11:20 CEST\). Trazaron la interrupción de nuevo al cambio de configuración reciente y lo corrigieron, que restauró la comunicación normal entre los componentes afectados. DRACOON Cloud estaba completamente disponible de nuevo a las 12:15 CEST. Luego monitoreamos la plataforma para confirmar que era estable y declaramos el incidente resuelto a las 12:30 CEST. **¿Qué podemos hacer para mejorar?** * Ampliaremos nuestras pruebas de preproducción y validación para los cambios de configuración de infraestructura para que coincidan mejor con las condiciones de producción reales. * Examinaremos cambios de este tipo en pasos más pequeños y graduales, para que detectemos cualquier comportamiento inesperado temprano. * Mejoraremos nuestros cheques automatizados para encontrar problemas como este más rápido y permitir un retroceso más rápido. Nos disculpamos por cualquier inconveniente que este incidente pueda haber causado. Nos comprometemos a mantener nuestros servicios estables y fiables y seguiremos adoptando medidas proactivas para prevenir incidentes similares en el futuro. Si tiene alguna pregunta o preocupación, por favor no dude en contactar con nuestro equipo de apoyo para recibir asistencia.

Traducido automáticamente desde la actualización oficial del incidente.

1. 16 de abril de 2026 a las 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 de abril de 2026 a las 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 de marzo de 2026 a las 8: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 de marzo de 2026 a las 8:51 UTCinvestigating

   We are continuing to investigate this issue.

3. 24 de marzo de 2026 a las 9: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 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de enero de 2026 a las 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 de enero de 2026 a las 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 de enero de 2026 a las 10:43 UTCidentified

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

3. 8 de enero de 2026 a las 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 de noviembre de 2025 a las 8: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 de noviembre de 2025 a las 8: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 de noviembre de 2025 a las 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 de noviembre de 2025 a las 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 de noviembre de 2025 a las 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 de noviembre de 2025 a las 8: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 de noviembre de 2025 a las 9: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 de noviembre de 2025 a las 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 de noviembre de 2025 a las 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 de agosto de 2025 a las 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 de agosto de 2025 a las 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 de agosto de 2025 a las 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 de septiembre de 2025 a las 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 de agosto de 2025 a las 6: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 de agosto de 2025 a las 7: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 de julio de 2025 a las 7: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 de julio de 2025 a las 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 de julio de 2025 a las 7: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 de septiembre de 2025 a las 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 de julio de 2025 a las 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 de julio de 2025 a las 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 de julio de 2025 a las 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 de septiembre de 2025 a las 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 de junio de 2025 a las 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 de junio de 2025 a las 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 de junio de 2025 a las 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 de septiembre de 2025 a las 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 de marzo de 2025 a las 6: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 de marzo de 2025 a las 6: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 de marzo de 2025 a las 8: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 de septiembre de 2025 a las 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 de marzo de 2025 a las 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 de marzo de 2025 a las 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.