Our team has completed a workaround for affected TikTok integrations across all regions.
As the next step, customers experiencing a "deleted token" error must reconnect their affected TikTok feeds to restore connectivity.
To reconnect, navigate to Settings > Integrations > Source Integrations, select the edit (pencil) icon for the affected TikTok source, and choose Reconnect.
We will continue monitoring the situation and provide further updates as needed.
identified
Our team has identified the cause of the issue affecting some TikTok integrations in Khoros Care. TikTok accounts that were connected more than about a year ago may have stopped bringing in new content, even though they still appear as connected. Accounts connected within the last year are not affected.
Affected customers may need to reconnect their TikTok accounts. To do this, go to Settings > Integrations > Source Integrations, select the edit (pencil) icon on the TikTok source, and choose Reconnect.
We are preparing an update that will clearly mark affected TikTok integrations as needing reconnection and notify administrators. We will provide another update as soon as more information is available.
investigating
We are investigating an issue affecting TikTok integrations in Khoros Care. Some customers may experience connectivity issues with their TikTok accounts, even though the integrations continue to appear as connected.
Our team is reviewing the affected integrations and working on the appropriate recovery steps. Affected customers may need to reconnect their TikTok accounts to restore connectivity.
We will provide further updates as more information becomes available.
September 2026
Problems with message delivery through our Instagram and Facebook integrations
We are aware of an issue affecting outbound message delivery through our Instagram and Facebook integrations. Some customers may experience failures when sending replies. Our team is investigating the root cause and working on a resolution. We will provide updates as more information becomes available
Legacy Incident Archive
31 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
March 2026
[EMEA] Analytics data not updated
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The missing historical dates have now been backfilled and restored, and Community Analytics is back on its normal refresh cadence. Because Community Analytics reports in UTC and refreshes on a delay, the most recent date may still be within the normal processing window before it appears. We continue monitoring the situation.
monitoring
We have completed the backfill, and the data for March 28th is expected to be completed in time. We continue to monitor the situation
monitoring
We have improved the speed of backfills, and expect to catch up on the remaining backfills over the next 2 days
monitoring
The backfill for the 22nd has completed, and the remaining days are in progress.
monitoring
The backfill for the 20th and 21st has completed, and the 22nd is in progress.
monitoring
The backfill for the 18th encountered issues and we are working on resolving this. The backfill for the 19th has completed, and the 20th is in progress.
monitoring
Backfill for 17th March has been completed. The backfill for the 18th is now in progress.
monitoring
Our Infrastructure team have resolved the issue, and the backfills for the 17th onwards are proceeding.
monitoring
Our Infrastructure team are investigating and fixing an issue with the backfill for 17th and 18th. The backfilling efforts will resume shortly.
monitoring
Backfill for 16th March has been completed. The backfill for the 17th is now in progress.
monitoring
Backfill for 15th March has been completed. The backfill for the 16th is now commencing.
monitoring
Backfill for 16th March is under progress. We will share another update once processing and validation have been completed.
monitoring
Backfill for March 15th for the affected region is completed.
We are continuing the backfill for March 16th, and we will share another update once processing and validation have been completed
monitoring
Backfill for March 15th for the affected EU data is completed.
monitoring
Backfill for March 14th for the affected EU data is completed.
We are continuing the backfill for March 15th, and we will share another update once processing and validation have been completed.
monitoring
Backfill processing for the affected EU data is still in progress.
Recovery work is continuing normally, and we will share another update once processing and validation have been completed.
monitoring
Backfill processing for the affected EU data is still in progress.
Recovery work is continuing normally, and we will share another update once processing and validation have been completed.
monitoring
Backfill processing for the affected EU data is still in progress. Based on current progress, we expect the remaining data to be fully ingested by March 19 morning UTC, with a final confirmation to follow once validation is complete.
identified
Backfilling of data is in progress for the 9th and the jobs continue to run as expected.
identified
Backfill processing is currently underway.
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have identified the analytics data population issue, and our teams applied a fix. Backfill processing is currently underway. We will share further updates as they become available.
identified
We have identified the issue and are in the process of developing a fix for the same.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating an issue that is affecting analytics data for EMEA Communities. Data have not been populated since the 14th of March.
Our infrastructure team is working on this with Urgent priority.