Jama Software incident

Jama Connect Status

Major Resolved View vendor source →

Jama Software experienced a major incident on April 16, 2026 affecting Connect, lasting 6h 13m. The incident has been resolved; the full update timeline is below.

Started
Apr 16, 2026, 10:43 AM UTC
Resolved
Apr 16, 2026, 04:57 PM UTC
Duration
6h 13m
Detected by Pingoru
Apr 16, 2026, 10:43 AM UTC

Affected components

Connect

Update timeline

  1. investigating Apr 16, 2026, 10:43 AM UTC

    We are investigating reports of customers unable to access Jama Connect. Our engineering team has been notified of the issues and is working towards a solution. As we continue to monitor and resolve the issue, we will keep this site up-to-date with the latest information. We apologize for this interruption.

  2. investigating Apr 16, 2026, 11:45 AM UTC

    We are continuing to investigate this issue.

  3. investigating Apr 16, 2026, 12:14 PM UTC

    We are continuing to investigate this issue.

  4. investigating Apr 16, 2026, 12:33 PM UTC

    We are continuing to investigate this issue.

  5. investigating Apr 16, 2026, 01:12 PM UTC

    We are continuing to investigate this issue.

  6. investigating Apr 16, 2026, 02:04 PM UTC

    We are continuing to investigate this issue.

  7. investigating Apr 16, 2026, 02:19 PM UTC

    We are continuing to investigate this issue.

  8. identified Apr 16, 2026, 02:21 PM UTC

    The issue has been identified and a fix is being implemented.

  9. identified Apr 16, 2026, 02:23 PM UTC

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

  10. identified Apr 16, 2026, 02:23 PM UTC

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

  11. identified Apr 16, 2026, 02:59 PM UTC

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

  12. identified Apr 16, 2026, 03:41 PM UTC

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

  13. identified Apr 16, 2026, 04:08 PM UTC

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

  14. monitoring Apr 16, 2026, 04:33 PM UTC

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

  15. monitoring Apr 16, 2026, 04:34 PM UTC

    We are continuing to monitor for any further issues.

  16. resolved Apr 16, 2026, 04:57 PM UTC

    This incident has been resolved.