There were 24 Khoros outages since February 4, 2026 totaling 2002h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating an issue where a subset of Khoros communities are facing performance issues.
This incident has been resolved.
We are currently investigating an issue where some customers may experience problems accessing their community portal. In some cases, the page may load incorrectly due to styling issues, making the portal difficult or impossible to use. Our team is actively working to identify the cause and restore normal functionality. We will provide another update as soon as more information is available.
A fix was implemented, and this incident has been resolved.
We are currently investigating this issue.
We have implemented a fix and are currently monitoring the situation to ensure the issue is fully resolved.
No issues have been reported after the fix was made. We are continuing to monitor.
We are continuing to monitor for any further updates. No issues have been observed since the fix was implemented.
No issues reported currently. We are diligently monitoring this.
This incident has been resolved.
We have found that there were issues with Community Analytics data not coming up from April 16 for EU Hosted communities. The data backfilling for the same is in progress currently.
We are continuing to investigate this issue.
The issue has been identified and the backfill has been triggered accordingly. Backfill is in progress and we will keep you posted with the status of the backfill
We have received reports that Analytics data is not coming up for US communities as well as EU Hosted communities. Our teams are moving forward with the backfill
The backfilling jobs are in progress and our teams are continuously monitoring them.
Backfill jobs are progressing as expected. Our teams continue to actively monitor the process.
Backfill for analytics data for all days is now complete with the exception of the 16th data for EU region; our team is still working on this.
Backfill efforts are continuing for Analytics data on April 16 in the EU region and April 21 in the AMER region. Our teams are actively monitoring the progress and will share additional updates as they become available.
The jobs are continuing to make progress and our teams are diligently monitoring the same.
The jobs continue to make steady progress, and our teams are actively monitoring them.
Right now the jobs for 2026-04-24 and 25th have failed and all communities will be missing data on these days until our Infrastructure team resolves this. We are working with the highest priority.
Our teams are continuing to look into the failures/missing data with the top most priority.
We are still investigating the missing / delayed data affecting Khoros Communities. Our teams continue to monitor the impacted jobs and are working with high priority to restore the missing data for the affected dates. At this time, the issue remains under active review, and we do not have a confirmed completion ETA yet. We will continue tracking the progress and share further updates as soon as more information becomes available.
Our teams are continuing to look into the failures/missing data with the top most priority.
The backfill is still in progress, with our teams constantly monitoring for failures/missing data
This incident has been resolved.
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.
We have identified the issue and applied a fix, we are monitoring the communities
This incident has been resolved.
We are currently investigating the Flow Analytics dashboards not showing data from 2026-04-08 onward
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.
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.
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.
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.
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.
We are investigating the issue where community posts are not being ingested into Care for 4/2, for AMER hosted communities
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.
The backfill has been finished. We are monitoring the situation for any residual issues.
We have confirmed that no further issues were detected during our monitoring. This incident has been resolved.
We are currently investigating the issues with some of the Khoros Community instances being down with 500 error.
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.
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.
We continue to observe stable performance across Khoros Community instances following the deployed fix. Monitoring will remain in place to ensure continued stability.
We continue to observe stable performance across Khoros Community instances following the deployed fix. Monitoring will remain in place to ensure continued stability.
The incident has been resolved.
We are currently investigating reports of Admin panel innaccessible due to 502 bad gateway errors on Staging environments
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.
Most communities are online, and our Infrastructure team continue to invesitgate the remaining issues.
All communities are now online. Thank you for your patience
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been applied, and the issue should be resolved. We are monitoring the situation.
We have seen no further issues at this time, and we continue to monitor on our end.
We are not observing any further issues at this time. The system remains stable following the applied fix, and we continue to monitor
This incident has been resolved.
We are currently investigating a production outage causing intermittent 504 timeout errors when users attempt to login
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.
We have identified an issue with the database entering failover loop, applied mitigation and are observing the system for errors.
We are observing some errors in the system and are continuing to find and investigate the root cause.
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.
We have observed no further issues through our monitoring. The login issues have been resolved.
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.
We are continuing to investigate this issue.
We have identified the issue and are in the process of developing a fix for the same.
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.
A fix has been implemented and we are monitoring the results.
Backfill processing is currently underway.
Backfilling of data is in progress for the 9th and the jobs continue to run as expected.
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.
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.
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.
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.
Backfill for March 15th for the affected EU data is completed.
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
Backfill for 16th March is under progress. We will share another update once processing and validation have been completed.
Backfill for 15th March has been completed. The backfill for the 16th is now commencing.
Backfill for 16th March has been completed. The backfill for the 17th is now in progress.
Our Infrastructure team are investigating and fixing an issue with the backfill for 17th and 18th. The backfilling efforts will resume shortly.
Our Infrastructure team have resolved the issue, and the backfills for the 17th onwards are proceeding.
Backfill for 17th March has been completed. The backfill for the 18th is now in progress.
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.
The backfill for the 20th and 21st has completed, and the 22nd is in progress.
The backfill for the 22nd has completed, and the remaining days are in progress.
We have improved the speed of backfills, and expect to catch up on the remaining backfills over the next 2 days
We have completed the backfill, and the data for March 28th is expected to be completed in time. We continue to monitor the situation
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.
This incident has been resolved.
We have received reports about people being unable to publish to Facebook. We are investigating the issue.
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.
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.
We are in the process of deploying a fix. No new issues have been reported currently and we are continuing to monitor the same.
Fix deployment in progress. No new issues have been reported.
The fixes have been successfully deployed. Publishing should now be operating normally, and we are continuing to monitor the system.
We are continuing to monitor this. No issues have been reported currently.
We are continuing to monitor this.
We have confirmed that this issue is now resolved.
We are an investigating an issue where Khoros Care chats either cannot be assigned or answered.
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.
We have started received confirmations that the issue is no longer seen. We are continuing to monitor this.
We have confirmed that the issue with Khoros Chats has now been resolved.
We are currently investigating reports by some customers experiencing delays in Community-to-Care ingestion
We are continuing to investigate the delays in Community to Care ingestion. We will provide further updates as soon as they are available.
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.
Our Engineering team are working on a fix for this issue.
We have introduced a fix for this issue and are now working on backfilling data for the affected dates.
We are continuing to monitor the ongoing backfilling for the affected dates.
We continue to monitor backfilling for the affected dates.
Monitoring continues as backfilling for the affected dates progresses.
Backfilling for the affected dates is still in progress and is progressing successfully.
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.
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.
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.
We have identified some data that has not been backfilled, and our Infrastructure team are working on resolving this.
Our Infrastructure team are still working on the missing backfilled data. We will share another update as soon as processing is complete.
The backfilling has now been completed. We will now monitor this for any further issues
This issue has been resolved. We have seen no further issues during our monitoring.
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.
Our Infrastructure team has identified the root cause and is actively working on a fix for the same.
A fix has been implemented and we are monitoring the results.
We have resolved the issue causing delays in ingestion from Communities to Care.
We have reports of analytics dashboards failing intermittently, and we are working to resolve the issue.
Sites have recovered and should now be live. We are looking into a permanent fix to prevent the recurrence of the issue.
Our Engineering team are working on the permanent fix for this issue.
We are continuing to monitor the sites' stability following the recovery.
Our Engineering team have identified the long term fix and we will monitor for stability after the deployment.
Our Engineering team is continuing to work on the permanent fix.
A fix has been made by the Engineering and we are now in the process of deploying it.
Our Infrastructure team are finalizing the deployment, and we expect this to be completed shortly.
Infrastructure team has completed the deployment. The issue with Analytics dashboard is resolved.
We are currently investigating the issue with Khoros Community Analytics not being displayed past 2026-02-27
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
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.
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.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We have identified additional issue since our last fix, and we are working on it.
A fix has been implemented and we are monitoring the results.
The issue has been resolved.
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.
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.
The issue has been resolved.
We are currently investigating an issue where analytics and the bulk api return incomplete data for dates past the 15th of February.
We are continuing to investigate this issue.
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.
We remain actively engaged in monitoring the data backfill recovery effort across all affected dates.
We continue to backfill the dates and expect this to continue during the coming day as we restore all data.
The data backfilling continues to be in progress and we are monitoring the same as well.
The data backfilling continues to be in progress and all jobs are currently running successfully.
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.
Feb 15th - 24nd has been backfilled. The 25th will be backfilled on the normal schedule. We will continue to monitor this closely.
Backfills have been completed and data should now be restored. Please reach out to Customer Support should you still experience any issues.
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.
The issue has been identified and a fix is being implemented.
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.
A fix has been implemented and we are monitoring results.
We have confirmed that the fix that was implemented has resolved this issue.
We are currently investigating this issue.
The issue has been resolved and we are monitoring the results.
We have confirmed that the issue causing delays in sending chat messages and assignment stalls has been resolved.
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.
We are continuing to investigate the issue. Further updates will be shared as more information becomes available.
We are continuing to investigate this issue.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Pingoru polls Khoros's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required