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.
We have observed no further issues through our monitoring. The login issues have been resolved.
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 are observing some errors in the system and are continuing to find and investigate the root cause.
We have identified an issue with the database entering failover loop, applied mitigation and are observing the system for errors.
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 are currently investigating a production outage causing intermittent 504 timeout errors when users attempt to login
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6020 services available
Integrations with