Historial de interrupciones de Samanage

1. 8 de septiembre de 2026 a las 14:27 UTCinvestigating

   Actualmente estamos experimentando retrasos en la visualización de información actualizada en toda la plataforma. Billetes nuevos y actualizados, comentarios, cambios de incidentes y actualizaciones de campo, como cambios de estado y título, pueden tardar más de lo esperado para aparecer o pueden mostrar temporalmente información obsoleta. Los tiempos de carga de página también pueden ser afectados. Nuestro equipo ha identificado el tema y está trabajando para resolverlo. Algunos retrasos pueden continuar mientras hacemos la solución a través de la plataforma.

2. 8 de septiembre de 2026 a las 15:25 UTCmonitoring

   La solución ha sido implementada, y estamos trabajando activamente a través de la acumulación restante de actualizaciones de tickets. Algunas actualizaciones pueden seguir atrasadas mientras se está procesando, pero esperamos que las demoras se reduzcan a medida que se despeja el atraso. Seguiremos monitorizando el sistema y proporcionaremos actualizaciones adicionales a medida que avance el procesamiento.

3. 8 de septiembre de 2026 a las 16:16 UTCresolved

   Este incidente ha sido resuelto.

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

1. 31 de agosto de 2026 a las 15:15 UTCidentified

   Actualmente estamos experimentando retrasos en la información actualizada que se muestra en la plataforma. Billetes nuevos y actualizados, comentarios, cambios de incidentes y actualizaciones de campo, como estado y título, y otras funciones, a veces son lentos para actualizar o mostrar información obsoleta. También estamos viendo tiempos de carga de página siendo impactados. El equipo ha identificado la cuestión y está trabajando en una resolución. Usted puede experimentar algunos retrasos a medida que desenrollamos la solución a través de la plataforma.

2. 31 de agosto de 2026 a las 15:58 UTCmonitoring

   La solución ha sido implementada, y estamos procesando activamente el atraso restante de actualizaciones de tickets. Mientras se está procesando, algunas actualizaciones de tickets pueden seguir experimentando retrasos. Esperamos que estos retrasos se resuelvan a medida que se despeja el atraso. Seguiremos vigilando el sistema y proporcionaremos nuevas actualizaciones a medida que avance el procesamiento.

3. 31 de agosto de 2026 a las 16:50 UTCmonitoring

   Estamos viendo mejoras tras el despliegue de la solución; estamos monitoreando activamente el sistema para asegurar que el rendimiento siga siendo estable y que todas las actualizaciones retrasadas se procesan completamente.

4. 31 de agosto de 2026 a las 17:42 UTCresolved

   Este incidente ha sido resuelto.

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

1. 14 de julio de 2026 a las 14:30 UTCinvestigating

   Actualmente estamos investigando un problema que afecta a SolarWinds Service Desk. Algunos usuarios pueden ser incapaces de acceder a la aplicación en este momento. Nuestro equipo está trabajando activamente para identificar la causa y restaurar el servicio lo más rápido posible. Compartiremos otra actualización tan pronto como esté disponible más información.

2. 14 de julio de 2026 a las 14:44 UTCinvestigating

   Seguimos investigando esta cuestión.

3. 14 de julio de 2026 a las 14:57 UTCinvestigating

   La aplicación es accesible de nuevo, y el servicio ha sido restaurado. Nuestro equipo sigue vigilando de cerca la aplicación para garantizar la estabilidad. Proporcionaremos otra actualización si se identifican otras cuestiones.

4. 14 de julio de 2026 a las 15:05 UTCmonitoring

   Nuestro equipo sigue vigilando de cerca la aplicación para garantizar la estabilidad. Se compartirán más actualizaciones tan pronto como estén disponibles.

5. 14 de julio de 2026 a las 16:01 UTCresolved

   Después de un largo período de monitoreo, SolarWinds Service Desk está operando normalmente. En este momento, consideramos el incidente resuelto. El análisis de la causa raíz (RCA) se compartirá en los próximos días una vez que la investigación esté completa. Si necesita cualquier asistencia o experiencia adicional, póngase en contacto con nosotros en [email protected].

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

1. 7 de julio de 2026 a las 15:59 UTCidentified

   Actualmente estamos investigando un problema que afecta a SolarWinds Service Desk, donde los incidentes creados por correo electrónico están siendo enviados con éxito, y se envían mensajes de confirmación, pero los incidentes recién creados pueden no aparecer en la página del índice de incidentes. Nuestro equipo está trabajando activamente para identificar la causa raíz y restaurar la visibilidad normal lo antes posible. Proporcionaremos otra actualización tan pronto como se disponga de más información.

2. 7 de julio de 2026 a las 16:23 UTCinvestigating

   Seguimos investigando un problema en la oficina de servicio de SolarWinds, donde no pueden aparecer nuevos incidentes en la página del índice de incidentes, a pesar de ser enviados con éxito y generar mensajes de confirmación. Nuestro equipo está trabajando para identificar la causa y restaurar la visibilidad normal. Compartiremos otra actualización tan pronto como esté disponible más información.

3. 7 de julio de 2026 a las 16:57 UTCidentified

   Hemos identificado la causa raíz de la cuestión que afecta a SolarWinds Service Desk, donde pueden no aparecer nuevos incidentes en la página del índice de incidentes a pesar de ser presentados con éxito. Compartiremos otra actualización tan pronto como se disponga de más información.

4. 7 de julio de 2026 a las 18:00 UTCmonitoring

   Se ha implementado una solución para remediar la cuestión que afecta a SolarWinds Service Desk, donde pueden no aparecer nuevos incidentes en la página del índice de incidentes a pesar de ser creados con éxito. Seguimos monitoreando el servicio de cerca para asegurar que se restablezca la visibilidad normal.

5. 7 de julio de 2026 a las 19:00 UTCresolved

   Después de un largo período de monitoreo, SolarWinds Service Desk está operando normalmente. En este momento, consideramos el incidente resuelto. Si necesita cualquier asistencia o experiencia adicional, póngase en contacto con nosotros en [email protected].

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

1. 30 de junio de 2026 a las 17:22 UTCinvestigating

   Actualmente estamos investigando un problema que afecta a SolarWinds Service Desk donde se envían con éxito incidentes creados por correo electrónico y se envían mensajes de confirmación, pero los incidentes recién creados pueden no aparecer en la página del índice de incidentes. Nuestro equipo está trabajando activamente para identificar la causa y restaurar la visibilidad normal lo antes posible. Compartiremos otra actualización tan pronto como se disponga de más información.

2. 30 de junio de 2026 a las 17:58 UTCidentified

   Hemos identificado la causa del problema reportado y estamos trabajando en una solución lo más rápido posible. Gracias por su paciencia.

3. 30 de junio de 2026 a las 18:09 UTCmonitoring

   Hemos completado la solución para esta cuestión y los servicios están volviendo a la normalidad. Los incidentes enviados a través del correo electrónico ahora deben aparecer correctamente en la página del índice de incidentes como se esperaba. Nuestro equipo seguirá vigilando estrechamente el medio ambiente para garantizar la estabilidad y confirmar que la cuestión se ha resuelto plenamente. Apreciamos su paciencia mientras trabajamos para abordar este problema.

4. 30 de junio de 2026 a las 19:47 UTCmonitoring

   Continuamos monitoreando el comportamiento de cerca mientras nuestro equipo trabaja para confirmar la visibilidad constante en la lista de incidentes. Compartiremos otra actualización tan pronto como se disponga de más información.

5. 30 de junio de 2026 a las 21:04 UTCmonitoring

   Estamos viendo mejoras en el rendimiento general de la aplicación. Nuestro equipo sigue vigilando estrechamente el medio ambiente para garantizar la estabilidad y confirmar que no se plantean nuevas cuestiones. Compartiremos actualizaciones adicionales según sea necesario.

6. 30 de junio de 2026 a las 22:02 UTCresolved

   Después de un largo período de vigilancia, la cuestión no se ha reanimado y no hemos recibido ningún informe adicional de impacto. El servicio funciona normalmente, y estamos considerando este incidente resuelto. Si continúa experimentando cualquier problema o necesita más asistencia, póngase en contacto con nosotros por correo electrónico a [email protected], y nuestro equipo estará encantado de ayudar.

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

1. 23 de junio de 2026 a las 16:14 UTCinvestigating

   Actualmente estamos investigando un problema en el que los incidentes creados a través del correo electrónico no pueden aparecer inmediatamente en la lista de incidentes en el servicio SolarWinds UI. Durante nuestro examen, confirmamos que las notificaciones de creación de incidentes se envían con éxito, y los incidentes afectados se pueden acceder a través de sus vínculos directos. Sin embargo, puede haber un retraso antes de que esos incidentes sean visibles en la lista de incidentes dentro de la UI. Nuestro equipo está investigando activamente este comportamiento y trabajando para determinar la causa. Compartiremos otra actualización tan pronto como se disponga de más información.

2. 23 de junio de 2026 a las 16:37 UTCmonitoring

   Actualmente estamos monitoreando esta cuestión. Nuestra investigación confirmó que la creación de incidentes está ocurriendo con éxito y los correos electrónicos de notificación se envían según lo previsto. Sin embargo, algunos incidentes creados a través del correo electrónico no pueden aparecer inmediatamente en la lista de incidentes dentro de la UI, aunque siguen siendo accesibles a través del enlace directo incluido en el correo electrónico de notificación. Continuamos monitoreando el comportamiento de cerca mientras nuestro equipo trabaja para confirmar la visibilidad constante en la lista de incidentes. Compartiremos otra actualización tan pronto como se disponga de más información.

3. 23 de junio de 2026 a las 18:31 UTCresolved

   Nuestra vigilancia indica que se ha resuelto la cuestión que impacta la visibilidad de los incidentes. Hemos seguido vigilando de cerca el servicio y no hemos observado ningún nuevo problema. En este momento, consideramos el incidente resuelto. Si necesita cualquier asistencia o experiencia adicional, póngase en contacto con nosotros en [email protected].

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

1. 3 de junio de 2026 a las 12:18 UTCinvestigating

   We are currently investigating reports of slow performance issues in SolarWinds Service Desk. Our team is working to resolve this as quickly as possible.

2. 3 de junio de 2026 a las 13:03 UTCidentified

   We have identified the cause of the reported issue and are actively working to implement a fix as quickly as possible. Thank you for your patience and understanding while we work toward a resolution.

3. 3 de junio de 2026 a las 13:32 UTCmonitoring

   We are seeing improved performance on our end and are continuing to monitor the situation closely. We are also working to confirm whether customers are experiencing similar improvements as we continue our efforts to ensure full service stability. We appreciate your patience and understanding during this time. We will provide another update as soon as additional information becomes available.

4. 3 de junio de 2026 a las 14:26 UTCresolved

   We have continued to monitor the service and have not observed any further issues. In addition, we have not received any new reports of slow performance. Based on our monitoring and the current system status, this incident is considered resolved. Should you require any further assistance or experience any additional issues, please do not hesitate to contact us at [email protected]. Thank you for your patience and cooperation throughout this process.

1. 6 de mayo de 2026 a las 13:23 UTCinvestigating

   We are aware of an issue that caused the application to be unavailable for a few minutes. Our team is currently investigating the cause and monitoring the service to ensure it remains stable. Further updates will be posted here as more information becomes available.

2. 6 de mayo de 2026 a las 13:53 UTCmonitoring

   The services are currently operating normally, and our engineering team is closely monitoring system performance to ensure continued stability. We will provide additional updates here if we observe any further impact or if additional action is required.

3. 6 de mayo de 2026 a las 15:25 UTCresolved

   Following an extended monitoring period, the issue has not reappeared, and no further impact has been reported. Services are operating normally, and we consider this incident resolved. If you experience any additional issues or need assistance, please contact us at [email protected], and our team will be glad to help.

1. 29 de abril de 2026 a las 19:01 UTCinvestigating

   We are aware of an issue that caused the application to be unavailable for approximately two minutes. Our team is currently investigating the cause and monitoring the service to ensure it remains stable. Further updates will be posted here as more information becomes available.

2. 29 de abril de 2026 a las 19:08 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 de abril de 2026 a las 19:56 UTCmonitoring

   The services are currently operating normally, and our engineering team is closely monitoring system performance to ensure continued stability. We will provide additional updates here if we observe any further impact or if additional action is required.

4. 29 de abril de 2026 a las 23:28 UTCresolved

   After an extended period of monitoring, the issue has not resurfaced and we have not received any additional reports of impact. Service is operating normally and we are considering this incident resolved. If you continue to experience any issues or need further assistance, please contact us via email at [email protected], and our team will be happy to help.

1. 3 de abril de 2026 a las 12:33 UTCinvestigating

   We are currently investigating reports of slow performance and intermittent Error 500 issues in SolarWinds Service Desk. Our team is working to resolve this as quickly as possible.

2. 3 de abril de 2026 a las 13:00 UTCidentified

   We've identified the cause of the reported issue and are working on a fix as quickly as possible. Thank you for your patience.

3. 3 de abril de 2026 a las 13:42 UTCmonitoring

   We have completed the fix for this issue and will continue to monitor the situation to ensure stability.

4. 3 de abril de 2026 a las 15:08 UTCinvestigating

   We have observed unexpected behavior following the recent fix and are currently reviewing the issue. Our team is continuing to investigate while working to ensure full stability. We appreciate your patience and will provide further updates as soon as more information becomes available.

5. 3 de abril de 2026 a las 16:29 UTCinvestigating

   We are actively investigating continued unexpected behavior following a recent fix. Our team is working to ensure full stability. We appreciate your patience and will share another update as soon as more information is available.

6. 3 de abril de 2026 a las 17:56 UTCmonitoring

   We are seeing improved results on our end and are continuing to monitor performance closely. We are also working to confirm whether customers are seeing similar improvement while we continue to ensure full stability. We appreciate your patience and will provide another update as soon as more information becomes available.

7. 3 de abril de 2026 a las 21:57 UTCresolved

   We have continued to monitor the service and have not observed any further issues. Additionally, we have not received any new reports of slow performance or Error 500 errors. At this time, the incident is considered resolved. If further assistance is needed, please contact [email protected]. Thank you for your patience throughout this process.

1. 18 de marzo de 2026 a las 9:14 UTCinvestigating

   We have received reports of overlapping text fields in Incident/Service Request tickets and are currently investigating the issue.

2. 18 de marzo de 2026 a las 9:46 UTCidentified

   We have identified the cause of the overlapping text fields and are currently working on a fix. We will provide updates as soon as progress is made. Thank you for your patience and understanding.

3. 18 de marzo de 2026 a las 11:52 UTCidentified

   We are still working on fixing the issue. We will continue to monitor the situation and provide updates as they become available.

4. 18 de marzo de 2026 a las 11:57 UTCidentified

   We will deploy a fix shortly. We will provide an update once it has been deployed.

5. 18 de marzo de 2026 a las 12:26 UTCidentified

   We are in the process of deploying the fix. We will keep you updated as progress continues.

6. 18 de marzo de 2026 a las 12:47 UTCmonitoring

   We have completed the deployment of the fix for this issue and will continue to monitor the situation to ensure stability.

7. 18 de marzo de 2026 a las 13:30 UTCresolved

   This issue has been resolved.

1. 2 de febrero de 2026 a las 15:49 UTCinvestigating

   We are currently experiencing performance issues in the Service Desk Application, and our team is investigating. This impacts actions such as navigating through the Incidents page and other areas of the app.

2. 2 de febrero de 2026 a las 16:21 UTCinvestigating

   We have identified elevated load on the database layer in our US Service Desk environment. This is leading to slow page loads, delayed data population, and intermittent 504 Gateway Timeout errors for some customers. Our team is actively working on remediation to reduce database load and restore normal performance. During this time, the application may run more slowly than normal. We will provide the next update within 30 minutes or sooner as we make progress.

3. 2 de febrero de 2026 a las 16:50 UTCidentified

   We are still actively working on reducing the elevated database load in our US Service Desk environment. The underlying issue has been identified, and our team is continuing remediation efforts to stabilize performance.

4. 2 de febrero de 2026 a las 17:26 UTCidentified

   We are continuing to work on a fix for this issue and further reducing the elevated database load in our US Service Desk environment. Some users may still experience intermittent slowness or timeouts while we complete these changes. We will provide another update within 30 minutes or as soon as we have more information.

5. 2 de febrero de 2026 a las 18:19 UTCmonitoring

   We have implemented a fix for the database load issue affecting our US Service Desk environment; we are restarting a set of frontend services to complete remediation. Users should now begin to see improved performance and fewer timeouts as these changes take effect. Our team will continue to closely monitor the environment and will provide another update once performance is fully stabilized.

6. 2 de febrero de 2026 a las 18:55 UTCresolved

   We have resolved the database load issue affecting our US Service Desk environment and restarted the impacted frontend services. Since then, performance has remained stable under monitoring, and we are no longer observing elevated errors or timeouts. This incident is now closed. If you continue to experience slowness or errors, please contact SolarWinds Support or open a ticket so we can investigate further.

1. 28 de enero de 2026 a las 19:54 UTCinvestigating

   We are investigating an issue where some users are unable to fully load service (catalog) requests. Affected pages may briefly appear and then show blank or incomplete content. Our engineering team is actively investigating the cause and working to restore full functionality. We will provide updates on this page as more information becomes available. If you are impacted and need assistance, please contact SolarWinds Support through your usual channels.

2. 28 de enero de 2026 a las 20:08 UTCinvestigating

   We are continuing to investigate this issue.

3. 28 de enero de 2026 a las 20:43 UTCinvestigating

   Our investigation has determined that this issue is limited to a subset of Service Desk service requests and service catalog items and does not affect all users or all catalogs. We are continuing to investigate the underlying cause and will provide additional updates on this page as our work progresses.

4. 28 de enero de 2026 a las 21:29 UTCidentified

   We have identified the root cause of the issue. It occurs when a process workflow includes a Send Notification action that sends an email to a user or email address that does not have a valid user account within the affected Service Desk instance. Our engineering team is actively working on a fix. Additional updates will be provided on this page as progress continues.

5. 28 de enero de 2026 a las 23:17 UTCidentified

   We are actively working on a fix for this issue. As a reminder, the cause occurs when a process workflow includes a Send Notification action that sends an email to a user or email address that does not have a valid user account in the affected Service Desk instance. As a temporary workaround, service desk administrators can update the affected workflows so that Send Notification actions are configured to send emails to a named user with a valid Service Desk account instead of an email address that is not associated with a user. We will provide further updates on this page as our work progresses.

6. 29 de enero de 2026 a las 1:41 UTCidentified

   Our engineering team has prepared a fix for this issue, and the deployment process has started. During the deployment window, some users may experience brief slowdowns or intermittent delays; we expect any impact to be minimal and temporary. We will provide a further update on this page once the deployment has finished.

7. 29 de enero de 2026 a las 3:30 UTCmonitoring

   Our Engineering team has successfully applied a fix and is applying it retroactively to resolve the issue for all affected users. Any interruptions during this process should be minimal. We will provide another update in the next hour.

8. 29 de enero de 2026 a las 5:38 UTCmonitoring

   Our Engineering team is continuously working on applying a fix to the data for all affected users. Further updates will be provided in the next hour.

9. 29 de enero de 2026 a las 8:19 UTCmonitoring

   Our Engineering team is actively deploying a remediation to address issues resulting in page load failures, blank pages, or incomplete content. Further updates will be provided as progress continues.

10. 29 de enero de 2026 a las 11:05 UTCmonitoring

    Our team is in the final stages of deploying the fix. We expect completion shortly and will share an update immediately.

11. 29 de enero de 2026 a las 11:28 UTCmonitoring

    The fix deployment is now complete, and our team is closely monitoring the results to ensure stability.

12. 29 de enero de 2026 a las 14:12 UTCresolved

    We are marking this issue as resolved, as we have confirmed that all new service requests work correctly and previously submitted requests work as intended. If the issue resurfaces or if you require any further assistance, please don’t hesitate to contact us at [email protected].

1. 27 de enero de 2026 a las 18:51 UTCinvestigating

   We are currently investigating an issue affecting Service Requests for customers in the US and AU regions. Initial findings indicate that when the approval process is configured to use the Incident Assignee as the approver, the workflow may terminate unexpectedly with the following error: “The task [Task Name] has been automatically declined per predefined approval conditions because the approval step contains unknown approvers.” Our engineering teams are actively working to identify the root cause and determine a resolution. If you have questions, are experiencing related issues, or would like to provide additional details, please contact us via chat or email at [email protected]. We will continue to provide updates as more information becomes available.

2. 27 de enero de 2026 a las 19:48 UTCinvestigating

   Our team is actively investigating the issue, which may be related to a recent deployment. We are working to identify the root cause and resolve it, and we will provide updates as more information becomes available. Thank you for your patience.

3. 27 de enero de 2026 a las 21:49 UTCinvestigating

   Our team is continuing to investigate the issue and is focused on identifying the root cause and resolving it as quickly as possible. We will provide updates as new details become available. Thank you for your patience.

4. 27 de enero de 2026 a las 23:13 UTCidentified

   We have identified the root cause of the issue affecting Service Request approval workflows for customers in the US and AU regions. We are currently testing a fix. Once testing is complete, we will proceed with deployment and share further updates.

5. 28 de enero de 2026 a las 3:44 UTCidentified

   The fix we had in place did not resolve the issue as expected. Our Engineering team has identified and is currently working on a resolution. Our team is preparing for the deployment, which is expected to be completed within the next hour. If this changes, we will provide an update immediately.

6. 28 de enero de 2026 a las 4:49 UTCresolved

   This issue has been resolved.

1. 27 de enero de 2026 a las 0:03 UTCinvestigating

   We are currently investigating an issue affecting the Service Desk in the AU Data Center, where newly created objects, such as tickets and assets, are not appearing in the user interface as expected. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.

2. 27 de enero de 2026 a las 1:23 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 27 de enero de 2026 a las 2:09 UTCresolved

   This incident has been resolved.

1. 12 de enero de 2026 a las 19:49 UTCinvestigating

   We are currently seeing performance slowness within the Service Desk Application, and our team is investigating this matter. This impacts actions such as navigating through the Incidents page and other areas of the app.

2. 12 de enero de 2026 a las 22:55 UTCinvestigating

   The platform performance has greatly improved, and while that is the case, we are still seeing delays, at times, when navigating between pages. The engineering team found a high load on the database, which has been cleared for a couple of hours, and are now focusing efforts on the remaining delay issues. You can expect the next update in one hour.

3. 13 de enero de 2026 a las 2:23 UTCresolved

   This issue has been resolved.

1. 12 de enero de 2026 a las 7:43 UTCinvestigating

   We are currently investigating an issue affecting the Service Desk in the AU Data Center. New tickets are not appearing in the UI. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.

2. 12 de enero de 2026 a las 12:28 UTCresolved

   This issue has been resolved.

1. 9 de enero de 2026 a las 9:27 UTCinvestigating

   We are aware of an issue affecting a scheduled Service Desk service catalog item in our EU data center. Our team is actively working to identify the root cause and restore normal functionality. Additional updates will be shared as they become available.

2. 9 de enero de 2026 a las 9:36 UTCidentified

   Additional resources have been allocated to help manage the queue. As a result, the backlog is now being processed efficiently, and pending items are getting cleared. Additional updates will be shared as they become available.

3. 9 de enero de 2026 a las 10:09 UTCmonitoring

   Scheduled service catalog item are now being processed. We are monitoring the situation closely to ensure continued stability.

4. 9 de enero de 2026 a las 11:00 UTCresolved

   This incident has been resolved.

1. 6 de enero de 2026 a las 10:47 UTCinvestigating

   We are currently investigating an issue affecting Service Desk in EU Data Center. Round-robin assignment and Automation Rules process are delayed, this affects automation assigning and or updating incidents. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.

2. 6 de enero de 2026 a las 11:14 UTCinvestigating

   We have identified performance degradation in the Service Desk application within EUDC. This issue is impacting multiple functionalities of the application. Our team is actively investigating the issue and working to identify the root cause. Further updates will be shared as more information becomes available.

3. 6 de enero de 2026 a las 14:32 UTCmonitoring

   Service Desk EU data-center degradation issue affecting the application has now been restored. System performance is now normal and the application is operating as expected. We continue to monitor performance closely to ensure ongoing stability and reliability.

4. 6 de enero de 2026 a las 17:59 UTCresolved

   This incident has been resolved.

1. 5 de enero de 2026 a las 13:35 UTCinvestigating

   We are currently investigating an issue affecting the Service Desk in our EU Data Center. The round-robin automatic assignment is not working as expected, and newly created tickets are not being assigned to a user or group automatically. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.

2. 5 de enero de 2026 a las 16:13 UTCmonitoring

   A fix has been implemented. We will continue to monitor until we can confirm that no additional impact is expected.

3. 5 de enero de 2026 a las 19:13 UTCresolved

   This incident has been resolved.