Histórico de interrupções do Activtrak

1. 1 Gwengolo 2026 da 16:24 UTCinvestigating

   Estamos experimentando um nível elevado de erros de API e atualmente estamos olhando para o problema.

2. 1 Gwengolo 2026 da 16:51 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 1 Gwengolo 2026 da 17:09 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 1 Gwengolo 2026 da 17:09 UTCmonitoring

   Continuamos monitorando quaisquer outros problemas.

5. 1 Gwengolo 2026 da 17:58 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 31 Eost 2026 da 20:04 UTCinvestigating

   Estamos experimentando um nível elevado de erros de aplicação no relatório "Produtividade por Localização" e estamos atualmente olhando para o problema.

2. 31 Eost 2026 da 20:50 UTCidentified

   A questão foi identificada e estamos a testar a solução.

3. 31 Eost 2026 da 21:43 UTCresolved

   O problema foi resolvido e o relatório "Produtividade por Localização" está funcionando corretamente.

Traduzido automaticamente da atualização oficial do incidente.

1. 26 Eost 2026 da 18:29 UTCinvestigating

   Nossa equipe de engenharia está investigando um aumento da taxa de erro associado com inscrições de contas. Usuário que está se inscrevendo para uma conta pode estar vendo uma conta gratuita em vez de uma nova avaliação.

2. 26 Eost 2026 da 19:47 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

3. 27 Eost 2026 da 02:00 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 19 Eost 2026 da 15:34 UTCinvestigating

   Alguns usuários podem estar passando por atrasos na coleta de dados do agente. A nossa equipa de engenharia está a investigar o problema.

2. 19 Eost 2026 da 16:47 UTCinvestigating

   Continuamos a investigar esta questão.

3. 19 Eost 2026 da 16:49 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 19 Eost 2026 da 17:26 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 10 Eost 2026 da 15:29 UTCinvestigating

   We are currently investigating this issue.

2. 10 Eost 2026 da 16:08 UTCidentified

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

3. 10 Eost 2026 da 16:13 UTCidentified

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

4. 10 Eost 2026 da 16:27 UTCmonitoring

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

5. 10 Eost 2026 da 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 Gouere 2026 da 15:03 UTCinvestigating

   Alguns usuários podem estar experimentando relatórios baseados no Insights falhando em carregar. A nossa equipa de engenharia está a investigar o problema.

2. 10 Gouere 2026 da 15:06 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 10 Gouere 2026 da 15:22 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 10 Gouere 2026 da 15:55 UTCresolved

   O incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 30 Mezheven 2026 da 17:01 UTCinvestigating

   Estamos experimentando um nível elevado de erros de login de aplicativos e atualmente estamos olhando para o problema.

2. 30 Mezheven 2026 da 18:06 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

3. 30 Mezheven 2026 da 20:16 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 16 Mezheven 2026 da 15:01 UTCinvestigating

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

2. 16 Mezheven 2026 da 16:34 UTCmonitoring

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

3. 16 Mezheven 2026 da 18:07 UTCresolved

   This incident has been resolved.

1. 10 Mezheven 2026 da 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 Mezheven 2026 da 21:29 UTCinvestigating

   We are continuing to investigate this issue.

3. 11 Mezheven 2026 da 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 Mezheven 2026 da 18:48 UTCinvestigating

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

2. 2 Mezheven 2026 da 21:37 UTCmonitoring

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

3. 3 Mezheven 2026 da 14:33 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 3 Mezheven 2026 da 17:09 UTCresolved

   This incident has been resolved.

1. 29 Mae 2026 da 14:23 UTCinvestigating

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

2. 29 Mae 2026 da 14:51 UTCidentified

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

3. 29 Mae 2026 da 15:32 UTCmonitoring

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

4. 29 Mae 2026 da 18:59 UTCmonitoring

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

5. 29 Mae 2026 da 23:04 UTCresolved

   This incident has been resolved.

1. 15 Mae 2026 da 17:39 UTCinvestigating

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

2. 15 Mae 2026 da 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 Mae 2026 da 18:30 UTCresolved

   This incident has been resolved.

1. 7 Mae 2026 da 18:31 UTCinvestigating

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

2. 8 Mae 2026 da 13:48 UTCresolved

   This incident has been resolved.

1. 7 Mae 2026 da 15:15 UTCinvestigating

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

2. 7 Mae 2026 da 15:24 UTCidentified

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

3. 7 Mae 2026 da 18:30 UTCmonitoring

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

4. 8 Mae 2026 da 13:48 UTCresolved

   This incident has been resolved.

1. 30 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 18:20 UTCinvestigating

   We are continuing to investigate this issue.

3. 20 Meurzh 2026 da 21:14 UTCresolved

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

1. 17 Meurzh 2026 da 17:32 UTCinvestigating

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

2. 17 Meurzh 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 20:46 UTCidentified

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

3. 11 Meurzh 2026 da 21:04 UTCresolved

   Our engineering team has deployed a fix for this issue.