Jama Software Outage History

Jama Software is up right now

Pingoru has recorded 52 incidents for Jama Software: 15 in the last 12 months and 4 in the last 90 days.

Source: status.jamasoftware.com

52incidents recorded
15last 12 months
4last 90 days
97 minutestypical duration
Incidents per month
024AprMayJunJulAugSepOct2
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking Jama Software in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026411 of 720 (2%)
May 202625 of 744 (1%)
June 202622 of 720 (0%)
July 202600 of 744 (0%)
August 202622 of 744 (0%)
September 202600 of 720 (0%)
October 202623 of 518 (1%)

Incidents, newest first

Minor October 13, 2026 Jama Connect Status 30m Connect

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 →

Major May 24, 2026 Jama Connect Performance Degredation 1h 48m Connect

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 →

Critical March 1, 2025 Jama Connect Currently Unavailable 57m Connect

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 →

Minor December 17, 2024 Jama Connect Performance Degradation 27m Connect

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 →

Major December 16, 2024 Jama Connect currently unavailable 55m Connect

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 →

Minor December 11, 2024 Jama Connect performance degradation 2d 8h Connect

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 →