Khoros incident

[AMER] Community Analytics Data Missing

Major Resolved View vendor source →

Khoros experienced a major incident on May 27, 2026 affecting Analytics, lasting 5d. The incident has been resolved; the full update timeline is below.

Started
May 27, 2026, 04:17 AM UTC
Resolved
Jun 01, 2026, 04:17 AM UTC
Duration
5d
Detected by Pingoru
May 27, 2026, 04:17 AM UTC

Affected components

Analytics

Update timeline

  1. investigating May 27, 2026, 04:17 AM UTC

    We are investigating reports of missing analytics data for AMER-hosted communities. Analytics data has been unavailable since May 21, 2026. Our Infrastructure team is actively looking into the root cause and we will provide updates as more information becomes available.

  2. investigating May 27, 2026, 11:01 AM UTC

    The Infrastructure team is working on backfilling the analytics data for AMER-hosted communities.

  3. identified May 27, 2026, 11:48 PM UTC

    Our team is continuing to investigate the missing Community Analytics data affecting AMER-hosted communities. Work is ongoing to backfill the impacted analytics data, and we will provide another update as soon as more information is available.

  4. identified May 28, 2026, 06:19 AM UTC

    Backfill work for AMER Community analytics data is ongoing. Analytics data for May 26th is now available. Our Infrastructure team continues to work on restoring data for the remaining affected dates. We will provide further updates as progress is made.

  5. identified May 28, 2026, 02:25 PM UTC

    We are continuously working on a fix and actively monitoring the situation.

  6. identified May 28, 2026, 07:18 PM UTC

    Backfill work for AMER Community analytics data is ongoing. Our Infrastructure team continues to work on restoring data for the remaining affected dates. We will provide further updates as progress is made.

  7. identified May 29, 2026, 03:28 AM UTC

    We have completed backfilling data for May 21, 22, and 27. Work is currently ongoing to populate the remaining affected dates. We will continue to provide updates as progress is made.

  8. identified May 29, 2026, 08:59 PM UTC

    Our Infrastructure team continues to work on restoring data for the remaining affected dates. We will provide further updates as progress is made.

  9. monitoring May 30, 2026, 07:52 AM UTC

    All affected dates have been successfully backfilled. Please reach out to us if you are still experiencing any issues or require further assistance.

  10. resolved Jun 01, 2026, 04:17 AM UTC

    This incident has been resolved.