MindTouch incident

CXone Knowledge Management - Service Degradation Status = Resolved

Minor Resolved View vendor source →

MindTouch experienced a minor incident on February 5, 2026 affecting Application (General Service) and Search and 1 more component, lasting 9h 44m. The incident has been resolved; the full update timeline is below.

Started
Feb 05, 2026, 06:26 PM UTC
Resolved
Feb 06, 2026, 04:10 AM UTC
Duration
9h 44m
Detected by Pingoru
Feb 05, 2026, 06:26 PM UTC

Affected components

Application (General Service)SearchGenerative SearchIn-Product Contextual HelpMindTouch Success Center

Update timeline

  1. investigating Feb 05, 2026, 06:26 PM UTC

    CXone Mpower Knowledge Management Service Degradation: Sites are loading slow or unavailable. The CXone Knowledge Management Engineering team is investigating reports of slow load times and occasional site unavailability.

  2. investigating Feb 05, 2026, 06:41 PM UTC

    CXone Knowledge Management Service Degradation: Slow Load Times and Unavailability. The Engineering team is still investigating at this time.

  3. investigating Feb 05, 2026, 06:57 PM UTC

    CXone Knowledge Management Service Degradation: Slow Load Times and Unavailability. The Engineering team is still investigating at this time.

  4. investigating Feb 05, 2026, 07:12 PM UTC

    CXone Knowledge Management Service Degradation: Slow Load Times and Unavailability. The Engineering team is still investigating at this time.

  5. investigating Feb 05, 2026, 07:29 PM UTC

    CXone Knowledge Management Service Degradation: Slow Load Times and Unavailability. The Engineering team is still investigating at this time.

  6. identified Feb 05, 2026, 07:45 PM UTC

    The issue has been identified and a fix is being worked on for deployment.

  7. identified Feb 05, 2026, 08:01 PM UTC

    The issue has been identified and a fix is being worked on for deployment.

  8. identified Feb 05, 2026, 08:17 PM UTC

    The issue has been identified and a fix is being worked on for deployment.

  9. identified Feb 05, 2026, 08:33 PM UTC

    The issue has been identified and a fix is being worked on for deployment.

  10. identified Feb 05, 2026, 08:53 PM UTC

    The issue has been identified and a fix is being worked on for deployment.

  11. identified Feb 05, 2026, 09:08 PM UTC

    We are continuing to work on a fix for this issue.

  12. identified Feb 05, 2026, 09:24 PM UTC

    We are continuing to work on a fix for this issue.

  13. identified Feb 05, 2026, 09:39 PM UTC

    We are continuing to work on a fix for this issue.

  14. monitoring Feb 05, 2026, 10:33 PM UTC

    A fix has been implemented and we are monitoring the results.

  15. monitoring Feb 05, 2026, 10:48 PM UTC

    We are continuing to monitor for any further issues.

  16. monitoring Feb 05, 2026, 11:05 PM UTC

    We are continuing to monitor for any further issues.

  17. monitoring Feb 05, 2026, 11:31 PM UTC

    We are continuing to monitor for any further issues.

  18. monitoring Feb 05, 2026, 11:47 PM UTC

    We are continuing to monitor for any further issues.

  19. monitoring Feb 06, 2026, 12:04 AM UTC

    We are continuing to monitor for any further issues.

  20. monitoring Feb 06, 2026, 12:19 AM UTC

    We are continuing to monitor for any further issues.

  21. monitoring Feb 06, 2026, 12:34 AM UTC

    We are continuing to monitor for any further issues.

  22. monitoring Feb 06, 2026, 12:50 AM UTC

    We are continuing to monitor for any further issues.

  23. monitoring Feb 06, 2026, 01:05 AM UTC

    We are continuing to monitor for any further issues.

  24. monitoring Feb 06, 2026, 01:20 AM UTC

    We are continuing to monitor for any further issues.

  25. monitoring Feb 06, 2026, 01:36 AM UTC

    We are continuing to monitor for any further issues.

  26. monitoring Feb 06, 2026, 01:51 AM UTC

    We are continuing to monitor for any further issues.

  27. monitoring Feb 06, 2026, 02:06 AM UTC

    We are continuing to monitor for any further issues.

  28. monitoring Feb 06, 2026, 02:21 AM UTC

    We are continuing to monitor for any further issues.

  29. monitoring Feb 06, 2026, 02:36 AM UTC

    We are continuing to monitor for any further issues.

  30. monitoring Feb 06, 2026, 02:52 AM UTC

    We are continuing to monitor for any further issues.

  31. monitoring Feb 06, 2026, 03:09 AM UTC

    We are continuing to monitor for any further issues.

  32. monitoring Feb 06, 2026, 03:25 AM UTC

    We are continuing to monitor for any further issues.

  33. monitoring Feb 06, 2026, 03:52 AM UTC

    We are continuing to monitor for any further issues.

  34. resolved Feb 06, 2026, 04:10 AM UTC

    This incident has been resolved.