Jama Software Outage History

Started Oct 13, 2026, 05:20 AM UTC· resolved Oct 13, 2026, 05:51 AM UTC

1. investigating Oct 13, 2026, 05:20 AM UTC

   Some customers have reported degradation to the performance of their Jama Connect instance. Our team has been notified and is investigating the issue. As we continue to monitor performance, we will update this site with the latest information. We apologize for this interruption.

2. identified Oct 13, 2026, 05:36 AM UTC

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

3. monitoring Oct 13, 2026, 05:43 AM UTC

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

4. resolved Oct 13, 2026, 05:51 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 11, 2026, 03:26 PM UTC· resolved Oct 11, 2026, 05:37 PM UTC

1. investigating Oct 11, 2026, 03:26 PM UTC

   Some customers have reported degradation to the performance of their Jama Connect instance. Our team has been notified and is investigating the issue. As we continue to monitor performance, we will update this site with the latest information. We apologize for this interruption.

2. identified Oct 11, 2026, 03:48 PM UTC

   We have identified the source of the issue and are working to resolve it.

3. identified Oct 11, 2026, 04:15 PM UTC

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

4. monitoring Oct 11, 2026, 05:27 PM UTC

   We have implemented a fix for the issues and are monitoring the results.

5. resolved Oct 11, 2026, 05:37 PM UTC

   The Jama Software engineering team has identified and resolved the outage issue. We will continue to monitor the situation but expect no further disruptions.

Read the full incident report →

Started Aug 06, 2026, 05:11 PM UTC· resolved Aug 06, 2026, 05:54 PM UTC

1. investigating Aug 06, 2026, 05:11 PM 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. monitoring Aug 06, 2026, 05:40 PM UTC

   We have implemented a fix for the issues and are monitoring the results.

3. resolved Aug 06, 2026, 05:54 PM UTC

   The Jama Software engineering team has identified and resolved the partial outage issue. We will continue to monitor the situation but expect no further disruptions.

Read the full incident report →

Started Aug 04, 2026, 04:29 PM UTC· resolved Aug 04, 2026, 05:57 PM UTC

1. investigating Aug 04, 2026, 04:29 PM 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. identified Aug 04, 2026, 04:58 PM UTC

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

3. monitoring Aug 04, 2026, 05:12 PM UTC

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

4. resolved Aug 04, 2026, 05:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 30, 2026, 04:57 PM UTC· resolved Jun 30, 2026, 05:12 PM UTC

1. investigating Jun 30, 2026, 04:57 PM UTC

   Some customers have reported degradation to the performance of their Jama Connect instance. Our team has been notified and is investigating the issue. As we continue to monitor performance, we will update this site with the latest information. We apologize for this interruption.

2. resolved Jun 30, 2026, 05:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 19, 2026, 09:43 PM UTC· resolved Jun 19, 2026, 11:00 PM UTC

1. investigating Jun 19, 2026, 09:43 PM UTC

   Some customers have reported degradation to the performance of their Jama Connect instance. Our team has been notified and is investigating the issue. As we continue to monitor performance, we will update this site with the latest information. We apologize for this interruption.

2. investigating Jun 19, 2026, 10:28 PM UTC

   The Jama Software engineering team is continuing to investigate the root cause of the ongoing performance degradation issue.

3. monitoring Jun 19, 2026, 10:33 PM UTC

   We have implemented a fix for the issues and are monitoring the results.

4. resolved Jun 19, 2026, 11:00 PM UTC

   The Jama Software engineering team has identified and resolved the performance degradation issue. We will continue to monitor the situation but expect no further disruptions.

Read the full incident report →

Started May 24, 2026, 01:15 AM UTC· resolved May 24, 2026, 03:03 AM UTC

1. investigating May 24, 2026, 01:15 AM UTC

   We are currently investigating this issue.

2. investigating May 24, 2026, 01:39 AM UTC

   We are continuing to investigate this issue.

3. investigating May 24, 2026, 01:47 AM UTC

   We are continuing to investigate this issue.

4. monitoring May 24, 2026, 02:54 AM UTC

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

5. resolved May 24, 2026, 03:03 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 20, 2026, 12:58 PM UTC· resolved May 20, 2026, 04:07 PM UTC

1. investigating May 20, 2026, 12:58 PM UTC

   We are currently investigating the issue.

2. monitoring May 20, 2026, 01:29 PM UTC

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

3. monitoring May 20, 2026, 01:41 PM UTC

   We are continuing to monitor for any further issues.

4. resolved May 20, 2026, 04:07 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 30, 2026, 11:52 AM UTC· resolved Apr 30, 2026, 01:33 PM UTC

1. investigating Apr 30, 2026, 11:52 AM UTC

   Some customers have reported degradation to the performance of their Jama Connect instance. Our team has been notified and is investigating the issue. As we continue to monitor performance, we will update this site with the latest information. We apologize for this interruption.

2. investigating Apr 30, 2026, 12:24 PM UTC

   The Jama Software engineering team is continuing to investigate the root cause of the ongoing performance degradation issue.

3. monitoring Apr 30, 2026, 12:49 PM UTC

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

4. monitoring Apr 30, 2026, 12:49 PM UTC

   We have implemented a fix for the issues and are monitoring the results.

5. monitoring Apr 30, 2026, 12:50 PM UTC

   We have implemented a fix for the issues and are monitoring the results.

6. resolved Apr 30, 2026, 01:33 PM UTC

   The Jama Software engineering team has identified and resolved the performance degradation issue. We will continue to monitor the situation but expect no further disruptions.

Read the full incident report →

Started Apr 16, 2026, 10:43 AM UTC· resolved Apr 16, 2026, 04:57 PM UTC

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.

Read the full incident report →

Started Apr 08, 2026, 06:10 PM UTC· resolved Apr 08, 2026, 09:00 PM UTC

1. investigating Apr 08, 2026, 06:10 PM UTC

   Some customers have reported degradation to the performance of their Jama Connect instance. Our team has been notified and is investigating the issue. As we continue to monitor performance, we will update this site with the latest information. We apologize for this interruption.

2. monitoring Apr 08, 2026, 06:15 PM UTC

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

3. resolved Apr 08, 2026, 09:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 08, 2026, 06:49 AM UTC· resolved Apr 08, 2026, 07:24 AM UTC

1. investigating Apr 08, 2026, 06:49 AM UTC

   Some customers have reported degradation to the performance of their Jama Connect instance. Our team has been notified and is investigating the issue. As we continue to monitor performance, we will update this site with the latest information. We apologize for this interruption.

2. identified Apr 08, 2026, 07:08 AM UTC

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

3. monitoring Apr 08, 2026, 07:13 AM UTC

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

4. resolved Apr 08, 2026, 07:24 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 25, 2026, 08:14 PM UTC· resolved Feb 25, 2026, 08:47 PM UTC

1. investigating Feb 25, 2026, 08:14 PM 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. identified Feb 25, 2026, 08:30 PM UTC

   We have identified the source of the issue and are working to resolve it.

3. monitoring Feb 25, 2026, 08:33 PM UTC

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

4. resolved Feb 25, 2026, 08:47 PM UTC

   The Jama Software engineering team has identified and resolved the issue. We will continue to monitor the situation but expect no further disruptions.

Read the full incident report →

Started Nov 12, 2025, 06:36 PM UTC· resolved Nov 12, 2025, 06:49 PM UTC

1. investigating Nov 12, 2025, 06:36 PM 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. identified Nov 12, 2025, 06:38 PM UTC

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

3. resolved Nov 12, 2025, 06:49 PM UTC

   A fix has been implemented and we are monitoring the results. Monitoring will continue for any further issues.

Read the full incident report →

Started Oct 23, 2025, 07:24 PM UTC· resolved Oct 23, 2025, 08:06 PM UTC

1. investigating Oct 23, 2025, 07:24 PM 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. identified Oct 23, 2025, 07:45 PM UTC

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

3. monitoring Oct 23, 2025, 07:58 PM UTC

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

4. monitoring Oct 23, 2025, 07:59 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Oct 23, 2025, 08:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 25, 2025, 07:42 AM UTC· resolved Aug 25, 2025, 08:52 AM UTC

1. investigating Aug 25, 2025, 07:42 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 Aug 25, 2025, 08:11 AM UTC

   The Jama Software engineering team is continuing to investigate the root cause of the ongoing outage issue.

3. identified Aug 25, 2025, 08:31 AM UTC

   We have identified the source of the issue and are working to resolve it.

4. identified Aug 25, 2025, 08:32 AM UTC

   We have identified the source of the issue and are working to resolve it.

5. monitoring Aug 25, 2025, 08:42 AM UTC

   We have implemented a fix for the issues and are monitoring the results.

6. resolved Aug 25, 2025, 08:52 AM UTC

   The Jama Software engineering team has identified and resolved the issue. We will continue to monitor the situation but expect no further disruptions.

Read the full incident report →

Started Jun 20, 2025, 06:55 AM UTC· resolved Jun 20, 2025, 09:32 AM UTC

1. investigating Jun 20, 2025, 06:55 AM UTC

   Some customers have reported degradation to the performance of their Jama Connect instance. Our team has been notified and is investigating the issue. As we continue to monitor performance, we will update this site with the latest information. We apologize for this interruption.

2. investigating Jun 20, 2025, 07:20 AM UTC

   We are continuing to investigate this issue.

3. identified Jun 20, 2025, 08:02 AM UTC

   We have identified the source of the issue and are working to resolve it.

4. identified Jun 20, 2025, 08:34 AM UTC

   We have identified the source of the issue and are working to resolve it.

5. monitoring Jun 20, 2025, 09:14 AM UTC

   We have implemented a fix for the issues and are monitoring the results.

6. resolved Jun 20, 2025, 09:32 AM UTC

   The Jama Software engineering team has identified and resolved the degradation performance issue. We will continue to monitor the situation but expect no further disruptions.

Read the full incident report →

Started Apr 02, 2025, 07:50 PM UTC· resolved Apr 02, 2025, 10:23 PM UTC

1. investigating Apr 02, 2025, 07:50 PM UTC

   Some customers have reported degradation to the performance of their Jama Connect instance. Our team has been notified and is investigating the issue. As we continue to monitor performance, we will update this site with the latest information. We apologize for this interruption.

2. investigating Apr 02, 2025, 08:17 PM UTC

   The Jama Software engineering team is continuing to investigate the root cause of the ongoing performance degradation issue.

3. investigating Apr 02, 2025, 08:43 PM UTC

   The Jama Software engineering team is continuing to investigate the root cause of the ongoing performance degradation issue.

4. investigating Apr 02, 2025, 09:16 PM UTC

   The Jama Software engineering team is continuing to investigate the root cause of the ongoing performance degradation issue.

5. investigating Apr 02, 2025, 09:46 PM UTC

   The Jama Software engineering team is continuing to investigate the root cause of the ongoing performance degradation issue.

6. monitoring Apr 02, 2025, 10:06 PM UTC

   We have implemented a fix for the issues and are monitoring the results.

7. resolved Apr 02, 2025, 10:23 PM UTC

   The Jama Software engineering team has identified and resolved the performance degradation issue. We will continue to monitor the situation but expect no further disruptions.

Read the full incident report →

Started Mar 31, 2025, 12:37 PM UTC· resolved Mar 31, 2025, 06:03 PM UTC

1. investigating Mar 31, 2025, 12:37 PM UTC

   Some customers have reported degradation to the performance of their Jama Connect instance. Our team has been notified and is investigating the issue. As we continue to monitor performance, we will update this site with the latest information. We apologize for this interruption.

2. investigating Mar 31, 2025, 01:02 PM UTC

   We are continue to investigate this issue.

3. investigating Mar 31, 2025, 01:38 PM UTC

   We are continuing to investigate this issue.

4. investigating Mar 31, 2025, 02:10 PM UTC

   We are continuing to investigate this issue.

5. investigating Mar 31, 2025, 03:01 PM UTC

   We are continuing to investigate this issue.

6. investigating Mar 31, 2025, 03:37 PM UTC

   We are continuing to investigate this issue.

7. investigating Mar 31, 2025, 04:08 PM UTC

   We are continuing to investigate this issue.

8. investigating Mar 31, 2025, 04:50 PM UTC

   We are still working together to find a solution for this

9. monitoring Mar 31, 2025, 05:39 PM UTC

   We have implemented a fix for the issues and are monitoring the results.

10. resolved Mar 31, 2025, 06:03 PM UTC

    The Jama Software engineering team has identified and resolved the degradation issue. We will continue to monitor the situation but expect no further disruptions.

Read the full incident report →

Started Mar 17, 2025, 01:47 PM UTC· resolved Mar 17, 2025, 02:14 PM UTC

1. investigating Mar 17, 2025, 01:47 PM 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 Mar 17, 2025, 02:06 PM UTC

   We are continuing to investigate this issue. Thank you for your patience.

3. resolved Mar 17, 2025, 02:14 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 01, 2025, 12:26 AM UTC· resolved Mar 01, 2025, 01:23 AM UTC

1. investigating Mar 01, 2025, 12:26 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 Mar 01, 2025, 12:29 AM UTC

   We are continuing to investigate this issue.

3. investigating Mar 01, 2025, 12:56 AM UTC

   The Jama Software engineering team is continuing to investigate the root cause of the ongoing outage issue.

4. identified Mar 01, 2025, 01:07 AM UTC

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

5. monitoring Mar 01, 2025, 01:16 AM UTC

   We have implemented a fix for the issues and are monitoring the results.

6. monitoring Mar 01, 2025, 01:16 AM UTC

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

7. monitoring Mar 01, 2025, 01:16 AM UTC

   We are continuing to monitor for any further issues.

8. resolved Mar 01, 2025, 01:23 AM UTC

   The Jama Software engineering team has identified and resolved the outage issue. We will continue to monitor the situation but expect no further disruptions.

Read the full incident report →

Started Dec 17, 2024, 02:03 PM UTC· resolved Dec 17, 2024, 02:30 PM UTC

1. investigating Dec 17, 2024, 02:03 PM UTC

   Some customers have reported degradation to the performance of their Jama Connect instance. Our team has been notified and is investigating the issue. As we continue to monitor performance, we will update this site with the latest information. We apologize for this interruption.

2. resolved Dec 17, 2024, 02:30 PM UTC

   The Jama Software engineering team has identified and resolved the performance degradation issue. We will continue to monitor the situation but expect no further disruptions.

Read the full incident report →

Started Dec 16, 2024, 11:14 PM UTC· resolved Dec 17, 2024, 12:10 AM UTC

1. investigating Dec 16, 2024, 11:14 PM 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 Dec 16, 2024, 11:42 PM UTC

   The Jama Software engineering team is continuing to investigate the root cause of the ongoing outage issue.

3. identified Dec 17, 2024, 12:05 AM UTC

   We have identified the source of the issue and are working to resolve it.

4. identified Dec 17, 2024, 12:05 AM UTC

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

5. resolved Dec 17, 2024, 12:10 AM UTC

   The Jama Software engineering team has identified and resolved the outage issue. We will continue to monitor the situation but expect no further disruptions.

Read the full incident report →

Started Dec 11, 2024, 12:00 AM UTC· resolved Dec 13, 2024, 08:11 AM UTC

1. investigating Dec 11, 2024, 12:00 AM UTC

   Some customers have reported degraded performance of their Jama Connect instance when using TraceView. Our team has been notified and is investigating the issue. We are continuing to investigate and will update this site with the latest information.

2. investigating Dec 11, 2024, 12:46 AM UTC

   We are continuing to investigate this issue.

3. investigating Dec 11, 2024, 05:40 PM UTC

   We are continuing to investigate this issue.

4. investigating Dec 12, 2024, 08:07 PM UTC

   We are continuing to investigate this issue.

5. monitoring Dec 13, 2024, 08:07 AM UTC

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

6. resolved Dec 13, 2024, 08:11 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 15, 2024, 06:49 AM UTC· resolved Nov 15, 2024, 07:11 AM UTC

1. investigating Nov 15, 2024, 06:49 AM UTC

   Some customers have reported degradation to the performance of their Jama Connect instance. Our team has been notified and is investigating the issue. As we continue to monitor performance, we will update this site with the latest information. We apologize for this interruption.

2. monitoring Nov 15, 2024, 07:00 AM UTC

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

3. resolved Nov 15, 2024, 07:11 AM UTC

   This incident has been resolved.

Read the full incident report →