Khoros incident
Some Khoros Community instances are down with error 500
Khoros experienced a major incident on April 2, 2026 affecting US Hosted Communities and EU Hosted Communities, lasting 1d. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 02, 2026, 12:16 AM UTC
We are currently investigating the issues with some of the Khoros Community instances being down with 500 error.
- identified Apr 02, 2026, 12:53 AM UTC
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.
- monitoring Apr 02, 2026, 02:02 AM UTC
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.
- monitoring Apr 02, 2026, 02:19 PM UTC
We continue to observe stable performance across Khoros Community instances following the deployed fix. Monitoring will remain in place to ensure continued stability.
- monitoring Apr 02, 2026, 09:27 PM UTC
We continue to observe stable performance across Khoros Community instances following the deployed fix. Monitoring will remain in place to ensure continued stability.
- resolved Apr 03, 2026, 02:19 AM UTC
The incident has been resolved.