Khoros had 61 outages in the last 2 years totaling 2111h 40m of downtime — averaging 2.5 incidents per month.
There were 61 Khoros outages since September 26, 2025 totaling 2111h 40m of downtime. Each is summarised below — incident details, duration, and resolution information.
Meta is currently experiencing high disruptions impacting Messenger API for Instagram, Facebook and Whatsapp, which in turn is impacting Khoros message ingestion activities.
We are currently investigating a partner platform issue affecting Khoros Care integrations with Meta services. Customers may experience delays, errors, or intermittent failures when using connected Meta channels, including message ingestion, publishing, or synchronization. Our teams are monitoring the situation closely and will provide updates as more information becomes available.
Meta is currently experiencing high disruptions impacting Messenger API for Instagram, Facebook and Whatsapp, which in turn is impacting Khoros message ingestion activities.
The disruptions from Meta have now been resolved. We are actively monitoring on our end. Please reach out via a Support ticket if any Meta integrations are not working as expected.
The issue related to the Meta platform disruption has been resolved, and services are now operating normally. Please note that the disruption may have caused some Meta channel connections to become disconnected. If you encounter connection errors, please re-register and re-verify the affected number/account with Meta. If the issue persists after re-registration and verification, please contact Support for further assistance.
We are currently investigating an issue affecting user login for some customers. Impacted users may experience MFA failures, including invalid token errors or issues receiving SMS authentication codes. We have identified that the issue appears to be related to the authentication flow. We are further investigating and will provide further updates as soon as more information is available.
We are continuously working on a fix and actively monitoring the situation.
Our infrastructure team has applied a fix for the MFA issue and we are monitoring the results.
We are continuing to monitor for any further issues.
The issue affecting some user login flows has been resolved. We have completed monitoring and are not seeing further impact at this time. Thank you for your patience.
This incident has been resolved.
We are aware of an issue causing replies to Google My Business (GMB) reviews to fail. We are actively investigating this and will provide updates as they become available.
We have identified the issue causing Google My Business (GMB) reviews to fail, and our Engineering team are currently working on a fix.
A fix has been deployed to address the issue causing Google My Business review replies to fail in Khoros Care. We are actively monitoring the environment to ensure replies are processing as expected. If you continue to experience issues, please reach out to Khoros Support.
After continued monitoring, we found that the issue affecting Google My Business replies in Khoros Care is still ongoing, due to data consumed during the incident. We have identified the issue affecting some Google My Business replies and are actively working to restore reply publishing for impacted cases. We will share another update as soon as more information is available.
Our Engineering team is actively working on restoring reply publishing for impacted reviews. We will continue to provide updates as progress is made and share additional information as soon as it becomes available.
Work on restoring reply publishing for impacted reviews is ongoing. We will continue to provide updates as progress is made and share additional information as soon as it becomes available.
A fix has been implemented and we are monitoring the results.
We are closing this incident as the fix has been implemented and the environment has been monitored successfully. The issue affecting Google My Business review replies in Khoros Care has been addressed, and reply publishing for impacted reviews has been restored. Our Engineering team completed the required remediation work and monitored the results to confirm that replies are processing as expected. If you continue to experience any issues with Google My Business replies, please contact Khoros Support for further assistance.
We are investigating reports that some customers using Khoros Care are seeing Facebook Messenger / Facebook DM author names display as long numeric IDs instead of customer names. Agents can generally continue to read and respond to affected conversations, but identifying customers by name in Care may be impacted. We are actively investigating and will provide another update as soon as we have more information.
We have identified the issue causing some customers to see Facebook Messenger / Facebook DM author names display as long numeric IDs instead of customer names. We are working on a fix for this issue and will update as soon as this is deployed.
We have deployed a fix that addresses the root cause of this issue. Facebook Messenger and Facebook DM sender names are now displaying correctly for new incoming messages. For messages received during the incident window, our team is actively working to determine the best path to restore the correct sender names. We are committed to keeping you informed as this progresses and will share an update shortly. Agents can continue to read and respond to all conversations in the meantime
We have deployed a fix that addresses the root cause of this issue. Facebook Messenger and Facebook DM sender names are now displaying correctly for new incoming messages. For messages received during the incident window, our team has completed restoration efforts and sender names should now appear correctly. We will continue monitoring the system to ensure stability. Agents can continue to read and respond to all conversations as normal. Thank you for your patience while we worked through this issue.
We will continue monitoring the system to ensure stability.
The fix has been implemented, and the system has been monitored for stability. The issue causing Facebook Messenger and Facebook DM author names to display as numeric IDs in Khoros Care has been addressed. New incoming messages are now displaying sender names correctly, and restoration efforts for messages received during the incident window have been completed. If you continue to see Facebook author names displayed incorrectly, please contact Khoros Support for further assistance.
We have found that there were issues with Community Analytics data not coming up from May 12 for APAC-hosted communities. The team is investigating.
The issue has been identified, and the backfill has been triggered accordingly. Backfill is in progress, and we will keep you posted on its status.
The backfill has been completed. We continue to investigate the root cause.
The issue affecting Community Analytics data for APAC-hosted communities from May 12 onward has been resolved. The backfill has completed successfully, and data is now available as expected.
We are currently investigating ingestion issues with some Care instances. The radius is unclear, so the customers are advised to create support tickets in case they notice degradation.
Our infrastructure team has applied a fix for the issue affecting ingestion. Services are recovering, and we are currently monitoring the environment to ensure stability. Customers should continue to report any ongoing degradation through support tickets.
We have observed some continued delays in post ingestion after our original fix, and we are investigating the cause.
We have identified the issue and implemented a secondary fix that has restored post ingestion. We are now working on a permanent fix for this.
The incident has been resolved.
We have been made aware that data may not be present in certain EMEA communities for April 30th. We are working on restoring this data and will provide further updates as they become available.
We are continuing to investigate this issue.
An issue was identified and a fix is being implemented by our Infrastructure team that will allow backfill operations to be performed for the April 30th data.
The issue has been resolved and a fix has been successfully deployed by the Infrastructure team. We are currently monitoring the system to ensure stability. Backfill operations for April 30th data are in progress and proceeding as expected.
The issue has been resolved and a fix has been successfully deployed by our Infrastructure team. We are currently monitoring the system to ensure stability. Backfill operations are underway and progressing as expected: April 30th data backfill has been completed. May 3rd and May 4th data backfills are currently in progress.
We are continuing to monitor for any further issues.
The May 3rd data has been backfilled and should be available in Analytics.
The incident has been resolved
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 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 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.