Khoros Status

Monitoring: The underlying issue has been resolved, and Care is now fully operational for all new and open content. We are working on a plan for recovering historical data in a phased manner. This will take some time, and we will follow up once we have an ETA. We sincerely appreciate your patience and understanding during this time. Please feel free to reach out to our support for assistance if you continue to experience issues with the new content.

Identified: The maintenance has been completed, and we are currently working to restore Care for open and new cases. This is expected to take approximately one more hour. We will share the estimated timeline for the recovery of historical data in our next update.

Identified: To resolve the current issue, we will be taking down Care for maintenance. We will update you as soon as it is back online.

Identified: We continue to work on the resolution and will keep you posted further as we have an update.

Identified: We continue to work towards the resolution, and we will keep you updated on the progress.

Investigating: We have identified an infrastructure issue that affects the search functionality, content appearance, and prevents agents from performing tasks in Care. This issue only affects the customers hosted in the AMER region.

Our engineering teams are actively working towards the resolution, and we will keep you updated on the progress as we have more info.

Investigating: We are actively working on the issue, and will share more info as we have it.

Investigating: This issue affects all AMER customers and impacts the performance of Care operations. We are actively troubleshooting the issue, and we will keep you updated as soon as we have more details.

Investigating: We are experiencing performance degradation in Care, which affects a subset of customers from the AMER region. We are actively investigating the issue, and we will keep you updated on the progress.

Monitoring: We experienced an issue with Facebook API. As a result, we noticed failure in responses on Facebook private conversations/DMs between 05:00 AM PST to 05:39 AM PST, 3rd Jan.

We will continue to monitor the situation and provide further updates accordingly.

Resolved: This incident has been resolved.

Monitoring: We want to inform you about an incident with Flow that occurred on 20th June, 2025, between 03:00 AM CDT and 04:55 AM CDT. During the incident, the Flow login service, promotions, outbound messages/broadcasts, and other core services in Flow were affected.

Our engineering team has taken the necessary measures and restored the affected services. We are actively monitoring the situation and will provide further updates as available.

Resolved: This incident has been resolved.

Monitoring: We want to inform you about an incident with Flow that occurred on 20th June, 2025, between 03:00 AM CDT and 04:55 AM CDT. During the incident, the Flow login service, promotions, outbound messages/broadcasts, and other core services in Flow were affected.

Our engineering team has taken the necessary measures and restored the affected services. We are actively monitoring the situation and will provide further updates as available.

Resolved: This incident has been resolved.

Monitoring: We want to inform you about an incident with Flow that occurred on 20th June, 2025, between 03:00 AM CDT and 04:55 AM CDT. During the incident, the Flow login service, promotions, outbound messages/broadcasts, and other core services in Flow were affected.

Our engineering team has taken the necessary measures and restored the affected services. We are actively monitoring the situation and will provide further updates as available.

Resolved: This incident has been resolved.

Monitoring: We want to inform you about an incident with Flow that occurred on 20th June, 2025, between 03:00 AM CDT and 04:55 AM CDT. During the incident, the Flow login service, promotions, outbound messages/broadcasts, and other core services in Flow were affected.

Our engineering team has taken the necessary measures and restored the affected services. We are actively monitoring the situation and will provide further updates as available.

Resolved: This incident has been resolved.

Monitoring: We want to inform you about an incident with Flow that occurred on 20th June, 2025, between 03:00 AM CDT and 04:55 AM CDT. During the incident, the Flow login service, promotions, outbound messages/broadcasts, and other core services in Flow were affected.

Our engineering team has taken the necessary measures and restored the affected services. We are actively monitoring the situation and will provide further updates as available.

Resolved: This incident has been resolved.

Monitoring: We want to inform you about an incident with Flow that occurred on 20th June, 2025, between 03:00 AM CDT and 04:55 AM CDT. During the incident, the Flow login service, promotions, outbound messages/broadcasts, and other core services in Flow were affected.

Our engineering team has taken the necessary measures and restored the affected services. We are actively monitoring the situation and will provide further updates as available.

Monitoring: We experienced an issue with Facebook API. As a result, we noticed failure in responses on Facebook private conversations/DMs between 05:00 AM PST to 05:39 AM PST, 3rd Jan.

We will continue to monitor the situation and provide further updates accordingly.