Khoros Outage History

Khoros Community Classic experienced a major outage where users encountered "403 Forbidden" errors when attempting to access communities, affecting both AWS US and EU hosting regions. The incident lasted approximately 60 hours, during which users were unable to access community platforms. The issue was identified and fixed, followed by a monitoring period before full resolution was confirmed.

Khoros Flow Analytics dashboards experienced a major incident where data from April 8, 2026 onward was not displaying to users. The service team began investigating the issue on April 9, 2026. The incident had a duration of 5 minutes before resolution.

Khoros experienced a major incident where community posts from AMER hosted communities were not being ingested into the Care system starting April 2nd. The issue affected the integration between the Community and Care platforms, preventing proper data flow between these services. The problem was resolved after 36.2 hours through a fix implementation followed by a backfill process to address missed posts during the outage period.

Some Khoros Community instances experienced 500 errors, affecting both AWS EU and US Community Hosting services for 26.1 hours. The engineering team identified the root cause and implemented a fix, followed by extended monitoring to ensure system stability. The incident was fully resolved after confirming stable performance across all affected instances.

Khoros staging environments experienced 502 bad gateway errors that made admin panels inaccessible, affecting AWS US Community Hosting. The infrastructure team identified the root cause and deployed fixes to each environment, with most communities restored within 13 hours and full resolution achieved after 23.5 hours.

The Khoros Flow Service experienced a major outage lasting 55.2 hours, with both the UI and API unavailable across all regions. The issue was identified and a fix was implemented, followed by extended monitoring to ensure system stability. The incident was fully resolved after confirming no further issues occurred.

Khoros experienced a major outage lasting 57 hours where users encountered 504 timeout errors when attempting to login, with some users also reporting unexpected logouts, 500 errors, and loss of access to chats and core workflows. The incident affected all major datacenters (AMER, APAC, and EMEA CARE) and was caused by a database entering a failover loop. The issue was resolved after applying mitigation measures and confirming system stability through monitoring.

Khoros experienced an analytics data population failure affecting EMEA Communities, with no data updates occurring from March 14th onwards due to issues with AWS EU Community Hosting and Community Analytics components. The infrastructure team implemented a fix and performed a systematic backfill process, restoring data day-by-day from March 14th through March 28th over approximately two weeks. The incident was fully resolved after 354.4 hours with all missing historical data restored and normal analytics refresh operations resumed.

Khoros Marketing experienced a major outage where users were unable to publish content to Facebook due to performance degradation from Meta that occurred on March 12-13. The Social Marketing Publishing component was affected for over 4 days (101.4 hours). The engineering team implemented a temporary fix followed by a permanent preventive solution, with the issue fully resolved on March 17.

Khoros Care experienced a major incident where chat conversations could not be assigned to agents or responded to, affecting all AMER, APAC, and EMEA Care datacenters. The issue prevented normal chat functionality across all regions for over 25 hours. The problem was resolved through an implemented fix, with full service restoration confirmed after monitoring.