Samanage driftsforstyrrelser

1. 8. september 2026 kl. 14.27 UTCinvestigating

   Vi oplever i øjeblikket forsinkelser i visning af opdaterede oplysninger på tværs af platformen. Nye og opdaterede billetter, kommentarer, hændelsesændringer og feltopdateringer - såsom state og titel ændringer - kan tage længere tid end forventet at dukke op eller kan midlertidigt vise forældede oplysninger. Sidebelastningstider kan også blive påvirket. Vores team har identificeret problemet og arbejder på at løse det. Nogle forsinkelser kan fortsætte, når vi rulle ud fix på tværs af platformen.

2. 8. september 2026 kl. 15.25 UTCmonitoring

   Fixet er blevet indsat, og vi arbejder aktivt gennem den resterende efterslæb af billetopdateringer. Nogle opdateringer kan fortsætte med at blive forsinket, mens behandlingen er i gang, men vi forventer forsinkelser til at mindske, som backlog er ryddet. Vi vil fortsætte med at overvåge systemet og levere yderligere opdateringer som behandling skrider frem.

3. 8. september 2026 kl. 16.16 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 31. august 2026 kl. 15.15 UTCidentified

   Vi oplever i øjeblikket forsinkelser i opdaterede oplysninger, der viser i platformen. Nye og opdaterede billetter, kommentarer, hændelsesændringer, og felt opdateringer, såsom stat og titel, og andre funktioner, er til tider langsomme til at opdatere og eller vise forældede oplysninger. Vi ser også sidebelastningstider blive påvirket. Holdet har identificeret problemet og arbejder på en resolution. Du kan opleve nogle forsinkelser, når vi rulle ud fix på tværs af platformen.

2. 31. august 2026 kl. 15.58 UTCmonitoring

   Fixet er blevet indsat, og vi er aktivt ved at behandle den resterende efterslæb af billetopdateringer. Mens behandlingen er i gang, kan nogle billetopdateringer fortsætte med at opleve forsinkelser. Vi forventer, at disse forsinkelser vil blive løst, efterhånden som efterslæbet er ryddet. Vi vil fortsat overvåge systemet og levere yderligere opdateringer, efterhånden som behandlingen skrider frem.

3. 31. august 2026 kl. 16.50 UTCmonitoring

   Vi ser forbedringer efter indførelsen af fixet; vi overvåger aktivt systemet for at sikre, at præstationerne forbliver stabile, og at alle forsinkede opdateringer behandles fuldt ud.

4. 31. august 2026 kl. 17.42 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. juli 2026 kl. 14.30 UTCinvestigating

   Vi undersøger i øjeblikket et problem, der påvirker SolarWinds Service Desk. Nogle brugere kan være ude af stand til at få adgang til programmet på dette tidspunkt. Vores team arbejder aktivt på at identificere årsagen og genoprette service så hurtigt som muligt. Vi vil dele en anden opdatering, så snart mere information er tilgængelig.

2. 14. juli 2026 kl. 14.44 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål.

3. 14. juli 2026 kl. 14.57 UTCinvestigating

   Ansøgningen er tilgængelig igen, og service er blevet genoprettet. Vores team fortsætter med at overvåge ansøgningen nøje for at sikre stabilitet. Vi vil give en anden opdatering, hvis yderligere spørgsmål er identificeret.

4. 14. juli 2026 kl. 15.05 UTCmonitoring

   Vores team fortsætter med at overvåge ansøgningen nøje for at sikre stabilitet. Yderligere opdateringer vil blive delt, så snart de er tilgængelige.

5. 14. juli 2026 kl. 16.01 UTCresolved

   Efter en længere overvågningsperiode fungerer SolarWinds Service Desk nu normalt. På dette tidspunkt, mener vi hændelsen løst. Root årsag analyse (RCA) vil blive delt i de kommende dage, når undersøgelsen er afsluttet. Hvis du har brug for yderligere assistance eller oplever yderligere problemer, bedes du kontakte os på teknisk support @ solarwinds.com.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 7. juli 2026 kl. 15.59 UTCidentified

   Vi er i øjeblikket ved at undersøge et problem, der påvirker SolarWinds Service Desk, hvor hændelser skabt via e-mail bliver indsendt med succes, og bekræftelsesmeddelelser bliver sendt, men de nyoprettede hændelser kan ikke vises på Incident Index side. Vores team arbejder aktivt på at identificere årsagen og genoprette normal synlighed så hurtigt som muligt. Vi vil give en anden opdatering, så snart mere information bliver tilgængelig.

2. 7. juli 2026 kl. 16.23 UTCinvestigating

   Vi fortsætter med at undersøge et problem i SolarWinds Service Desk, hvor nye hændelser kan ikke vises på Incident Index side, på trods af at blive indsendt med succes og generere bekræftelsesmeddelelser. Vores team arbejder på at identificere årsagen og genoprette normal synlighed. Vi vil dele en anden opdatering, så snart mere information er tilgængelig.

3. 7. juli 2026 kl. 16.57 UTCidentified

   Vi har identificeret den grundlæggende årsag til problemet påvirker SolarWinds Service Desk, hvor nye hændelser kan ikke vises på Incident Index side på trods af at blive indsendt med succes. Vi vil dele en anden opdatering, så snart mere information bliver tilgængelig.

4. 7. juli 2026 kl. 18.00 UTCmonitoring

   En rettelse er blevet indsat for at afhjælpe problemet påvirker SolarWinds Service Desk, hvor nye hændelser kan ikke vises på Incident Index side på trods af at blive oprettet med succes. Vi fortsætter med at overvåge tjenesten nøje for at sikre, at den normale synlighed genoprettes fuldt ud.

5. 7. juli 2026 kl. 19.00 UTCresolved

   Efter en længere overvågningsperiode fungerer SolarWinds Service Desk nu normalt. På dette tidspunkt, mener vi hændelsen løst. Hvis du har brug for yderligere assistance eller oplever yderligere problemer, bedes du kontakte os på teknisk support @ solarwinds.com.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 30. juni 2026 kl. 17.22 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem, der påvirker SolarWinds Service Desk, hvor hændelser oprettet via e-mail er indsendt med succes, og bekræftelsesmeddelelser sendes, men de nyoprettede hændelser kan ikke vises i Incident Index side. Vores team arbejder aktivt på at identificere årsagen og genoprette normal synlighed så hurtigt som muligt. Vi vil dele en anden opdatering, så snart mere information bliver tilgængelig.

2. 30. juni 2026 kl. 17.58 UTCidentified

   Vi har identificeret årsagen til det rapporterede problem og arbejder på et fix så hurtigt som muligt. Tak for din tålmodighed.

3. 30. juni 2026 kl. 18.09 UTCmonitoring

   Vi har afsluttet fixet for dette spørgsmål, og tjenesterne vender tilbage til normale. Hændelser indsendt via e-mail skal nu vises korrekt i hændelsesindeks siden som forventet. Vores team vil fortsat nøje overvåge miljøet for at sikre stabilitet og bekræfte, at problemet er løst fuldt ud. Vi sætter pris på din tålmodighed, mens vi arbejdede på at løse dette spørgsmål.

4. 30. juni 2026 kl. 19.47 UTCmonitoring

   Vi fortsætter med at overvåge adfærd tæt, mens vores team arbejder for at bekræfte konsekvent synlighed i hændelseslisten. Vi vil dele en anden opdatering, så snart mere information bliver tilgængelig.

5. 30. juni 2026 kl. 21.04 UTCmonitoring

   Vi ser forbedringer i programmets samlede ydeevne. Vores team overvåger fortsat miljøet nøje for at sikre stabilitet og bekræfter, at der ikke opstår yderligere problemer. Vi vil dele yderligere opdateringer efter behov.

6. 30. juni 2026 kl. 22.02 UTCresolved

   Efter en længere overvågningsperiode er spørgsmålet ikke dukket op igen, og vi har ikke modtaget yderligere rapporter om virkningen. Tjenesten fungerer normalt, og vi overvejer denne hændelse løst. Hvis du fortsætter med at opleve problemer eller har brug for yderligere hjælp, bedes du kontakte os via e-mail på teknisk support @ solarwinds.com, og vores team vil med glæde hjælpe.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 23. juni 2026 kl. 16.14 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem, hvor hændelser oprettet via e-mail kan ikke vises umiddelbart i hændelseslisten i SolarWinds Service Desk UI. Under vores gennemgang bekræftede vi, at meddelelser om oprettelse af hændelser sendes med succes, og de berørte hændelser kan tilgås via deres direkte forbindelser. Der kan dog være en forsinkelse, inden disse hændelser bliver synlige på listen over hændelser i EU-listen. Vores team undersøger denne adfærd og arbejder på at afgøre årsagen. Vi vil dele en anden opdatering, så snart mere information bliver tilgængelig.

2. 23. juni 2026 kl. 16.37 UTCmonitoring

   Vi overvåger i øjeblikket dette spørgsmål. Vores undersøgelse bekræftede, at det lykkes at oprette en hændelse, og at e-mails sendes som forventet. Men nogle hændelser oprettet via e-mail kan ikke vises umiddelbart i hændelseslisten i UI, selv om de forbliver tilgængelige via det direkte link, der er inkluderet i anmeldelsen e-mail. Vi fortsætter med at overvåge adfærd tæt, mens vores team arbejder for at bekræfte konsekvent synlighed i hændelseslisten. Vi vil dele en anden opdatering, så snart mere information bliver tilgængelig.

3. 23. juni 2026 kl. 18.31 UTCresolved

   Vores overvågning viser, at problemet med at påvirke hændelsens synlighed er løst. Vi har fortsat med nøje at overvåge tjenesten og har ikke observeret nogen yderligere forekomster af problemet. På dette tidspunkt, mener vi hændelsen løst. Hvis du har brug for yderligere assistance eller oplever yderligere problemer, bedes du kontakte os på teknisk support @ solarwinds.com.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 3. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 19.08 UTCinvestigating

   We are continuing to investigate this issue.

3. 29. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 13.42 UTCmonitoring

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

4. 3. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. marts 2026 kl. 09.14 UTCinvestigating

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

2. 18. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 11.57 UTCidentified

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

5. 18. marts 2026 kl. 12.26 UTCidentified

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

6. 18. marts 2026 kl. 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. marts 2026 kl. 13.30 UTCresolved

   This issue has been resolved.

1. 2. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 20.08 UTCinvestigating

   We are continuing to investigate this issue.

3. 28. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 11.28 UTCmonitoring

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

12. 29. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 04.49 UTCresolved

   This issue has been resolved.

1. 27. januar 2026 kl. 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. januar 2026 kl. 01.23 UTCmonitoring

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

3. 27. januar 2026 kl. 02.09 UTCresolved

   This incident has been resolved.

1. 12. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 02.23 UTCresolved

   This issue has been resolved.

1. 12. januar 2026 kl. 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. januar 2026 kl. 12.28 UTCresolved

   This issue has been resolved.

1. 9. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 10.09 UTCmonitoring

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

4. 9. januar 2026 kl. 11.00 UTCresolved

   This incident has been resolved.

1. 6. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 17.59 UTCresolved

   This incident has been resolved.

1. 5. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 19.13 UTCresolved

   This incident has been resolved.