Khoros Outage History

Data for April 30th went missing from EMEA communities in Khoros Communities, affecting Community Analytics and AWS EU Community Hosting services. The infrastructure team identified and deployed a fix, then performed backfill operations to restore the missing data for April 30th, May 3rd, and May 4th. The incident was resolved after approximately 103 hours with all affected data successfully restored.

Khoros experienced degraded performance affecting a subset of communities hosted on AWS US infrastructure for 1.4 hours. The performance issues impacted community functionality during the incident period. The service team investigated and resolved the underlying issue, restoring normal performance to all affected communities.

Some Khoros Community Classic customers experienced problems accessing their community portals, with pages loading incorrectly due to styling issues that made the portals difficult or impossible to use. The issue affected AWS US Community Hosting and lasted approximately 2.3 hours. A fix was implemented and the incident was resolved.

Khoros Care Agent view experienced a major incident lasting 47 hours, affecting agents with delays in sending messages, closed interactions incorrectly returning after closure, and occasional blank interaction panes. The service team implemented a fix and monitored the system for stability before resolving the incident.

Community Analytics data failed to appear for EU hosted communities starting April 16, with US communities also affected later. The incident impacted analytics reporting across multiple regions for over 10 days, with backfill jobs experiencing ongoing failures and delays. The issue was resolved through data backfilling operations that were continuously monitored until completion on April 30.

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.