Mavenlink incident

Elevated Errors

Minor Resolved View vendor source →

Mavenlink experienced a minor incident on January 14, 2026 affecting Kantata OX Application and Kantata OX M-Bridge and 1 more component, lasting 2h 44m. The incident has been resolved; the full update timeline is below.

Started
Jan 14, 2026, 03:41 PM UTC
Resolved
Jan 14, 2026, 06:25 PM UTC
Duration
2h 44m
Detected by Pingoru
Jan 14, 2026, 03:41 PM UTC

Affected components

Kantata OX ApplicationKantata OX M-BridgeKantata OX APISmart Upload ManagerKantata Connect

Update timeline

  1. investigating Jan 14, 2026, 03:41 PM UTC

    We’re noticing a higher number of errors than usual in Kantata OX. We’re working to resolve this as quickly as possible. Thanks for your patience! Users experiencing this issue can refresh the page and continue to work as usual.

  2. investigating Jan 14, 2026, 04:17 PM UTC

    We’re continuing to investigate the issue and working to resolve this as quickly as possible. Thank you for your patience! Users experiencing this issue can refresh the page and continue to work as usual.

  3. investigating Jan 14, 2026, 04:24 PM UTC

    We are continuing to investigate this issue.

  4. identified Jan 14, 2026, 04:29 PM UTC

    The issue has been identified and a fix is being implemented. Thank you for your patience while we work to resolve this issue.

  5. monitoring Jan 14, 2026, 04:37 PM UTC

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

  6. investigating Jan 14, 2026, 04:57 PM UTC

    We are continuing to observe elevated error rates. We're continuing to work to resolve this as quickly as possible. Thank you for your patience!

  7. monitoring Jan 14, 2026, 05:53 PM UTC

    We have identified the issue and deployed a fix. Error rates are now decreasing and we will continue to monitor performance and errors until returning to normal operation. Thank you for your patience as we work to fully resolve this.

  8. resolved Jan 14, 2026, 06:25 PM UTC

    This incident has been resolved. Users and integrations that encountered 502 or 504 errors are safe to retry operations. Some M-Bridge and Connect integrations may have automatically disabled due to elevated error rates and may need to be manually re-enabled.