Khoros Outage History

Khoros is up right now

Pingoru has recorded 76 incidents for Khoros: 71 in the last 12 months and 4 in the last 90 days.

Source: status.khoros.com

76incidents recorded
71last 12 months
4last 90 days
3 daystypical duration
Incidents per month
0510AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Khoros in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20268491 of 720 (68%)
May 20269454 of 744 (61%)
June 20267569 of 720 (79%)
July 2026598 of 744 (13%)
August 2026125 of 744 (3%)
September 202619 of 720 (1%)
October 202600 of 588 (0%)

Incidents, newest first

Major April 27, 2026 Khoros Care Agent view - delays in sending, closed interactions returning after close, and occasional blank interaction pane 1d 22h Agent View

Started Apr 27, 2026, 09:02 AM UTC· resolved Apr 29, 2026, 07:58 AM UTC

  1. investigating Apr 27, 2026, 09:02 AM UTC

    We are currently investigating this issue.

  2. monitoring Apr 27, 2026, 12:32 PM UTC

    We have implemented a fix and are currently monitoring the situation to ensure the issue is fully resolved.

  3. monitoring Apr 28, 2026, 04:23 AM UTC

    No issues have been reported after the fix was made. We are continuing to monitor.

  4. monitoring Apr 28, 2026, 12:38 PM UTC

    We are continuing to monitor for any further updates. No issues have been observed since the fix was implemented.

  5. monitoring Apr 29, 2026, 03:31 AM UTC

    No issues reported currently. We are diligently monitoring this.

  6. resolved Apr 29, 2026, 07:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 10, 2026 [Khoros Community Classic] 403 Forbidden Error 2d 11h APAC Hosted Communities, US Hosted Communities, EU Hosted Communities

Started Apr 10, 2026, 05:40 PM UTC· resolved Apr 13, 2026, 05:33 AM UTC

  1. investigating Apr 10, 2026, 05:40 PM UTC

    We are currently investigating multiple reports about "403 Forbidden" errors when attempting to access the community. We still are gauging the impact whether it affects all regions or only US.

  2. monitoring Apr 10, 2026, 05:56 PM UTC

    We have identified the issue and applied a fix, we are monitoring the communities

  3. resolved Apr 13, 2026, 05:33 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 9, 2026 [Khoros Flow] Flow Analytics dashboards not showing data from 2026-04-08 onward 7d 11h Analytics

Started Apr 09, 2026, 03:43 PM UTC· resolved Apr 17, 2026, 03:23 AM UTC

  1. investigating Apr 09, 2026, 03:43 PM UTC

    We are currently investigating the Flow Analytics dashboards not showing data from 2026-04-08 onward

  2. identified Apr 13, 2026, 06:23 AM UTC

    The root cause for the Flow Analytics dashboards not showing data from 2026-04-08 onward was identified and fixed. We are currently backfilling the missing data for the dashboards.

  3. identified Apr 14, 2026, 03:31 AM UTC

    Our Development team is actively working on backfilling the missing analytics data. We will continue to provide updates as work progresses. We appreciate your patience and apologize for any disruption to your reporting workflows.

  4. identified Apr 15, 2026, 07:24 AM UTC

    Our Development team is still working on backfilling the missing analytics data. We will continue to provide updates as work progresses. We appreciate your patience and apologize for any disruption to your reporting workflows.

  5. identified Apr 16, 2026, 05:54 AM UTC

    We have encountered some technical challenges during the backfill process, which is causing it to take longer than expected. We are actively working to resolve these challenges and will keep you informed as we make progress. We apologize for any inconvenience this may have caused to your reporting workflows.

  6. resolved Apr 17, 2026, 03:23 AM UTC

    The Flow Analytics dashboards are now functioning normally and displaying data as expected. However, due to the complexity of the backfill process, restoring historical data will continue to be tracked on a per-customer basis through support tickets. If you have any questions or concerns about your Flow Analytics dashboards, please don’t hesitate to reach out to our Support team.

Read the full incident report →

Critical April 2, 2026 [AMER] Community posts are not being ingested into Care 1d 12h Khoros Community Integration

Started Apr 02, 2026, 05:03 PM UTC· resolved Apr 04, 2026, 05:13 AM UTC

  1. investigating Apr 02, 2026, 05:03 PM UTC

    We are investigating the issue where community posts are not being ingested into Care for 4/2, for AMER hosted communities

  2. identified Apr 02, 2026, 07:53 PM UTC

    The fix was implemented, and we can see the new posts are being ingested. We are yet to see if the auto-reconciliation process will resolve the past problems, or if there will be a need for a separate backfill.

  3. monitoring Apr 03, 2026, 08:33 PM UTC

    The backfill has been finished. We are monitoring the situation for any residual issues.

  4. resolved Apr 04, 2026, 05:13 AM UTC

    We have confirmed that no further issues were detected during our monitoring. This incident has been resolved.

Read the full incident report →

Major April 2, 2026 Some Khoros Community instances are down with error 500 1d 2h US Hosted Communities, EU Hosted Communities

Started Apr 02, 2026, 12:16 AM UTC· resolved Apr 03, 2026, 02:19 AM UTC

  1. investigating Apr 02, 2026, 12:16 AM UTC

    We are currently investigating the issues with some of the Khoros Community instances being down with 500 error.

  2. identified Apr 02, 2026, 12:53 AM UTC

    We have identified the issue affecting some Khoros Community instances resulting in 500 errors. Our engineering team is actively working on implementing a fix. We will continue to provide updates as more information becomes available. Thank you for your patience.

  3. monitoring Apr 02, 2026, 02:02 AM UTC

    A fix has been implemented for the issue affecting Khoros Community instances that were returning 500 errors. We are currently monitoring the systems to ensure stability and full recovery. Thank you for your continued patience. We will share further updates as they become available.

  4. monitoring Apr 02, 2026, 02:19 PM UTC

    We continue to observe stable performance across Khoros Community instances following the deployed fix. Monitoring will remain in place to ensure continued stability.

  5. monitoring Apr 02, 2026, 09:27 PM UTC

    We continue to observe stable performance across Khoros Community instances following the deployed fix. Monitoring will remain in place to ensure continued stability.

  6. resolved Apr 03, 2026, 02:19 AM UTC

    The incident has been resolved.

Read the full incident report →

Major March 27, 2026 Staging Environments - Admin Panel Inaccessible 502 Bad Gateway Error 23h 31m US Hosted Communities

Started Mar 27, 2026, 04:19 PM UTC· resolved Mar 28, 2026, 03:51 PM UTC

  1. investigating Mar 27, 2026, 04:19 PM UTC

    We are currently investigating reports of Admin panel innaccessible due to 502 bad gateway errors on Staging environments

  2. identified Mar 27, 2026, 09:53 PM UTC

    We have identified the cause of the 502 bad gateway errors on Staging environments, and we are rolling out fixes for each of the environments now.

  3. identified Mar 28, 2026, 05:39 AM UTC

    Most communities are online, and our Infrastructure team continue to invesitgate the remaining issues.

  4. resolved Mar 28, 2026, 03:51 PM UTC

    All communities are now online. Thank you for your patience

Read the full incident report →

Critical March 20, 2026 Khoros Flow Service Outage – UI & API Unavailable (All Regions) 2d 7h Core System

Started Mar 20, 2026, 07:56 AM UTC· resolved Mar 22, 2026, 03:02 PM UTC

  1. investigating Mar 20, 2026, 07:56 AM UTC

    We are currently investigating this issue.

  2. identified Mar 20, 2026, 09:03 AM UTC

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

  3. monitoring Mar 20, 2026, 09:33 AM UTC

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

  4. monitoring Mar 20, 2026, 08:08 PM UTC

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

  5. monitoring Mar 21, 2026, 05:43 PM UTC

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

  6. resolved Mar 22, 2026, 03:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 17, 2026 User logins fails with 504 timeout 2d 8h EU Hosted Care, US Hosted Care

Started Mar 17, 2026, 03:11 PM UTC· resolved Mar 20, 2026, 12:10 AM UTC

  1. investigating Mar 17, 2026, 03:11 PM UTC

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

  2. investigating Mar 17, 2026, 03:16 PM UTC

    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.

  3. identified Mar 17, 2026, 04:11 PM UTC

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

  4. investigating Mar 18, 2026, 02:19 AM UTC

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

  5. monitoring Mar 19, 2026, 12:19 AM UTC

    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.

  6. resolved Mar 20, 2026, 12:10 AM UTC

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

Read the full incident report →

Minor March 16, 2026 [EMEA] Analytics data not updated 14d 18h EU Hosted Communities, Analytics

Started Mar 16, 2026, 10:15 AM UTC· resolved Mar 31, 2026, 04:34 AM UTC

  1. investigating Mar 16, 2026, 10:15 AM UTC

    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.

  2. investigating Mar 16, 2026, 10:16 AM UTC

    We are continuing to investigate this issue.

  3. identified Mar 17, 2026, 01:36 AM UTC

    We have identified the issue and are in the process of developing a fix for the same.

  4. identified Mar 17, 2026, 10:07 AM UTC

    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.

  5. monitoring Mar 17, 2026, 10:07 AM UTC

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

  6. identified Mar 17, 2026, 10:34 AM UTC

    Backfill processing is currently underway.

  7. identified Mar 18, 2026, 12:50 AM UTC

    Backfilling of data is in progress for the 9th and the jobs continue to run as expected.

  8. monitoring Mar 19, 2026, 12:22 AM UTC

    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.

  9. monitoring Mar 19, 2026, 11:50 PM UTC

    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.

  10. monitoring Mar 20, 2026, 10:00 AM UTC

    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.

  11. monitoring Mar 20, 2026, 10:48 AM UTC

    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.

  12. monitoring Mar 20, 2026, 07:58 PM UTC

    Backfill for March 15th for the affected EU data is completed.

  13. monitoring Mar 22, 2026, 03:06 PM UTC

    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

  14. monitoring Mar 23, 2026, 01:48 AM UTC

    Backfill for 16th March is under progress. We will share another update once processing and validation have been completed.

  15. monitoring Mar 23, 2026, 10:20 PM UTC

    Backfill for 15th March has been completed. The backfill for the 16th is now commencing.

  16. monitoring Mar 24, 2026, 12:18 PM UTC

    Backfill for 16th March has been completed. The backfill for the 17th is now in progress.

  17. monitoring Mar 24, 2026, 10:42 PM UTC

    Our Infrastructure team are investigating and fixing an issue with the backfill for 17th and 18th. The backfilling efforts will resume shortly.

  18. monitoring Mar 24, 2026, 10:57 PM UTC

    Our Infrastructure team have resolved the issue, and the backfills for the 17th onwards are proceeding.

  19. monitoring Mar 25, 2026, 12:59 PM UTC

    Backfill for 17th March has been completed. The backfill for the 18th is now in progress.

  20. monitoring Mar 26, 2026, 09:18 PM UTC

    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.

  21. monitoring Mar 27, 2026, 05:01 PM UTC

    The backfill for the 20th and 21st has completed, and the 22nd is in progress.

  22. monitoring Mar 28, 2026, 12:09 AM UTC

    The backfill for the 22nd has completed, and the remaining days are in progress.

  23. monitoring Mar 28, 2026, 08:12 PM UTC

    We have improved the speed of backfills, and expect to catch up on the remaining backfills over the next 2 days

  24. monitoring Mar 29, 2026, 01:21 PM UTC

    We have completed the backfill, and the data for March 28th is expected to be completed in time. We continue to monitor the situation

  25. monitoring Mar 30, 2026, 11:58 PM UTC

    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.

  26. resolved Mar 31, 2026, 04:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 13, 2026 Khoros Marketing fails to publish to Facebook 4d 5h Organic Publishing, Paid Publishing

Started Mar 13, 2026, 07:20 PM UTC· resolved Mar 18, 2026, 12:42 AM UTC

  1. investigating Mar 13, 2026, 07:20 PM UTC

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

  2. monitoring Mar 13, 2026, 11:28 PM UTC

    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.

  3. monitoring Mar 14, 2026, 08:14 PM UTC

    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.

  4. monitoring Mar 16, 2026, 01:52 AM UTC

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

  5. monitoring Mar 16, 2026, 09:40 AM UTC

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

  6. monitoring Mar 16, 2026, 01:26 PM UTC

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

  7. monitoring Mar 17, 2026, 01:47 AM UTC

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

  8. monitoring Mar 17, 2026, 09:42 AM UTC

    We are continuing to monitor this.

  9. resolved Mar 18, 2026, 12:42 AM UTC

    We have confirmed that this issue is now resolved.

Read the full incident report →

Major March 12, 2026 Khoros Care chats cannot be responded 1d 1h APAC Hosted Care, EU Hosted Care, US Hosted Care

Started Mar 12, 2026, 08:45 PM UTC· resolved Mar 13, 2026, 10:00 PM UTC

  1. investigating Mar 12, 2026, 08:45 PM UTC

    We are an investigating an issue where Khoros Care chats either cannot be assigned or answered.

  2. monitoring Mar 12, 2026, 11:11 PM UTC

    We have implemented a fix for the issue where Khoros Care chats were unable to be assigned or responded to. We are actively monitoring the situation.

  3. monitoring Mar 13, 2026, 05:22 AM UTC

    We have started received confirmations that the issue is no longer seen. We are continuing to monitor this.

  4. resolved Mar 13, 2026, 10:00 PM UTC

    We have confirmed that the issue with Khoros Chats has now been resolved.

Read the full incident report →

Minor March 12, 2026 Delays in Community-to-Care Ingestions 12d 4h Khoros Community Integration

Started Mar 12, 2026, 05:31 PM UTC· resolved Mar 24, 2026, 10:10 PM UTC

  1. investigating Mar 12, 2026, 05:31 PM UTC

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

  2. investigating Mar 12, 2026, 11:39 PM UTC

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

  3. investigating Mar 13, 2026, 11:08 AM UTC

    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.

  4. identified Mar 13, 2026, 10:52 PM UTC

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

  5. monitoring Mar 15, 2026, 12:41 PM UTC

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

  6. monitoring Mar 16, 2026, 01:49 AM UTC

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

  7. monitoring Mar 16, 2026, 09:35 AM UTC

    We continue to monitor backfilling for the affected dates.

  8. monitoring Mar 17, 2026, 01:40 AM UTC

    Monitoring continues as backfilling for the affected dates progresses.

  9. monitoring Mar 18, 2026, 12:54 AM UTC

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

  10. monitoring Mar 19, 2026, 12:15 AM UTC

    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.

  11. monitoring Mar 19, 2026, 11:53 PM UTC

    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.

  12. monitoring Mar 20, 2026, 03:36 AM UTC

    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.

  13. monitoring Mar 20, 2026, 08:19 PM UTC

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

  14. monitoring Mar 23, 2026, 09:00 AM UTC

    Our Infrastructure team are still working on the missing backfilled data. We will share another update as soon as processing is complete.

  15. monitoring Mar 23, 2026, 10:41 PM UTC

    The backfilling has now been completed. We will now monitor this for any further issues

  16. resolved Mar 24, 2026, 10:10 PM UTC

    This issue has been resolved. We have seen no further issues during our monitoring.

Read the full incident report →

Major March 9, 2026 Delays in ingestion from Communities to Care 22h 58m APAC Hosted Care, EU Hosted Care, US Hosted Care

Started Mar 09, 2026, 11:12 PM UTC· resolved Mar 10, 2026, 10:10 PM UTC

  1. identified Mar 09, 2026, 11:12 PM UTC

    We are aware of an issue with delays in ingestion from Communities to Care. Our Infrastructure team have identified the issue, and we will provide further updates as they become available.

  2. identified Mar 10, 2026, 05:28 AM UTC

    Our Infrastructure team has identified the root cause and is actively working on a fix for the same.

  3. monitoring Mar 10, 2026, 12:23 PM UTC

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

  4. resolved Mar 10, 2026, 10:10 PM UTC

    We have resolved the issue causing delays in ingestion from Communities to Care.

Read the full incident report →

Major March 9, 2026 Analytics dashboards fail intermittently 3d 12h Analytics

Started Mar 09, 2026, 12:55 PM UTC· resolved Mar 13, 2026, 12:55 AM UTC

  1. identified Mar 09, 2026, 12:55 PM UTC

    We have reports of analytics dashboards failing intermittently, and we are working to resolve the issue.

  2. monitoring Mar 09, 2026, 01:34 PM UTC

    Sites have recovered and should now be live. We are looking into a permanent fix to prevent the recurrence of the issue.

  3. monitoring Mar 09, 2026, 11:00 PM UTC

    Our Engineering team are working on the permanent fix for this issue.

  4. monitoring Mar 10, 2026, 05:20 AM UTC

    We are continuing to monitor the sites' stability following the recovery.

  5. monitoring Mar 10, 2026, 10:44 PM UTC

    Our Engineering team have identified the long term fix and we will monitor for stability after the deployment.

  6. monitoring Mar 11, 2026, 05:58 AM UTC

    Our Engineering team is continuing to work on the permanent fix.

  7. monitoring Mar 12, 2026, 04:57 AM UTC

    A fix has been made by the Engineering and we are now in the process of deploying it.

  8. monitoring Mar 12, 2026, 11:44 PM UTC

    Our Infrastructure team are finalizing the deployment, and we expect this to be completed shortly.

  9. resolved Mar 13, 2026, 12:55 AM UTC

    Infrastructure team has completed the deployment. The issue with Analytics dashboard is resolved.

Read the full incident report →

Major March 2, 2026 [AMER] Khoros Communities analytics and bulk API return incomplete data for dates past 2026-02-27 2d 15h US Hosted Communities, Analytics

Started Mar 02, 2026, 12:25 PM UTC· resolved Mar 05, 2026, 03:28 AM UTC

  1. investigating Mar 02, 2026, 12:25 PM UTC

    We are currently investigating the issue with Khoros Community Analytics not being displayed past 2026-02-27

  2. identified Mar 02, 2026, 12:46 PM UTC

    We have identified the issue which caused Analytics polling to fail, and we are working on backfilling the data. The backfill for the 2026-02-28 is in progress

  3. identified Mar 03, 2026, 04:33 AM UTC

    The backfill for February 28 and March 1 have completed. Analytics data for these dates should now be visible in dashboards and via the Bulk API. We will continue to monitor the workflow closely and provide further updates as needed.

  4. monitoring Mar 04, 2026, 03:49 AM UTC

    The backfill for March 2 has now completed and analytics processing has returned to normal daily job runs. All missing data should now be available in dashboards and via the Bulk API. We will continue to monitor the data ingestion pipeline over the next 24 hours to ensure stability.

  5. resolved Mar 05, 2026, 03:28 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 21, 2026 Khoros Care: Users unable to login to application 18h 32m APAC Hosted Care, EU Hosted Care, US Hosted Care

Started Feb 21, 2026, 09:14 AM UTC· resolved Feb 22, 2026, 03:46 AM UTC

  1. investigating Feb 21, 2026, 09:14 AM UTC

    We are aware of an issue preventing some users from passing the welcome screen when logging into Khoros Care. Our Infrastructure team are actively investigating this issue.

  2. identified Feb 21, 2026, 09:38 AM UTC

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

  3. monitoring Feb 21, 2026, 11:05 AM UTC

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

  4. identified Feb 21, 2026, 11:21 AM UTC

    We have identified additional issue since our last fix, and we are working on it.

  5. monitoring Feb 21, 2026, 11:35 AM UTC

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

  6. resolved Feb 22, 2026, 03:46 AM UTC

    The issue has been resolved.

Read the full incident report →

Major February 18, 2026 Khoros Care - Login Issues 1d 6h APAC Hosted Care, EU Hosted Care, US Hosted Care

Started Feb 18, 2026, 09:45 PM UTC· resolved Feb 20, 2026, 04:23 AM UTC

  1. investigating Feb 18, 2026, 09:45 PM UTC

    We are aware of an issue preventing some users from passing the welcome screen when logging into Khoros Care. Our Infrastructure team are actively investigating this issue.

  2. monitoring Feb 19, 2026, 12:24 AM UTC

    We have resolved the issue preventing some users from passing the welcome screen when logging in to Khoros Care. Please ensure that browser Cache is cleared in order for the fix to apply correctly. We are actively monitoring the situation.

  3. resolved Feb 20, 2026, 04:23 AM UTC

    The issue has been resolved.

Read the full incident report →

Major February 18, 2026 Khoros Communities analytics and bulk api return incomplete data for dates past 15th of February 7d 13h APAC Hosted Communities, US Hosted Communities, EU Hosted Communities, Analytics

Started Feb 18, 2026, 08:41 PM UTC· resolved Feb 26, 2026, 10:19 AM UTC

  1. investigating Feb 18, 2026, 08:41 PM UTC

    We are currently investigating an issue where analytics and the bulk api return incomplete data for dates past the 15th of February.

  2. investigating Feb 19, 2026, 06:28 AM UTC

    We are continuing to investigate this issue.

  3. identified Feb 20, 2026, 10:15 PM UTC

    We have identified the issue which caused Analytics polling to fail, and we are working on backfilling the data. The backfill for the 18th has completed, except for one step which we are working on resolving. The backfill for the 16th is In progress and nearing completion. The backfills for the 17th and 19th are queued to start after the 16th completes.

  4. identified Feb 23, 2026, 01:46 AM UTC

    We remain actively engaged in monitoring the data backfill recovery effort across all affected dates.

  5. identified Feb 23, 2026, 10:18 AM UTC

    We continue to backfill the dates and expect this to continue during the coming day as we restore all data.

  6. identified Feb 24, 2026, 02:01 AM UTC

    The data backfilling continues to be in progress and we are monitoring the same as well.

  7. identified Feb 25, 2026, 12:35 AM UTC

    The data backfilling continues to be in progress and all jobs are currently running successfully.

  8. identified Feb 25, 2026, 03:58 AM UTC

    Data backfill continues to progress. Analytics data has been fully restored through February 20 and February 21 is available with superuser metrics still being finalized. Backfill jobs for February 22-24 are queued and processing sequentially. All jobs are currently running successfully and being monitored. We expect the pipeline to be fully caught up by Friday, February 27.

  9. identified Feb 26, 2026, 01:01 AM UTC

    Feb 15th - 24nd has been backfilled. The 25th will be backfilled on the normal schedule. We will continue to monitor this closely.

  10. resolved Feb 26, 2026, 10:19 AM UTC

    Backfills have been completed and data should now be restored. Please reach out to Customer Support should you still experience any issues.

Read the full incident report →

Major February 18, 2026 [Khoros Care] Cases and messages delayed in appearing in queues and in assignment to agents 1d 14h US Hosted Care

Started Feb 18, 2026, 07:38 AM UTC· resolved Feb 19, 2026, 09:40 PM UTC

  1. investigating Feb 18, 2026, 07:38 AM UTC

    We are experiencing an ongoing issue affecting ingestion and queue processing. As a result, cases and messages may appear in the Available queue or in agent queues much later than expected (from several minutes up to an hour or more), and assignment to agents can be delayed.

  2. identified Feb 18, 2026, 03:07 PM UTC

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

  3. identified Feb 18, 2026, 04:25 PM UTC

    The fix is currently being incrementally applied. As a result, performance is gradually improving. We will provide another update once the rollout is fully completed and performance has been fully restored.

  4. monitoring Feb 18, 2026, 06:56 PM UTC

    A fix has been implemented and we are monitoring results.

  5. resolved Feb 19, 2026, 09:40 PM UTC

    We have confirmed that the fix that was implemented has resolved this issue.

Read the full incident report →

Minor February 10, 2026 [Khoros Care] Significant delays sending messages while handling chats, and chat/case assignment appears stalled 7h 11m Agent View, Brand Messenger

Started Feb 10, 2026, 03:41 PM UTC· resolved Feb 10, 2026, 10:53 PM UTC

  1. investigating Feb 10, 2026, 03:41 PM UTC

    We are currently investigating this issue.

  2. monitoring Feb 10, 2026, 04:18 PM UTC

    The issue has been resolved and we are monitoring the results.

  3. resolved Feb 10, 2026, 10:53 PM UTC

    We have confirmed that the issue causing delays in sending chat messages and assignment stalls has been resolved.

Read the full incident report →

Critical February 4, 2026 [Khoros Care] Several functionalities impacted or failing in US Hosted Care only, EU and APAC not impacted 1d 11h US Hosted Care, Agent View, Analytics, Manage View and 1 more

Started Feb 04, 2026, 01:06 PM UTC· resolved Feb 06, 2026, 12:14 AM UTC

  1. investigating Feb 04, 2026, 01:06 PM UTC

    We are experiencing an ongoing issue affecting the Khoros Care Manage View. As a result, users may be unable to access the Manage View and see a server communication error. Our Infrastructure team is working to resolve this issue.

  2. investigating Feb 04, 2026, 02:47 PM UTC

    We are continuing to investigate the issue. Further updates will be shared as more information becomes available.

  3. investigating Feb 04, 2026, 03:28 PM UTC

    We are continuing to investigate this issue.

  4. investigating Feb 04, 2026, 05:08 PM UTC

    This issue is limited to US-hosted Care environments. EU and APAC regions are not impacted. Our teams are actively investigating and will provide updates as more information becomes available.

  5. monitoring Feb 05, 2026, 12:27 AM UTC

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

  6. resolved Feb 06, 2026, 12:14 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 26, 2026 Khoros Care - degraded performance with message delivery. 14h 30m EU Hosted Care, US Hosted Care

Started Jan 26, 2026, 11:19 AM UTC· resolved Jan 27, 2026, 01:50 AM UTC

  1. investigating Jan 26, 2026, 11:19 AM UTC

    We are investigating reports of degraded performance in Khoros Care that are affecting agent console responsiveness and message delivery (delays in sending and receiving messages, as well as in claiming and assigning conversations).

  2. investigating Jan 26, 2026, 11:54 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jan 26, 2026, 12:54 PM UTC

    The affected systems have automatically recovered, and the previously observed delays are no longer occurring. We are continuing to actively monitor system performance to ensure ongoing stability.

  4. resolved Jan 27, 2026, 01:50 AM UTC

    The performance degradation impacting agent console responsiveness and message delivery has been resolved.

Read the full incident report →

Major January 21, 2026 Khoros Community Azure outage 4m US Hosted Communities, EU Hosted Communities

Started Jan 21, 2026, 01:50 AM UTC· resolved Jan 21, 2026, 01:55 AM UTC

  1. identified Jan 21, 2026, 01:50 AM UTC

    Khoros Community Azure outage is currently observed. This was caused by incorrectly rolled out changes, and we are in the process of rolling back the changes now.

  2. resolved Jan 21, 2026, 01:55 AM UTC

    The rollback has been completed and this incident is resolved.

Read the full incident report →

Notice January 20, 2026 Analytics data not updated 1d 19h Analytics

Started Jan 20, 2026, 11:26 AM UTC· resolved Jan 22, 2026, 06:51 AM UTC

  1. investigating Jan 20, 2026, 11:26 AM UTC

    We are currently investigating an issue that is affecting analytics data. Data are not populated since the 16th of January. Our infrastructure team is working on this with Urgent priority.

  2. identified Jan 20, 2026, 01:39 PM UTC

    We have identified the analytics data population issue and our teams applied a fix. Source systems are confirmed healthy, and backfill processing is currently underway. We will share further updates as they become available.

  3. identified Jan 20, 2026, 03:29 PM UTC

    We are continuing the backfill operations, we will share further updates as they become available

  4. identified Jan 21, 2026, 03:44 AM UTC

    The backfill operations are in progress and our teams are monitoring the same as well.

  5. monitoring Jan 22, 2026, 02:13 AM UTC

    The backfill operations have been completed and we are continuing to monitor.

  6. resolved Jan 22, 2026, 06:51 AM UTC

    The issue has been fully resolved. Our teams have confirmed system stability, and all services are operating normally.

Read the full incident report →

Major January 16, 2026 [Khoros Care & Marketing] LinkedIn integration outage 2d 12h Organic Publishing, Third-party APIs

Started Jan 16, 2026, 03:06 PM UTC· resolved Jan 19, 2026, 03:11 AM UTC

  1. identified Jan 16, 2026, 03:06 PM UTC

    We are experiencing an ongoing outage affecting our LinkedIn integration. As a result, it is not possible to reply to existing messages, and no new messages will be ingested. Our Engineering team is working to resolve this issue urgently.

  2. identified Jan 16, 2026, 04:40 PM UTC

    We have identified the root cause being a deprecated service from LinkedIn requiring a change in our codebase. Our team is still looking into this matter.

  3. identified Jan 16, 2026, 05:38 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Jan 16, 2026, 08:16 PM UTC

    The fix has been deployed, and we believe the issue is resolved.

  5. resolved Jan 19, 2026, 03:11 AM UTC

    The issue affecting the LinkedIn integration has been resolved. The fix has been deployed, and message ingestion and replies are now functioning as expected. If you continue to experience any issues, please contact Support for further assistance.

Read the full incident report →