Khoros incident

Classic hosted communities analytics data missing since 24th of May - EU

Minor Resolved View vendor source →

Khoros experienced a minor incident on May 29, 2026 affecting EU Hosted Communities and Analytics, lasting 8d 5h. The incident has been resolved; the full update timeline is below.

Started
May 29, 2026, 03:07 PM UTC
Resolved
Jun 06, 2026, 08:14 PM UTC
Duration
8d 5h
Detected by Pingoru
May 29, 2026, 03:07 PM UTC

Affected components

EU Hosted CommunitiesAnalytics

Update timeline

  1. identified May 29, 2026, 03:07 PM UTC

    We are aware of an issue with analytics for EU-hosted classic communities. We have triggered the backfill already, and we'll post updates as they are made.

  2. identified May 29, 2026, 11:58 PM UTC

    We are continuing to work on restoring the missing analytics data for EU-hosted classic communities. The backfill process has already been initiated, and we are monitoring its progress closely. We will provide another update as soon as more information becomes available.

  3. identified May 30, 2026, 08:39 AM UTC

    Data has been backfilled up to the 27th. We continue to backfill the remaining two days.

  4. identified May 30, 2026, 08:39 AM UTC

    We continue to backfill data for May 28th and 29th.

  5. identified Jun 01, 2026, 03:32 AM UTC

    The backfilling process is progressing as expected.

  6. identified Jun 01, 2026, 05:10 PM UTC

    The backfilling process is progressing as expected.

  7. identified Jun 02, 2026, 03:52 AM UTC

    We are continuing to monitor the backfilling status. No issues have been encountered.

  8. identified Jun 02, 2026, 11:54 PM UTC

    Our team is currently working on the required remediation. We will share the next update as soon as additional progress is made.

  9. identified Jun 03, 2026, 09:01 PM UTC

    The team continues working on the remediation.

  10. identified Jun 04, 2026, 03:51 AM UTC

    The remediation effort remains underway. We will share the next update as soon as there is more to report.

  11. identified Jun 04, 2026, 06:46 PM UTC

    The team continues working on the remediation.

  12. identified Jun 05, 2026, 03:31 AM UTC

    The remediation effort is ongoing by our teams.

  13. monitoring Jun 05, 2026, 11:34 AM UTC

    The issue affecting analytics collection has been resolved, and analytics data is now being collected and processed correctly. We have completed our investigation and remediation activities and will continue to monitor the platform to ensure ongoing stability.

  14. monitoring Jun 05, 2026, 08:01 PM UTC

    We are continuing to monitor for any further issues.

  15. resolved Jun 06, 2026, 08:14 PM UTC

    The incident has been resolved.