Khoros Status

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.

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.

Resolved: We have observed no further issues through our monitoring. The login issues have been resolved.

Monitoring: The issue has been resolved, service has remained stable since recovery, and we are continuing follow-up work to reduce the risk of recurrence. We apologize for the disruption and will continue to monitor closely.

Investigating: We are observing some errors in the system and are continuing to find and investigate the root cause.

Identified: We have identified an issue with the database entering failover loop, applied mitigation and are observing the system for errors.

Investigating: We are investigating reports of users being unexpectedly logged out, seeing 500 errors, or being unable to log in to Khoros Care. Some customers are also reporting loss of access to chats and other core workflows.

Investigating: We are currently investigating a production outage causing intermittent 504 timeout errors when users attempt to login

Resolved: We have observed no further issues through our monitoring. The login issues have been resolved.

Monitoring: The issue has been resolved, service has remained stable since recovery, and we are continuing follow-up work to reduce the risk of recurrence. We apologize for the disruption and will continue to monitor closely.

Investigating: We are observing some errors in the system and are continuing to find and investigate the root cause.

Identified: We have identified an issue with the database entering failover loop, applied mitigation and are observing the system for errors.

Investigating: We are investigating reports of users being unexpectedly logged out, seeing 500 errors, or being unable to log in to Khoros Care. Some customers are also reporting loss of access to chats and other core workflows.

Investigating: We are currently investigating a production outage causing intermittent 504 timeout errors when users attempt to login

Monitoring: We have identified some data that has not been backfilled, and our Infrastructure team are working on resolving this.

Monitoring: The historical backfill work for the affected ingestion period has finished. New Community-to-Care ingestion should now be operating normally, and missing historical data from the impacted window should be restored where applicable.

Our teams will remain on enhanced monitoring for 24 hours to validate end-to-end behavior before we close this incident.

Monitoring: Data ingestion recovery remains in progress. Backfill processing has already completed in one affected region and is still running in the remaining impacted EU region.

We will share another update as soon as processing is complete and final validation has been finished.

Monitoring: Data ingestion recovery is nearing completion. Backfill processing has already completed in one affected region and is still running in the remaining impacted EU region. Based on current progress, we expect ingestion to be fully completed by the morning of March 19 UTC, assuming the remaining jobs finish successfully.

Monitoring: Backfilling for the affected dates is still in progress and is progressing successfully.

Monitoring: Monitoring continues as backfilling for the affected dates progresses.

Monitoring: We continue to monitor backfilling for the affected dates.

Monitoring: We are continuing to monitor the ongoing backfilling for the affected dates.

Monitoring: We have introduced a fix for this issue and are now working on backfilling data for the affected dates.

Identified: Our Engineering team are working on a fix for this issue.

Investigating: We are continuing to investigate the delays affecting Community-to-Care ingestion. Our team is actively reviewing the issue, and the investigation is ongoing. We will share additional updates as soon as more information becomes available.

Investigating: We are continuing to investigate the delays in Community to Care ingestion. We will provide further updates as soon as they are available.

Investigating: We are currently investigating reports by some customers experiencing delays in Community-to-Care ingestion

Resolved: We have confirmed that this issue is now resolved.

Monitoring: We are continuing to monitor this.

Monitoring: We are continuing to monitor this. No issues have been reported currently.

Monitoring: The fixes have been successfully deployed. Publishing should now be operating normally, and we are continuing to monitor the system.

Monitoring: Fix deployment in progress. No new issues have been reported.

Monitoring: We are in the process of deploying a fix. No new issues have been reported currently and we are continuing to monitor the same.

Monitoring: Our Engineering has implemented a temporary fix for the Meta performance degradation issue. They continue to work on a permanent resolution. We will continue to monitor this situation.

Monitoring: Our Engineering team found that there was a performance degradation from Meta on March 12 that stopped on March 13. They are implementing a preventive fix in case it happens again. We will continue to monitor this situation.

Investigating: We have received reports about people being unable to publish to Facebook. We are investigating the issue.

Resolved: We have confirmed that this issue is now resolved.

Monitoring: We are continuing to monitor this.

Monitoring: We are continuing to monitor this. No issues have been reported currently.

Monitoring: The fixes have been successfully deployed. Publishing should now be operating normally, and we are continuing to monitor the system.

Monitoring: Fix deployment in progress. No new issues have been reported.

Monitoring: We are in the process of deploying a fix. No new issues have been reported currently and we are continuing to monitor the same.

Monitoring: Our Engineering has implemented a temporary fix for the Meta performance degradation issue. They continue to work on a permanent resolution. We will continue to monitor this situation.

Monitoring: Our Engineering team found that there was a performance degradation from Meta on March 12 that stopped on March 13. They are implementing a preventive fix in case it happens again. We will continue to monitor this situation.

Investigating: We have received reports about people being unable to publish to Facebook. We are investigating the issue.

Monitoring: We are not observing any further issues at this time. The system remains stable following the applied fix, and we continue to monitor

Monitoring: We have seen no further issues at this time, and we continue to monitor on our end.

Monitoring: A fix has been applied, and the issue should be resolved. We are monitoring the situation.

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

Investigating: We are currently investigating this issue.