Khoros Outage History

Started Jan 14, 2026, 05:40 PM UTC· resolved Jan 15, 2026, 12:38 PM UTC

1. investigating Jan 14, 2026, 05:40 PM UTC

   We are currently investigating an increased rate of 403 errors reported by several customers (global)

2. identified Jan 14, 2026, 07:30 PM UTC

   The issue has been identified and the fix is being applied.

3. monitoring Jan 15, 2026, 01:47 AM UTC

   The issue causing 403 errors when loading assets has now been fixed. We are actively monitoring to ensure that that no further issues occur.

4. resolved Jan 15, 2026, 12:38 PM UTC

   The issue causing 403 errors when loading assets has now been fixed, and no reoccurrences have been reported. Please reach out to Customer Support if you require additional assistance.

Read the full incident report →

Started Jan 08, 2026, 12:42 PM UTC· resolved Jan 11, 2026, 07:18 AM UTC

1. investigating Jan 08, 2026, 12:42 PM UTC

   We are currently experiencing an issue where analytics data is unavailable for Posts and Marketing dashboards over the past few days. Our team is investigating the cause and working toward a resolution. We will share updates as more details become available.

2. identified Jan 09, 2026, 03:05 AM UTC

   We have implemented a fix and have started the backfill process for the affected analytics data. We will continue to monitor progress and share further updates as we move toward full resolution.

3. monitoring Jan 09, 2026, 07:28 AM UTC

   The issue has been fixed now, we are closely monitoring now.

4. monitoring Jan 10, 2026, 10:07 AM UTC

   We are continuing to closely monitor the system to ensure stability and completion of the data backfill. Further updates will be shared if needed.

5. resolved Jan 11, 2026, 07:18 AM UTC

   This incident has been fully resolved, and no further issues have been observed during ongoing monitoring.

Read the full incident report →

Started Jan 07, 2026, 04:09 PM UTC· resolved Jan 08, 2026, 01:08 AM UTC

1. investigating Jan 07, 2026, 04:09 PM UTC

   We are currently investigating the issues with some of the instances being down with "An error occurred while processing your request."

2. monitoring Jan 07, 2026, 04:36 PM UTC

   The fix has been implemented, and the issue is currently resolved.

3. resolved Jan 08, 2026, 01:08 AM UTC

   The issue impacting some Khoros Community Aurora instances, where users encountered the message “An error occurred while processing your request", has been successfully resolved.

Read the full incident report →

Started Jan 06, 2026, 03:01 PM UTC· resolved Jan 07, 2026, 01:34 AM UTC

1. investigating Jan 06, 2026, 03:01 PM UTC

   We are investigating reports of style issues within Khoros Communities, including incorrect CSS rendering. Further updates will be shared as they become available.

2. identified Jan 06, 2026, 04:22 PM UTC

   The issue has been identified, and we are in the process of rolling out the fix.

3. monitoring Jan 06, 2026, 11:06 PM UTC

   Our infrastructure team has applied a fix and we are monitoring the results.

4. resolved Jan 07, 2026, 01:34 AM UTC

   The issue causing style inconsistencies and incorrect CSS rendering in Khoros Communities has been fully resolved. Our teams have confirmed system stability, and all services are operating normally at this time. If you continue to experience any issues, please contact Support.

Read the full incident report →

Started Dec 16, 2025, 08:27 AM UTC· resolved Dec 16, 2025, 05:48 PM UTC

1. investigating Dec 16, 2025, 08:27 AM UTC

   We are currently investigating an issue with the Community <> Care post ingestion.

2. monitoring Dec 16, 2025, 08:50 AM UTC

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

3. resolved Dec 16, 2025, 05:48 PM UTC

   The issue affecting the Community <> Care post ingestion has been fully resolved. A fix was successfully implemented, and monitoring confirmed that posts are now being ingested and processed as expected. No further impact has been observed, and the integration is operating normally.

Read the full incident report →

Started Dec 15, 2025, 04:08 AM UTC· resolved Dec 15, 2025, 05:01 PM UTC

1. investigating Dec 15, 2025, 04:08 AM UTC

   We are currently investigating an issue where the Manage Views tab is not visible in the Khoros Care Console UI for some users. This may prevent access to Manage View–related functionality. Our team is actively working to identify the root cause and will provide updates as more information becomes available.

2. monitoring Dec 15, 2025, 05:08 AM UTC

   Our infrastructure team has implemented a fix, and the reported issue is no longer reproducible. We are continuing to monitor the situation to ensure stability.

3. resolved Dec 15, 2025, 05:01 PM UTC

   The issue affecting the visibility of the Manage Views tab in the Khoros Care Console has been resolved. The fix has been successfully implemented, and the reported behavior is no longer reproducible. All affected functionality has been restored, and we will continue to monitor the system to ensure ongoing stability.

Read the full incident report →

Started Dec 10, 2025, 02:25 AM UTC· resolved Dec 10, 2025, 09:55 AM UTC

1. investigating Dec 09, 2025, 10:17 PM UTC

   We are aware of an intermittent issue affecting Khoros Care, where some agents are unable to communicate with clients, and some are experiencing login difficulties. Our team is actively investigating the root cause and will provide further updates as they become available.

2. identified Dec 10, 2025, 12:46 AM UTC

   The issue has been identified and we are working on implementing fix

3. monitoring Dec 10, 2025, 02:25 AM UTC

   A fix has been implemented and we are monitoring results.

4. resolved Dec 10, 2025, 09:55 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 08, 2025, 04:06 PM UTC· resolved Dec 12, 2025, 04:09 AM UTC

1. investigating Dec 08, 2025, 04:06 PM UTC

   We are currently investigating an issue where the virus scan stuck in progress for all attachments.

2. identified Dec 08, 2025, 04:27 PM UTC

   The issue has been identified, and our team is working on deploying a potential fix in stages, starting with the Staging, Demo and Preproduction instances.

3. identified Dec 08, 2025, 11:39 PM UTC

   Demo, Stage, and APAC communities have been updated with a fix for this issue. The fix is rolling out for EMEA communities now, and US communities will follow during the assigned maintenance window.

4. identified Dec 09, 2025, 02:32 AM UTC

   The fix rollout for EMEA has been completed now. The fix for US communities will follow in assigned maintenance window.

5. identified Dec 09, 2025, 07:06 AM UTC

   We have determined that the earlier fix did not fully resolve the antivirus scanning issue. Our team is now implementing an enhanced solution designed to address all remaining edge cases.

6. identified Dec 09, 2025, 03:28 PM UTC

   Our Engineering team has released a new version internally to fix this issue. It will be rolled out to EU Prod Hosted communities shortly, we will update when we have finished the rollout.

7. identified Dec 09, 2025, 05:58 PM UTC

   We have deployed a fix that we believe has fixed the issue for EMEA, we are currently monitoring and validating it. We will follow with the roll-out to APAC region shortly after validation.

8. identified Dec 09, 2025, 07:25 PM UTC

   We have validated the fix for the EMEA region, and will proceed with the deployment for the APAC region.

9. monitoring Dec 09, 2025, 08:21 PM UTC

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

10. monitoring Dec 10, 2025, 04:00 AM UTC

    All regions are working fine currently. We are continuing to monitor.

11. monitoring Dec 11, 2025, 04:02 AM UTC

    All regions are operating normally at this time; monitoring is ongoing.

12. resolved Dec 12, 2025, 04:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Started Nov 19, 2025, 04:14 AM UTC· resolved Nov 20, 2025, 03:23 AM UTC

1. investigating Nov 19, 2025, 04:14 AM UTC

   We are currently investigating an issue causing slow loading of the Marketing Calendar and impacting calendar publishing functionality. We will share further updates as we work toward a resolution.

2. identified Nov 19, 2025, 07:44 AM UTC

   We’ve pinpointed the issues causing slow performance in the Marketing Calendar and have begun implementing fixes. Our team is actively working toward a complete resolution and will provide further updates as progress continues.

3. monitoring Nov 19, 2025, 09:00 AM UTC

   We have applied a fix to address the slow-loading behavior and related issues in the Marketing Calendar, and initial monitoring shows performance improvements. We are continuing to monitor the situation to ensure stability.

4. resolved Nov 20, 2025, 03:23 AM UTC

   We have successfully implemented a fix for the slow-loading behavior in the Marketing Calendar, and initial monitoring indicates restored functionality. We will close the incident as system performance is now stable and will keep observing to ensure continued reliability.

Read the full incident report →

Started Nov 18, 2025, 01:04 PM UTC· resolved Nov 18, 2025, 11:00 PM UTC

1. identified Nov 18, 2025, 01:04 PM UTC

   We are currently experiencing an ongoing Cloudflare incident that is impacting Khoros Community third-party integrations. You can follow the upstream incident here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 If you are using a reverse proxy or any integration that relies on Cloudflare, please contact Cloudflare for additional support. We are actively monitoring the situation and will continue to provide updates as Cloudflare works toward a resolution.

2. monitoring Nov 18, 2025, 03:21 PM UTC

   Cloudflare has resolved the issue and we are monitoring the situation

3. resolved Nov 18, 2025, 11:00 PM UTC

   The Cloudflare outage has now been resolved: https://www.cloudflarestatus.com/

Read the full incident report →

Started Nov 18, 2025, 01:01 PM UTC· resolved Nov 18, 2025, 10:59 PM UTC

1. identified Nov 18, 2025, 01:01 PM UTC

   We are currently experiencing an ongoing Cloudflare incident that is impacting the Khoros Flow Bot Functionalities. You can track the upstream incident here: https://www.cloudflarestatus.com/incidents/8gmgl95oj3h7 Our team is actively monitoring the situation and awaiting further updates from Cloudflare as they work toward a resolution.

2. monitoring Nov 18, 2025, 03:21 PM UTC

   Cloudflare issue is fixed, and we are monitoring the situation for further updates.

3. resolved Nov 18, 2025, 10:59 PM UTC

   The Cloudflare outage has now been resolved: https://www.cloudflarestatus.com/

Read the full incident report →

Started Nov 14, 2025, 05:08 PM UTC· resolved Nov 25, 2025, 09:58 AM UTC

1. investigating Nov 14, 2025, 05:08 PM UTC

   We are currently investigating an issue where some Instagram Direct Messages are not being ingested into the platform. This may result in delays or missing messages for certain workspaces. Our teams are actively working to identify the root cause and restore full functionality. Further updates will follow.

2. identified Nov 17, 2025, 03:11 AM UTC

   We have identified that the issue is caused by errors within the Meta Integration API. While the frequency of these errors has decreased, we are actively working with Meta Support to fully resolve the problem. Thank you for your continued patience as we work toward restoration of normal functionality.

3. identified Nov 18, 2025, 04:34 AM UTC

   We are continuing to follow up with Meta Support regarding the ongoing issues affecting Instagram Direct Message ingestion. We remain engaged to help drive a full resolution.

4. identified Nov 19, 2025, 07:08 AM UTC

   We are actively working with Meta Support to resolve this, and we will provide further updates as they become available.

5. identified Nov 20, 2025, 05:33 AM UTC

   We continue to work closely with Meta Support to investigate and resolve the ongoing issue. We will share additional updates as soon as more information becomes available.

6. identified Nov 21, 2025, 03:08 AM UTC

   We are actively working with Meta Support to progress the investigation. Meta has enabled additional logging on their side to help pinpoint the root cause, and their team is continuing efforts toward a full resolution. We will share further updates as they become available.

7. identified Nov 23, 2025, 07:04 AM UTC

   We are still working with Meta Support on the investigation. The Meta Engineering team is working toward a full resolution. We will share further updates as they become available.

8. identified Nov 23, 2025, 04:37 PM UTC

   We continue to communicate closely with Meta Support, which is working on a permanent fix for the issue. We will share additional updates as soon as more information becomes available.

9. identified Nov 24, 2025, 02:14 PM UTC

   We are continuing to monitor the issue where Instagram Direct Messages are not being ingested into Khoros Care. Our teams remain in contact with Meta for updates and will provide further information as it becomes available.

10. identified Nov 24, 2025, 09:32 PM UTC

    Our teams continue in contact with Meta for updates and will provide further information as it becomes available.

11. monitoring Nov 25, 2025, 07:45 AM UTC

    Our teams have received confirmation from Meta that fixes were applied on their side. After testing, we have verified that Instagram Direct Messages are now successfully ingesting into Khoros Care. We will continue to monitor, but no further impact is expected at this time. Thank you for your patience throughout this incident.

12. resolved Nov 25, 2025, 09:58 AM UTC

    After multiple confirmations, we have concluded that the issue has been resolved, and messaging is now fully functional in Khoros Care. Thank you for your understanding and patience.

Read the full incident report →

Started Nov 12, 2025, 04:52 PM UTC· resolved Nov 14, 2025, 03:17 AM UTC

1. investigating Nov 12, 2025, 04:52 PM UTC

   We’ve identified an issue where the Marketing Calendar view is showing blank for some users. Our engineering team is actively investigating the root cause. We’ll provide an update as soon as we have more information. Thank you for your patience and comprehension.

2. monitoring Nov 12, 2025, 06:40 PM UTC

   Our Infrastructure team has resolved the issue causing some users to see a blank Marketing Calendar view. We are now actively monitoring the situation to ensure that the issue remains resolved.

3. investigating Nov 12, 2025, 08:58 PM UTC

   We are aware of an issue impacting some users where Content or Plans pages are not loading or loading slowly. Our Engineering teams are actively working on this.

4. identified Nov 13, 2025, 03:27 AM UTC

   We have identified the cause of the missing content on Calendar pages and confirmed the fix. Our Infrastructure team is now implementing the solution. We will share further updates as progress continues toward full resolution.

5. identified Nov 13, 2025, 10:17 AM UTC

   We continue to implement the required fix for the missing content in calendar pages. We will provide further updates as they become available.

6. identified Nov 13, 2025, 02:52 PM UTC

   Our Infrastructure team had resolved the issue with Calendar Contents. However some customers are still facing issues with Plans and Content Pages. We are continuing to work towards resolving that.

7. monitoring Nov 13, 2025, 04:37 PM UTC

   Our Infrastructure team has resolved the issue causing some users to have problems while loading the calendar views. We are now actively monitoring the situation to ensure that the issue remains resolved. Please monitor on your end and let us know if you observe any further issues.

8. resolved Nov 14, 2025, 03:17 AM UTC

   We have received confirmation that this issue has been resolved. Please reach out to Customer Support if you have any issues, and our agents will assist you in having them addressed.

Read the full incident report →

Started Nov 12, 2025, 06:56 AM UTC· resolved Nov 12, 2025, 12:05 PM UTC

1. investigating Nov 12, 2025, 06:56 AM UTC

   We are currently investigating a DNS resolution issue with Khoros Care that affects a few functionalities, primarily introducing delays in responses via various integrations.

2. identified Nov 12, 2025, 07:46 AM UTC

   We identified the root cause of delays, and a fix is being implemented.

3. monitoring Nov 12, 2025, 08:03 AM UTC

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

4. resolved Nov 12, 2025, 12:05 PM UTC

   This issue has been resolved

Read the full incident report →

Started Nov 10, 2025, 11:18 AM UTC· resolved Nov 11, 2025, 05:45 AM UTC

1. investigating Nov 10, 2025, 11:18 AM UTC

   We are aware of an issue affecting multiple communities, where they are inaccessible or very slow to load. We are currently investigating and will provide further updates as they become available.

2. identified Nov 10, 2025, 12:04 PM UTC

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

3. monitoring Nov 10, 2025, 12:04 PM UTC

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

4. monitoring Nov 11, 2025, 04:12 AM UTC

   We continue to closely monitor system performance to ensure stability across all affected communities. At this time, services are operational, and we are observing normal response times.

5. resolved Nov 11, 2025, 05:45 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 09, 2025, 04:37 PM UTC· resolved Nov 13, 2025, 09:38 AM UTC

1. investigating Nov 09, 2025, 04:37 PM UTC

   We are currently investigating an issue with Khoros Care where delays are experienced when sending Brand Messenger replies

2. investigating Nov 09, 2025, 05:13 PM UTC

   We are continuing to investigate the issue; during the investigation, we have noticed that the delays are affecting replies through different integrations.

3. investigating Nov 10, 2025, 03:07 AM UTC

   We are continuing to investigate the delays experienced with Khoros Care, specifically with Brand Messenger replies, and are exploring potential issues related to system configurations and request processing. We appreciate your patience as we work towards a resolution.

4. monitoring Nov 10, 2025, 07:41 AM UTC

   We identified the root cause of delays, and a fix has been implemented. We are monitoring the results.

5. investigating Nov 10, 2025, 02:44 PM UTC

   We are continuing to investigate the reoccurrence of delays affecting replies through various integrations. We appreciate your patience as we work towards a resolution.

6. monitoring Nov 10, 2025, 07:50 PM UTC

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

7. monitoring Nov 11, 2025, 04:24 AM UTC

   We are continuing to monitor the platform following the fix implementation. System performance remains stable, and we will keep observing metrics closely to ensure sustained recovery.

8. investigating Nov 11, 2025, 07:48 PM UTC

   We are currently investigating this issue.

9. monitoring Nov 11, 2025, 11:36 PM UTC

   Our Infrastructure team has identified the root cause of the issue that was causing delays in Khoros Care messages. We have implemented a fix for this, and are actively monitoring the results.

10. monitoring Nov 12, 2025, 06:07 AM UTC

    We are continuing to monitor performance to ensure stability.

11. monitoring Nov 13, 2025, 05:34 AM UTC

    We are continuing to closely monitor the platform, and system performance has remained stable. We have not observed any new errors, and all services are operating as expected. We will continue to track metrics to ensure sustained stability.

12. resolved Nov 13, 2025, 09:38 AM UTC

    We have received confirmation that this issue has been resolved. Please reach out to Customer Support if you have any issues, and our agents will assist you in having them addressed.

Read the full incident report →

Started Nov 03, 2025, 10:18 PM UTC· resolved Nov 05, 2025, 11:01 AM UTC

1. investigating Nov 03, 2025, 10:18 PM UTC

   We are currently investigating an issue causing all connected YouTube accounts to become automatically deauthenticated across multiple markets. As a result, scheduled posts to YouTube and other integrated platforms may not be published as expected. Some users have successfully reauthenticated their accounts but continue to receive deauthentication notifications. Others are unable to reauthenticate due to error messages. Impact Scope: YouTube integrations Scheduled post publishing Comment monitoring and moderation workflows Our engineering team is actively working with YouTube’s API team to identify the root cause and restore stable authentication. We will provide updates as soon as more information is available.

2. investigating Nov 04, 2025, 04:30 AM UTC

   We’re continuing to investigate reports of YouTube accounts automatically disconnecting, which is impacting integrations, scheduled publishing, and comment workflows. We’ll continue to share updates as soon as new information is available.

3. monitoring Nov 04, 2025, 05:50 AM UTC

   A fix has been implemented and customers can now connect/authenticate their YouTube accounts again. We are monitoring this.

4. monitoring Nov 05, 2025, 04:48 AM UTC

   We are receiving confirmations that the issue has been resolved and no new issues have been reported related to this. We will continue to monitor.

5. resolved Nov 05, 2025, 11:01 AM UTC

   This issue is now resolved, as confirmed by our users. Please reach out to Customer Support for any other queries.

Read the full incident report →

Started Nov 03, 2025, 02:43 PM UTC· resolved Nov 04, 2025, 11:35 AM UTC

1. investigating Nov 03, 2025, 02:43 PM UTC

   We are currently investigating this issue.

2. monitoring Nov 03, 2025, 03:46 PM UTC

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

3. monitoring Nov 04, 2025, 04:34 AM UTC

   We have received positive feedback on the fix and will continue to monitor the same for now.

4. resolved Nov 04, 2025, 11:35 AM UTC

   This issue has been confirmed as resolved. Please reach out to Customer Support for any other issues you may be experiencing.

Read the full incident report →

Started Oct 23, 2025, 04:47 AM UTC· resolved Oct 30, 2025, 10:33 AM UTC

1. investigating Oct 23, 2025, 04:47 AM UTC

   We are investigating an issue causing missing Community Analytics data for customers in the EMEA region since October 21st. We are also working to restore and backfill the affected analytics jobs.

2. identified Oct 23, 2025, 09:36 AM UTC

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

3. identified Oct 24, 2025, 04:01 AM UTC

   The data for October 21 has been successfully backfilled, and we are now working on backfilling the data for October 22.

4. identified Oct 25, 2025, 06:23 AM UTC

   The data for October 22 has been successfully backfilled, and we are now working on backfilling the data for October 23.

5. identified Oct 26, 2025, 06:15 AM UTC

   We’re currently experiencing an issue with the data backfill for October 23. The process did not complete successfully because some jobs became stuck. Our Infrastructure team is actively investigating the cause and working to complete the backfill as soon as possible.

6. identified Oct 26, 2025, 04:25 PM UTC

   Our Development team has fixed the issues with the October 23rd data backfill, and the Analytics data should now start appearing in the dashboards. We will continue to work on restoring the Analytics data.

7. identified Oct 27, 2025, 03:58 AM UTC

   Backfilling of the data for October 26th has been initiated and is in progress currently. This is being actively monitored by our team.

8. identified Oct 28, 2025, 11:19 AM UTC

   Our Development team has completed the backfill for October 24th data, and the Analytics data should now start appearing in the dashboards. As before, we will continue to work on restoring the Analytics data.

9. identified Oct 29, 2025, 03:03 AM UTC

   Our Development team has completed the backfill for October 25th and 26th data, and the Analytics data should now start appearing in the dashboards. As before, we will continue to work on restoring the Analytics data.

10. identified Oct 29, 2025, 05:27 AM UTC

    The restoration of data for October 28th is in progress and the backfill for October 27th will be completed after that. Although, note that there should be data starting to appear for both October 27th and 28th now. Our teams are continuing to work on this.

11. identified Oct 29, 2025, 12:15 PM UTC

    The processing of October 28th has been completed. We are now monitoring the backfill of October 27th. Our team will monitor and update here once it finishes.

12. monitoring Oct 29, 2025, 01:00 PM UTC

    The backfill for the 27th has been completed now. We see the data available on the dashboard.

13. resolved Oct 30, 2025, 10:33 AM UTC

    The backfill for October 29th has now been completed successfully, and all data should be present. Please reach out to customer support if you still experience any issues; we will be happy to assist.

Read the full incident report →

Started Oct 22, 2025, 10:57 AM UTC· resolved Oct 23, 2025, 10:08 PM UTC

1. investigating Oct 22, 2025, 10:57 AM UTC

   We are currently investigating a service disruption affecting the Khoros platform. Some users may experience issues sending messages, delays in message delivery, or temporary unavailability of the platform. Our Infrastructure team is actively investigating the root cause and working to restore full functionality as soon as possible. We understand the impact this may have on your operations and appreciate your patience while we resolve the issue. Further updates will be shared as soon as more information becomes available.

2. investigating Oct 22, 2025, 10:57 AM UTC

   We are continuing to investigate this issue.

3. monitoring Oct 22, 2025, 11:59 AM UTC

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

4. monitoring Oct 22, 2025, 11:59 AM UTC

   We are continuing to monitor for any further issues.

5. resolved Oct 23, 2025, 10:08 PM UTC

   The fix deployed by our infrastructure team has resolved the service disruption affecting the Khoros Care platform.

Read the full incident report →

Started Oct 20, 2025, 11:33 AM UTC· resolved Oct 20, 2025, 11:14 PM UTC

1. identified Oct 20, 2025, 11:33 AM UTC

   AWS has confirmed increased error rates and latencies affecting multiple services in the US-EAST-1 region. The incident is currently classified as "Degraded" by AWS. You may experience slowness, timeouts, or trouble accessing some parts of platform and services. We're closely monitoring the situation and will keep you updated as AWS provides more information.

2. resolved Oct 20, 2025, 11:14 PM UTC

   AWS has confirmed that the outage in the US-EAST-1 region has now been resolved, and all services are operational.

Read the full incident report →

Started Oct 15, 2025, 10:53 AM UTC· resolved Oct 21, 2025, 09:43 PM UTC

1. identified Oct 15, 2025, 10:53 AM UTC

   We have identified an issue with posts failing to be published with media. A fix has already been identified for this behavior.

2. identified Oct 16, 2025, 04:43 AM UTC

   Our Development team has implemented a fix for the identified publishing issue. We are now preparing a deployment that includes this fix to resolve the problem with posts containing media. Further updates will be shared once the deployment is completed and verified.

3. monitoring Oct 17, 2025, 03:16 AM UTC

   We have deployed a fix to address the publishing failures affecting posts with media. Initial monitoring indicates that the errors have stopped following the deployment. We will continue to monitor the system closely to ensure full stability.

4. resolved Oct 21, 2025, 09:43 PM UTC

   Since deploying the fix that addresses the publishing failures for Instagram video posts, we have monitored closely and confirmed that publishing is now working as expected.

Read the full incident report →

Started Sep 26, 2025, 04:34 PM UTC· resolved Oct 24, 2025, 12:38 PM UTC

1. identified Sep 26, 2025, 04:34 PM UTC

   We are currently investigating intermittent authentication issues affecting Meta (Facebook and Instagram) channel connections in Khoros Care. Impacted customers may experience periodic disconnections of their Meta social channels, requiring manual reconnection to restore message flow. Our teams are mobilized to implement a comprehensive solution. While we work on a permanent fix, affected channels can be reconnected manually to restore functionality. We understand the critical nature of social channel connectivity for your operations and apologize for any inconvenience

2. identified Sep 27, 2025, 12:06 AM UTC

   We are continuing to investigate the intermittent connection issues affecting Meta channel authentication in Khoros Care, which may require manual reconnection to restore functionality. Our team is working diligently to implement a comprehensive solution, and we appreciate your patience during this time.

3. identified Sep 29, 2025, 05:21 AM UTC

   We are continuing to investigate the Meta (Facebook/Instagram) authentication disruptions in Khoros Care. Our teams are dligently working towards a permanent resolution.

4. identified Sep 30, 2025, 03:46 AM UTC

   We are continuing to work towards a long term solution for the intermittent authentication issues impacting Meta (Facebook and Instagram) channel connections in Khoros Care. We appreciate your patience as we work towards a resolution.

5. identified Oct 03, 2025, 04:38 AM UTC

   Our Development team has implemented additional logging and monitoring for the Meta channel authentication issues. We are closely tracking error activity and continuing to work on a long-term solution to ensure stable and reliable performance.

6. identified Oct 03, 2025, 11:54 PM UTC

   We have been closely monitoring the authentication issues affecting Meta (Facebook and Instagram) channel connections in Khoros Care. At this time, we have observed no further instances of the issue. We will continue monitoring this diligently on our end. Please let us know if any further issues are observed on your end, as this will help our development team to address the issue with a robust permanent solution. Thank you for your assistance and patience in this matter.

7. monitoring Oct 06, 2025, 10:41 PM UTC

   We are continuing to monitor intermittent authentication issues impacting Meta (Facebook and Instagram) channel connections in Khoros Care. We appreciate your patience as our engineering team works toward a comprehensive solution. Thank you for your assistance and patience in this matter.

8. identified Oct 06, 2025, 10:58 PM UTC

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

9. identified Oct 08, 2025, 03:34 AM UTC

   After implementing additional logging, we haven't observed the issue in the last 4 days. We are currently monitoring backend logs for recurrence to validate and finalize the identified long-term solution.

10. identified Oct 10, 2025, 03:59 AM UTC

    Our Development team is investigating the root cause and working towards the next steps. Please notify us if you experience any further issues so we can look into them. We appreciate your patience and understanding as we work to ensure a stable experience.

11. monitoring Oct 22, 2025, 05:44 AM UTC

    The issue has been fixed now and we are monitoring the results.

12. resolved Oct 24, 2025, 12:38 PM UTC

    This incident has been resolved.

Read the full incident report →