Jive Software incident

Fogbugz sites are failing to load due to JSON API errors

Minor Resolved View vendor source →

Jive Software experienced a minor incident on September 23, 2025 affecting API and Website, lasting 7d 19h. The incident has been resolved; the full update timeline is below.

Started
Sep 23, 2025, 03:35 AM UTC
Resolved
Sep 30, 2025, 11:06 PM UTC
Duration
7d 19h
Detected by Pingoru
Sep 23, 2025, 03:35 AM UTC

Affected components

APIWebsite

Update timeline

  1. investigating Sep 17, 2025, 09:47 AM UTC

    We’re investigating elevated 500 responses from the JSON API endpoint /api/0, which is causing site load failures.

  2. monitoring Sep 17, 2025, 10:51 AM UTC

    The fix has been applied, and we’re monitoring system performance.

  3. monitoring Sep 18, 2025, 03:43 AM UTC

    We are continuing to monitor system performance closely. No new reports of issues have been observed since our last update. At this time, FogBugz remains fully operational. We will provide further updates if any new developments occur.

  4. investigating Sep 18, 2025, 03:03 PM UTC

    Some customers are now reporting intermittent API errors, our team is actively investigating the new errors.

  5. investigating Sep 20, 2025, 02:08 AM UTC

    There are no new issues reported currently. Our team is continuing to look into the previously reported intermittent errors.

  6. investigating Sep 21, 2025, 09:18 AM UTC

    No additional disruptions have been observed. The team continues to focus on stabilizing the earlier reported intermittent issues.

  7. identified Sep 22, 2025, 03:45 AM UTC

    The issue has been identified and the team is looking into the steps for fixing the same.

  8. identified Sep 23, 2025, 03:35 AM UTC

    Work is actively in progress for the fixes and verifying the effectiveness of the same.

  9. monitoring Sep 23, 2025, 05:40 AM UTC

    A fix has been implemented and we are currently monitoring the same.

  10. investigating Sep 23, 2025, 04:18 PM UTC

    We are continuing to investigate as monitoring indicates the issue persists.

  11. identified Sep 23, 2025, 11:45 PM UTC

    We’ve introduced improvements to enhance platform stability. Over the coming days, our team will be closely tracking performance and will take further action to investigate and optimize should any issues arise.

  12. monitoring Sep 25, 2025, 05:33 AM UTC

    We have applied further fixes and will monitor the performance of the same.

  13. identified Sep 26, 2025, 04:29 AM UTC

    Some customers have reported the errors to be back and we have found the related part of the stack that could be causing this. The team is actively looking into the same.

  14. monitoring Sep 26, 2025, 09:38 PM UTC

    Presently, the issue is not reproducible. We are actively monitoring this.

  15. monitoring Sep 29, 2025, 05:14 AM UTC

    Our team is monitoring for any recurrence. The problem is not reproducible as of now.

  16. resolved Sep 30, 2025, 11:06 PM UTC

    We’ve actively monitored the impact of the improvements to the system over the past days. No further instances of the issue have been observed and we are considering this issue to be resolved.