Historique des pannes de Samanage

1. 31 août 2026 à 15:15 UTCidentified

   Nous avons actuellement des retards dans la mise à jour de l'information sur la plateforme. Les tickets, les commentaires, les changements d'incident et les mises à jour sur le terrain, comme l'état et le titre, ainsi que d'autres fonctions, sont parfois lents à mettre à jour ou à afficher des informations périmées. Nous voyons également les temps de chargement des pages touchés. L'équipe a identifié la question et travaille à une résolution. Vous pouvez rencontrer quelques retards lorsque nous déplaçons le correctif sur la plate-forme.

2. 31 août 2026 à 15:58 UTCmonitoring

   La correction a été déployée, et nous traitons activement l'arriéré de mises à jour des billets. Pendant que le traitement est en cours, certaines mises à jour de billets peuvent continuer à connaître des retards. Nous nous attendons à ce que ces retards soient réglés à mesure que l'arriéré sera réglé. Nous continuerons de surveiller le système et de fournir d'autres mises à jour à mesure que le traitement progresse.

3. 31 août 2026 à 16:50 UTCmonitoring

   Nous assistons à des améliorations après le déploiement de la solution; nous surveillons activement le système pour nous assurer que les performances restent stables et que toutes les mises à jour retardées sont entièrement traitées.

4. 31 août 2026 à 17:42 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 14 juillet 2026 à 14:30 UTCinvestigating

   Nous enquêtons actuellement sur un problème touchant SolarWinds Service Desk. Certains utilisateurs pourraient ne pas être en mesure d'accéder à l'application pour le moment. Notre équipe travaille activement à identifier la cause et à rétablir le service le plus rapidement possible. Nous partagerons une autre mise à jour dès que plus d'informations seront disponibles.

2. 14 juillet 2026 à 14:44 UTCinvestigating

   Nous continuons d'enquêter sur cette question.

3. 14 juillet 2026 à 14:57 UTCinvestigating

   L'application est à nouveau accessible et le service a été restauré. Notre équipe continue de surveiller étroitement l'application afin d'assurer la stabilité. Nous fournirons une autre mise à jour si d'autres questions sont identifiées.

4. 14 juillet 2026 à 15:05 UTCmonitoring

   Notre équipe continue de surveiller étroitement l'application afin d'assurer la stabilité. D'autres mises à jour seront communiquées dès qu'elles seront disponibles.

5. 14 juillet 2026 à 16:01 UTCresolved

   Après une longue période de surveillance, SolarWinds Service Desk fonctionne maintenant normalement. À l'heure actuelle, nous considérons l'incident résolu. L'analyse des causes profondes (ARC) sera partagée dans les prochains jours une fois l'enquête terminée. Si vous avez besoin d'aide ou d'expérience supplémentaires, veuillez nous contacter à [email protected].

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 7 juillet 2026 à 15:59 UTCidentified

   Nous enquêtons actuellement sur un problème touchant SolarWinds Service Desk, où les incidents créés par courriel sont soumis avec succès, et des messages de confirmation sont envoyés, mais les incidents nouvellement créés peuvent ne pas apparaître sur la page Index des incidents. Notre équipe s'emploie activement à identifier la cause profonde et à rétablir la visibilité normale le plus rapidement possible. Nous fournirons une autre mise à jour dès que plus d'information sera disponible.

2. 7 juillet 2026 à 16:23 UTCinvestigating

   Nous continuons d'enquêter sur un problème dans SolarWinds Service Desk où de nouveaux incidents peuvent ne pas apparaître sur la page Index des incidents, bien que soumis avec succès et générant des messages de confirmation. Notre équipe s'efforce d'identifier la cause et de rétablir une visibilité normale. Nous partagerons une autre mise à jour dès que plus d'informations seront disponibles.

3. 7 juillet 2026 à 16:57 UTCidentified

   Nous avons identifié la cause profonde du problème touchant SolarWinds Service Desk, où de nouveaux incidents peuvent ne pas apparaître sur la page Index des incidents malgré avoir été soumis avec succès. Nous partagerons une autre mise à jour dès que d'autres informations seront disponibles.

4. 7 juillet 2026 à 18:00 UTCmonitoring

   Un correctif a été mis en place pour remédier au problème touchant SolarWinds Service Desk, où de nouveaux incidents peuvent ne pas apparaître sur la page Index des incidents malgré avoir été créés avec succès. Nous continuons de surveiller de près le service pour nous assurer que la visibilité normale est entièrement rétablie.

5. 7 juillet 2026 à 19:00 UTCresolved

   Après une longue période de surveillance, SolarWinds Service Desk fonctionne maintenant normalement. À l'heure actuelle, nous considérons l'incident résolu. Si vous avez besoin d'aide ou d'expérience supplémentaires, veuillez nous contacter à [email protected].

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 30 juin 2026 à 17:22 UTCinvestigating

   Nous enquêtons actuellement sur un problème touchant SolarWinds Service Desk où les incidents créés par courriel sont soumis avec succès et des messages de confirmation sont envoyés, mais les incidents nouvellement créés peuvent ne pas apparaître dans la page Index des incidents. Notre équipe s'emploie activement à identifier la cause et à rétablir la visibilité normale le plus rapidement possible. Nous partagerons une autre mise à jour dès que d'autres informations seront disponibles.

2. 30 juin 2026 à 17:58 UTCidentified

   Nous avons identifié la cause du problème signalé et nous travaillons sur une solution aussi rapidement que possible. Merci de votre patience.

3. 30 juin 2026 à 18:09 UTCmonitoring

   Nous avons terminé la correction pour ce problème et les services reviennent à la normale. Les incidents soumis par courriel devraient maintenant apparaître correctement dans la page Index des incidents comme prévu. Notre équipe continuera de surveiller de près l'environnement pour assurer la stabilité et confirmer que la question a été entièrement réglée. Nous apprécions votre patience pendant que nous avons travaillé sur cette question.

4. 30 juin 2026 à 19:47 UTCmonitoring

   Nous continuons de surveiller de près le comportement pendant que notre équipe s'efforce de confirmer une visibilité constante dans la liste des incidents. Nous partagerons une autre mise à jour dès que d'autres informations seront disponibles.

5. 30 juin 2026 à 21:04 UTCmonitoring

   Nous constatons des améliorations dans le rendement global de l'application. Notre équipe continue de surveiller de près l'environnement afin d'assurer la stabilité et de confirmer qu'aucun autre problème ne se pose. Nous partagerons des mises à jour supplémentaires au besoin.

6. 30 juin 2026 à 22:02 UTCresolved

   Après une longue période de surveillance, la question n'a pas refait surface et nous n'avons reçu aucun autre rapport d'impact. Le service fonctionne normalement, et nous envisageons de résoudre cet incident. Si vous continuez à éprouver des problèmes ou avez besoin d'aide, veuillez nous contacter par courriel à [email protected], et notre équipe sera heureuse de vous aider.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 23 juin 2026 à 16:14 UTCinvestigating

   Nous enquêtons actuellement sur un problème où les incidents créés par courriel peuvent ne pas apparaître immédiatement dans la liste des incidents dans SolarWinds Service Desk UI. Au cours de notre examen, nous avons confirmé que les avis de création d'incidents étaient envoyés avec succès et que les incidents touchés pouvaient être consultés par le biais de leurs liens directs. Cependant, il peut y avoir un retard avant que ces incidents ne deviennent visibles dans la liste des incidents au sein de l'AC. Notre équipe enquête activement sur ce comportement et travaille à déterminer la cause. Nous partagerons une autre mise à jour dès que d'autres informations seront disponibles.

2. 23 juin 2026 à 16:37 UTCmonitoring

   Nous suivons actuellement cette question. Notre enquête a confirmé que la création d'incidents se produit avec succès et que les courriels de notification sont envoyés comme prévu. Cependant, certains incidents créés par courriel peuvent ne pas apparaître immédiatement dans la liste des incidents au sein de l'AC, même s'ils demeurent accessibles par le lien direct inclus dans le courriel de notification. Nous continuons de surveiller de près le comportement pendant que notre équipe s'efforce de confirmer une visibilité constante dans la liste des incidents. Nous partagerons une autre mise à jour dès que d'autres informations seront disponibles.

3. 23 juin 2026 à 18:31 UTCresolved

   Notre surveillance indique que le problème touchant la visibilité des incidents a été résolu. Nous avons continué à surveiller de près le service et n'avons pas observé d'autres événements du problème. À l'heure actuelle, nous considérons l'incident résolu. Si vous avez besoin d'aide ou d'expérience supplémentaires, veuillez nous contacter à [email protected].

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 3 juin 2026 à 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 juin 2026 à 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 juin 2026 à 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 juin 2026 à 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 mai 2026 à 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 mai 2026 à 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 mai 2026 à 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 avril 2026 à 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 avril 2026 à 19:08 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 13:42 UTCmonitoring

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

4. 3 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 mars 2026 à 09:14 UTCinvestigating

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

2. 18 mars 2026 à 09: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 mars 2026 à 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 mars 2026 à 11:57 UTCidentified

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

5. 18 mars 2026 à 12:26 UTCidentified

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

6. 18 mars 2026 à 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 mars 2026 à 13:30 UTCresolved

   This issue has been resolved.

1. 2 février 2026 à 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 février 2026 à 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 février 2026 à 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 février 2026 à 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 février 2026 à 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 février 2026 à 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 janvier 2026 à 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 janvier 2026 à 20:08 UTCinvestigating

   We are continuing to investigate this issue.

3. 28 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 01: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 janvier 2026 à 03: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 janvier 2026 à 05: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 janvier 2026 à 08: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 janvier 2026 à 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 janvier 2026 à 11:28 UTCmonitoring

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

12. 29 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 03: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 janvier 2026 à 04:49 UTCresolved

   This issue has been resolved.

1. 27 janvier 2026 à 00: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 janvier 2026 à 01:23 UTCmonitoring

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

3. 27 janvier 2026 à 02:09 UTCresolved

   This incident has been resolved.

1. 12 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 02:23 UTCresolved

   This issue has been resolved.

1. 12 janvier 2026 à 07: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 janvier 2026 à 12:28 UTCresolved

   This issue has been resolved.

1. 9 janvier 2026 à 09: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 janvier 2026 à 09: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 janvier 2026 à 10:09 UTCmonitoring

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

4. 9 janvier 2026 à 11:00 UTCresolved

   This incident has been resolved.

1. 6 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 17:59 UTCresolved

   This incident has been resolved.

1. 5 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 19:13 UTCresolved

   This incident has been resolved.

1. 18 novembre 2025 à 13:32 UTCmonitoring

   We're currently experiencing an upstream vendor outage. This is affecting services, and you may see failures in items such as VA (Virtual Agent) functionality and custom domain routing. Our teams are monitoring the situation closely for updates.

2. 18 novembre 2025 à 14:16 UTCmonitoring

   Our upstream vendor are continue working on restoring service for application services.

3. 18 novembre 2025 à 15:33 UTCmonitoring

   Based on the recent update from our upstream vendor they have implemented a fix to resolve the issue. Our team is continuously monitoring for updates.

4. 18 novembre 2025 à 19:23 UTCmonitoring

   Our upstream vendor’s issue has been resolved, and we are no longer seeing any impact on our platform. We will continue to closely monitor the fix.

5. 18 novembre 2025 à 23:17 UTCresolved

   This issue has been resolved. Please contact us at [email protected] if you need further assistance.