Störungsverlauf von Activtrak

1. 1. September 2026 um 16:24 UTCinvestigating

   Wir haben ein erhöhtes Maß an API-Fehlern und untersuchen derzeit das Problem.

2. 1. September 2026 um 16:51 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

3. 1. September 2026 um 17:09 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 1. September 2026 um 17:09 UTCmonitoring

   Wir werden weiterhin auf weitere Probleme achten.

5. 1. September 2026 um 17:58 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 31. August 2026 um 20:04 UTCinvestigating

   Wir erleben ein erhöhtes Maß an Anwendungsfehlern im Bericht "Produktivität nach Standort" und untersuchen derzeit das Problem.

2. 31. August 2026 um 20:50 UTCidentified

   Das Problem wurde identifiziert und wir testen den Fix.

3. 31. August 2026 um 21:43 UTCresolved

   Das Problem wurde behoben und der Bericht "Produktivität nach Standort" funktioniert korrekt.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 26. August 2026 um 18:29 UTCinvestigating

   Unser Engineering-Team untersucht eine erhöhte Fehlerquote im Zusammenhang mit Kontoanmeldungen. Benutzer, die sich für ein Konto anmelden, sehen möglicherweise ein kostenloses Konto anstelle einer neuen Testversion.

2. 26. August 2026 um 19:47 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 27. August 2026 um 02:00 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 19. August 2026 um 15:34 UTCinvestigating

   Einige Benutzer haben möglicherweise Verzögerungen bei der Erfassung von Agentendaten. Unser Ingenieurteam untersucht das Problem.

2. 19. August 2026 um 16:47 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 19. August 2026 um 16:49 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 19. August 2026 um 17:26 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 10. August 2026 um 15:29 UTCinvestigating

   We are currently investigating this issue.

2. 10. August 2026 um 16:08 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 10. August 2026 um 16:13 UTCidentified

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

4. 10. August 2026 um 16:27 UTCmonitoring

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

5. 10. August 2026 um 18:42 UTCresolved

   The Azure AD integration will run normally tonight. Accounts can manually refresh/sync now by going to the APIs & Integration / Integrations page, view the Azure AD Instance, and clicking the manual refresh button.

1. 10. Juli 2026 um 15:03 UTCinvestigating

   Bei einigen Benutzern können Insights-basierte Berichte nicht geladen werden. Unser Ingenieurteam untersucht das Problem.

2. 10. Juli 2026 um 15:06 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

3. 10. Juli 2026 um 15:22 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 10. Juli 2026 um 15:55 UTCresolved

   Der Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 30. Juni 2026 um 17:01 UTCinvestigating

   Wir haben ein erhöhtes Maß an Anwendungs-Login-Fehlern und untersuchen derzeit das Problem.

2. 30. Juni 2026 um 18:06 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 30. Juni 2026 um 20:16 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. Juni 2026 um 15:01 UTCinvestigating

   We're experiencing login and application errors and are investigating.

2. 16. Juni 2026 um 16:34 UTCmonitoring

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

3. 16. Juni 2026 um 18:07 UTCresolved

   This incident has been resolved.

1. 10. Juni 2026 um 21:28 UTCinvestigating

   Some users may be experiencing delays in agent data collection. Our engineering team is looking into the issue. No data loss is occurring due to these delays.

2. 10. Juni 2026 um 21:29 UTCinvestigating

   We are continuing to investigate this issue.

3. 11. Juni 2026 um 15:20 UTCresolved

   Our engineering team implemented a fix last night and confirms that delayed data collection is now resolved. No data loss is occurring due to these delays.

1. 2. Juni 2026 um 18:48 UTCinvestigating

   Our engineering team is investigating an increase in errors associated with the real-time visibility feature.

2. 2. Juni 2026 um 21:37 UTCmonitoring

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

3. 3. Juni 2026 um 14:33 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 3. Juni 2026 um 17:09 UTCresolved

   This incident has been resolved.

1. 29. Mai 2026 um 14:23 UTCinvestigating

   Some users may be experiencing delays in insights reporting data. Our engineering team is looking into the issue.

2. 29. Mai 2026 um 14:51 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 29. Mai 2026 um 15:32 UTCmonitoring

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

4. 29. Mai 2026 um 18:59 UTCmonitoring

   Our engineering team is actively monitoring the fix. Backlogs are processing and Insights data will refresh as they clear.

5. 29. Mai 2026 um 23:04 UTCresolved

   This incident has been resolved.

1. 15. Mai 2026 um 17:39 UTCinvestigating

   Some users may be experiencing delays in agent data collection. Our engineering team is looking into the issue.

2. 15. Mai 2026 um 22:38 UTCmonitoring

   A fix has been deployed and is under active monitoring. Agent data reprocessing is underway and reports will catch up within the next few hours.

3. 16. Mai 2026 um 18:30 UTCresolved

   This incident has been resolved.

1. 7. Mai 2026 um 18:31 UTCinvestigating

   Some users may be experiencing delays in agent data collection. Our engineering team is looking into the issue.

2. 8. Mai 2026 um 13:48 UTCresolved

   This incident has been resolved.

1. 7. Mai 2026 um 15:15 UTCinvestigating

   Some users may be experiencing delays with data collection of screenshots. Our engineering team is looking into the issue.

2. 7. Mai 2026 um 15:24 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 7. Mai 2026 um 18:30 UTCmonitoring

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

4. 8. Mai 2026 um 13:48 UTCresolved

   This incident has been resolved.

1. 30. April 2026 um 13:25 UTCinvestigating

   We are currently investigating an issue with the Next Generation User Management (NGUM) system that could be causing Users data to be temporarily unavailable. Our engineering team has been notified and is actively working to restore service. We will provide another update as soon as we have more information.

2. 30. April 2026 um 13:33 UTCidentified

   We have identified the cause of the issue affecting the Next Generation User Management (NGUM) system. The service has been restored and User data should now be available. Please note that some users may experience delays in data availability as the system works through a backlog of data. We expect this to resolve on its own and are actively monitoring.

3. 30. April 2026 um 13:58 UTCmonitoring

   The Next Generation User Management (NGUM) system has been restored and we are actively monitoring system recovery. Backend processing queues that were impacted during the incident have been cleared and reprocessed. The majority of affected accounts have been recovered and data should be current or actively updating. We will continue to monitor until all systems have fully stabilized.

4. 30. April 2026 um 18:41 UTCresolved

   The issue affecting Next Generation User Management (NGUM) system has been fully resolved. All systems are operating normally and User data is available as expected. We apologize for any inconvenience this may have caused and thank you for your patience while we worked to restore service.

1. 28. April 2026 um 13:33 UTCinvestigating

   We are currently investigating an issue with the Next Generation User Management (NGUM) system that could be causing Users data to be temporarily unavailable. Our engineering team has been notified and is actively working to restore service. We will provide another update as soon as we have more information.

2. 28. April 2026 um 13:44 UTCidentified

   We have identified the cause of the issue affecting the Next Generation User Management (NGUM) system. The service has been restored and User data should now be available. Please note that some users may experience delays in data availability as the system works through a backlog of data. We expect this to resolve on its own and are actively monitoring.

3. 28. April 2026 um 17:52 UTCmonitoring

   The Next Generation User Management (NGUM) system has been restored and we are actively monitoring system recovery. Backend processing queues that were impacted during the incident have been cleared and reprocessed. The majority of affected accounts have been recovered and data should be current or actively updating. We will continue to monitor until all systems have fully stabilized.

4. 29. April 2026 um 17:38 UTCresolved

   The issue affecting Next Generation User Management (NGUM) system has been fully resolved. All systems are operating normally and User data is available as expected. We apologize for any inconvenience this may have caused and thank you for your patience while we worked to restore service.

1. 23. April 2026 um 15:09 UTCinvestigating

   Some users may be experiencing delays in insights and ActivConnect reporting data. Our engineering team is looking into the issue.

2. 23. April 2026 um 16:06 UTCidentified

   We have identified the cause of the delays affecting insights and ActivConnect reporting data for some accounts. Our engineering team is actively working on a resolution. We will provide further updates as progress is made.

3. 24. April 2026 um 14:56 UTCresolved

   The delays affecting insights and ActivConnect reporting data have been resolved. Processing has returned to normal and all data is up to date. We apologize for any inconvenience this may have caused.

1. 20. März 2026 um 18:20 UTCinvestigating

   The Watchdog entry is tied to a background service that’s part of the ActivTrak agent. Its purpose is to monitor the agent and restart it if needed to ensure continuous data collection. It is not a real user, does not collect any additional data, and does not impact reporting or insights. We’re actively investigating why it may be appearing as a user profile and will resolve it. No action is required on your end, and there’s no impact to your service. Until this is resolved, it will consume a license.

2. 20. März 2026 um 18:20 UTCinvestigating

   We are continuing to investigate this issue.

3. 20. März 2026 um 21:14 UTCresolved

   This incident has been resolved. The Watchdog user entry has been removed. No further action is required.

1. 17. März 2026 um 17:32 UTCinvestigating

   We're experiencing an elevated level of application errors and are currently looking into the issue.

2. 17. März 2026 um 18:14 UTCmonitoring

   We have identified the root cause and implemented a fix. We will continue to monitor the logs for any furhter elevated error rates.

3. 17. März 2026 um 18:55 UTCresolved

   This incident has been resolved. If you continue to experience issues, please log out and log back in to refresh your session. We apologize for the disruption and thank you for your patience.

1. 11. März 2026 um 19:31 UTCinvestigating

   Our engineering team is investigating issues with the Time Zone settings page. Customers may not be able to load the page at this time.

2. 11. März 2026 um 20:46 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 11. März 2026 um 21:04 UTCresolved

   Our engineering team has deployed a fix for this issue.