Release Tracker Outage History

Release Tracker is up right now

Release Tracker had 5 outages in the last 2 years totaling 22h 38m of downtime, averaging 0.2 incidents per month.

There were 5 Release Tracker outages since July 23, 2025 totaling 22h 38m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: releasetracker.statuspage.io

Minor May 11, 2026

Issue Affecting "View as tree" button

Detected by Pingoru
May 11, 2026, 02:04 AM UTC
Resolved
May 11, 2026, 04:52 PM UTC
Duration
14h 47m
Affected: Release Tracker
Timeline · 4 updates
  1. investigating May 11, 2026, 02:04 AM UTC

    Clicking the "View as tree" button currently makes all work items clear from the view. We are currently investigating this issue. Current mitigation: Only view work items as a list. If you click "View as tree", clicking "View as list" will return the view to normal.

  2. identified May 11, 2026, 02:04 AM UTC

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

  3. monitoring May 11, 2026, 04:37 PM UTC

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

  4. resolved May 11, 2026, 04:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 17, 2025

Issue Affecting New Installations

Detected by Pingoru
Dec 17, 2025, 03:08 PM UTC
Resolved
Dec 17, 2025, 04:21 PM UTC
Duration
1h 12m
Affected: Release Tracker
Timeline · 3 updates
  1. identified Dec 17, 2025, 03:08 PM UTC

    We are currently investigating an issue that is preventing new installations from completing successfully. This issue does not affect existing customers or current installations. All existing environments remain fully operational. We have identified the cause of the issue affecting new installations and are working on a fix. Existing customers remain unaffected.

  2. monitoring Dec 17, 2025, 04:02 PM UTC

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

  3. resolved Dec 17, 2025, 04:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 13, 2025

Release Tracker Team configuration not working

Detected by Pingoru
Nov 13, 2025, 09:20 PM UTC
Resolved
Nov 14, 2025, 12:17 AM UTC
Duration
2h 56m
Affected: Release Tracker
Timeline · 4 updates
  1. investigating Nov 13, 2025, 09:20 PM UTC

    We are currently investigating this issue.

  2. identified Nov 13, 2025, 09:26 PM UTC

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

  3. monitoring Nov 13, 2025, 11:24 PM UTC

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

  4. resolved Nov 14, 2025, 12:17 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 11, 2025

Add Existing Test Plan Functionality Broken

Detected by Pingoru
Nov 11, 2025, 01:34 PM UTC
Resolved
Nov 11, 2025, 04:11 PM UTC
Duration
2h 37m
Affected: Release Tracker
Timeline · 6 updates
  1. investigating Nov 11, 2025, 01:34 PM UTC

    We are currently investigating this issue.

  2. identified Nov 11, 2025, 01:45 PM UTC

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

  3. identified Nov 11, 2025, 02:37 PM UTC

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

  4. identified Nov 11, 2025, 02:56 PM UTC

    We are deploying a fix to our customers.

  5. monitoring Nov 11, 2025, 03:37 PM UTC

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

  6. resolved Nov 11, 2025, 04:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 23, 2025

Release Planner bug discovered

Detected by Pingoru
Jul 23, 2025, 02:35 PM UTC
Resolved
Jul 23, 2025, 03:39 PM UTC
Duration
1h 4m
Affected: Release Tracker
Timeline · 4 updates
  1. investigating Jul 23, 2025, 02:35 PM UTC

    We have identified an issue with Release Planner which will make it not function properly. Our team is looking to release a fix today. In the meantime, please manage your Release planning using other means.

  2. identified Jul 23, 2025, 02:39 PM UTC

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

  3. monitoring Jul 23, 2025, 03:38 PM UTC

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

  4. resolved Jul 23, 2025, 03:39 PM UTC

    This incident has been resolved.

Read the full incident report →