61 Activtrak incidents · Ekim 2024 — official updates, affected components, duration and resolution details.
Bazı kullanıcılar bilgi raporlama verilerinde gecikmeler yaşayabilir. Mühendislik ekibimiz konuya bakıyor.
Sorun tespit edildi ve bir düzeltme uygulanır.
Bir düzeltme uygulandı ve mevcut gerilog işleniyor. Mühendislik ekibimiz sonuçları izliyor.
Bu olay çözüldü.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
Kullanıcılar yapılandırma sayfaları üzerinde yüksek bir uygulama hataları yaşıyoruz ve şu anda konuya bakıyoruz.
Sorunu tespit ettik ve düzeltme üzerinde çalışıyoruz.
Bir düzeltme uygulandı ve sonuçları takip ediyoruz.
Sorun çözüldü.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
Mühendislik ekibimiz, giriş ile ilgili bir artış numarası veya hataları tespit etti.
Mühendislik ekibimiz bazı hesaplar için girişle ilgili yüksek hata oranlarına bakmaya devam ediyor.
Bir düzeltme uygulandı ve sonuçları takip ediyoruz.
Bu olay çözüldü.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
Yüksek düzeyde API hataları yaşıyoruz ve şu anda konuya bakıyoruz.
Sorun tespit edildi ve bir düzeltme uygulanır.
Bir düzeltme uygulandı ve sonuçları takip ediyoruz.
Daha fazla sorun için izlemeye devam ediyoruz.
Bu olay çözüldü.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
“Yerellik” raporunda yüksek bir uygulama hataları yaşıyoruz ve şu anda konuya bakıyoruz.
Sorun tespit edildi ve düzeltmeyi test ediyoruz.
Sorun çözüldü ve "Yerellik" raporu doğru çalışıyor.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
Mühendislik ekibimiz, hesap işaretleriyle ilişkili artan bir hata oranını araştırıyor. Bir hesap için kaydolan kullanıcı yeni bir deneme yerine ücretsiz bir hesap görebilir.
Bir düzeltme uygulandı ve sonuçları takip ediyoruz.
Bu olay çözüldü.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
Bazı kullanıcılar ajan veri koleksiyonunda gecikmeler yaşayabilir. Mühendislik ekibimiz konuya bakıyor.
Bu konuyu araştırmaya devam ediyoruz.
Bir düzeltme uygulandı ve sonuçları takip ediyoruz.
Bu olay çözüldü.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
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.
Bazı kullanıcılar, yüklemeye başarısız olan raporlara dayanan İçgörüleri deneyimleyebilir. Mühendislik ekibimiz konuya bakıyor.
Sorun tespit edildi ve bir düzeltme uygulanır.
Bir düzeltme uygulandı ve sonuçları takip ediyoruz.
Olay çözüldü.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
Yüksek bir uygulama giriş hataları seviyesini yaşıyoruz ve şu anda konuya bakıyoruz.
Bir düzeltme uygulandı ve sonuçları takip ediyoruz.
Bu olay çözüldü.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
We're experiencing login and application errors and are investigating.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We are continuing to investigate this issue.
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.
Our engineering team is investigating an increase in errors associated with the real-time visibility feature.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
Some users may be experiencing delays in insights reporting data. Our engineering team is looking into the issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
Our engineering team is actively monitoring the fix. Backlogs are processing and Insights data will refresh as they clear.
This incident has been resolved.
Some users may be experiencing delays in agent data collection. Our engineering team is looking into the issue.
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.
This incident has been resolved.
Some users may be experiencing delays in agent data collection. Our engineering team is looking into the issue.
This incident has been resolved.
Some users may be experiencing delays with data collection of screenshots. Our engineering team is looking into the issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
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.
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.
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.
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.
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.
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.
Some users may be experiencing delays in insights and ActivConnect reporting data. Our engineering team is looking into the issue.
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.
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.
