Cronologia delle interruzioni di Activtrak

1. 1 settembre 2026 alle ore 16:24 UTCinvestigating

   Stiamo vivendo un elevato livello di errori API e attualmente stiamo cercando nel problema.

2. 1 settembre 2026 alle ore 16:51 UTCidentified

   Il problema è stato identificato e si sta attuando una correzione.

3. 1 settembre 2026 alle ore 17:09 UTCmonitoring

   Una soluzione è stata implementata e stiamo monitorando i risultati.

4. 1 settembre 2026 alle ore 17:09 UTCmonitoring

   Stiamo continuando a monitorare eventuali ulteriori problemi.

5. 1 settembre 2026 alle ore 17:58 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 31 agosto 2026 alle ore 20:04 UTCinvestigating

   Stiamo sperimentando un elevato livello di errori di applicazione sul rapporto "Produttività per posizione" e stanno attualmente cercando nel problema.

2. 31 agosto 2026 alle ore 20:50 UTCidentified

   Il problema è stato identificato e stiamo testando la correzione.

3. 31 agosto 2026 alle ore 21:43 UTCresolved

   Il problema è stato risolto e il rapporto "Productivity By Location" funziona correttamente.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 26 agosto 2026 alle ore 18:29 UTCinvestigating

   Il nostro team di ingegneri sta indagando su un aumento del tasso di errore associato ai registri di account. L'utente che si iscrive per un account può essere vedere un account gratuito invece di una nuova prova.

2. 26 agosto 2026 alle ore 19:47 UTCmonitoring

   Una soluzione è stata implementata e stiamo monitorando i risultati.

3. 27 agosto 2026 alle ore 02:00 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 19 agosto 2026 alle ore 15:34 UTCinvestigating

   Alcuni utenti possono riscontrare ritardi nella raccolta dati dell'agente. Il nostro team di ingegneri sta indagando sul problema.

2. 19 agosto 2026 alle ore 16:47 UTCinvestigating

   Stiamo continuando a indagare su questo problema.

3. 19 agosto 2026 alle ore 16:49 UTCmonitoring

   Una soluzione è stata implementata e stiamo monitorando i risultati.

4. 19 agosto 2026 alle ore 17:26 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 10 agosto 2026 alle ore 15:29 UTCinvestigating

   We are currently investigating this issue.

2. 10 agosto 2026 alle ore 16:08 UTCidentified

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

3. 10 agosto 2026 alle ore 16:13 UTCidentified

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

4. 10 agosto 2026 alle ore 16:27 UTCmonitoring

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

5. 10 agosto 2026 alle ore 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 luglio 2026 alle ore 15:03 UTCinvestigating

   Alcuni utenti possono sperimentare rapporti basati su Insights che non riescono a caricare. Il nostro team di ingegneri sta indagando sul problema.

2. 10 luglio 2026 alle ore 15:06 UTCidentified

   Il problema è stato identificato e si sta attuando una correzione.

3. 10 luglio 2026 alle ore 15:22 UTCmonitoring

   Una soluzione è stata implementata e stiamo monitorando i risultati.

4. 10 luglio 2026 alle ore 15:55 UTCresolved

   L'incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 30 giugno 2026 alle ore 17:01 UTCinvestigating

   Stiamo sperimentando un elevato livello di errori di login dell'applicazione e stiamo attualmente cercando nel problema.

2. 30 giugno 2026 alle ore 18:06 UTCmonitoring

   Una soluzione è stata implementata e stiamo monitorando i risultati.

3. 30 giugno 2026 alle ore 20:16 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 16 giugno 2026 alle ore 15:01 UTCinvestigating

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

2. 16 giugno 2026 alle ore 16:34 UTCmonitoring

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

3. 16 giugno 2026 alle ore 18:07 UTCresolved

   This incident has been resolved.

1. 10 giugno 2026 alle ore 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 giugno 2026 alle ore 21:29 UTCinvestigating

   We are continuing to investigate this issue.

3. 11 giugno 2026 alle ore 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 giugno 2026 alle ore 18:48 UTCinvestigating

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

2. 2 giugno 2026 alle ore 21:37 UTCmonitoring

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

3. 3 giugno 2026 alle ore 14:33 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 3 giugno 2026 alle ore 17:09 UTCresolved

   This incident has been resolved.

1. 29 maggio 2026 alle ore 14:23 UTCinvestigating

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

2. 29 maggio 2026 alle ore 14:51 UTCidentified

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

3. 29 maggio 2026 alle ore 15:32 UTCmonitoring

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

4. 29 maggio 2026 alle ore 18:59 UTCmonitoring

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

5. 29 maggio 2026 alle ore 23:04 UTCresolved

   This incident has been resolved.

1. 15 maggio 2026 alle ore 17:39 UTCinvestigating

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

2. 15 maggio 2026 alle ore 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 maggio 2026 alle ore 18:30 UTCresolved

   This incident has been resolved.

1. 7 maggio 2026 alle ore 18:31 UTCinvestigating

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

2. 8 maggio 2026 alle ore 13:48 UTCresolved

   This incident has been resolved.

1. 7 maggio 2026 alle ore 15:15 UTCinvestigating

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

2. 7 maggio 2026 alle ore 15:24 UTCidentified

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

3. 7 maggio 2026 alle ore 18:30 UTCmonitoring

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

4. 8 maggio 2026 alle ore 13:48 UTCresolved

   This incident has been resolved.

1. 30 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 18:20 UTCinvestigating

   We are continuing to investigate this issue.

3. 20 marzo 2026 alle ore 21:14 UTCresolved

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

1. 17 marzo 2026 alle ore 17:32 UTCinvestigating

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

2. 17 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 20:46 UTCidentified

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

3. 11 marzo 2026 alle ore 21:04 UTCresolved

   Our engineering team has deployed a fix for this issue.