Update - The temporary fix means that our data is within 5 hours current at the moment for reporting. We have identified a fix for the data synchronization issue we saw on some projects, it has been rolled out and we are monitoring to ensure that further issues are not seen.

Historical (between 30Nov & 7Dec) data and current total counts remain impacted by the historical data dips that we continue to work on backfilling.

Only Historical data from after November 30 is being affected.
We will continue to leave this incident in investigating status until we are able to confirm a full and permanent fix.
Dec 8, 19:37 UTC

Update - With our temporary fix in place our reporting system freshness continue to improve, and our teams are making progress towards a full fix.

We have identified are working on filling in missing data gaps, while we continue to work on streamlining the data flow in a steady pace.

We are currently investigating a data synchronization issue with the current fix, that manifests in some projects having an inconsistent number of issues (that is changing through the day).

Only Historical data from after November 30 is being affected.
We will continue to leave this incident in investigating status until we are able to confirm a full and permanent fix.
Dec 7, 19:03 UTC

Update - Our mitigation for the current database replication problems are proving successful. At this time, the freshness of our reporting system is greatly improved, but we can not yet guarantee this to be within the usual 3 hour window. We aim to have an update for that tomorrow (Tuesday). Historical data from 30th November until 7th December will contain gaps which we are in the process of filling.

This mitigation enables the reporting data being returned to be correct and up to date as soon as possible. As well as this, we have teams focussed on a full fix. We will leave this incident in investigating status until we are able to confirm a full and permanent fix.
Dec 6, 19:43 UTC

Update - Our reporting services is unfortunately still running behind in updating data, During this time, the graphs and totals showing the latest number of issues are inaccurate, and not all issues for the past two days will be visible in the issues tab or in the reporting API.

We appreciate this has significant impact to our customers using reporting and are very focused on resolving is asap. We made some further changes to our systems late yesterday (Sunday) and initial indications are that the system is catching up (although this will take some hours). We will update later today (Monday UTC).

Once the system has caught up then we will will need to repair any gaps in the data to avoid ‘dips’ in the historic information and we are preparing to do that.
Dec 6, 08:04 UTC

Update - Our reporting service is still running behind on updating data. During this time, the graphs and totals showing the latest number of issues are inaccurate, and not all issues for the past two days will be visible in the issues tab or in the reporting API. We are actively working on resolving this incident and will continue to provide further updates here.
Dec 5, 13:20 UTC

Update - Our reporting service is still running behind on updating data. During this time, the graphs and totals showing the latest number of issues are inaccurate, and not all issues for the past two days will be visible in the issues tab or in the reporting API. We are actively working on resolving this incident and will provide further updates here.
Dec 4, 12:33 UTC

Update - We believe we have identified the cause of this issue and are working to resolve it.
Dec 2, 11:15 UTC

Investigating - Our reporting service is currently experiencing slowness in data freshness and may update data later than 3 hours after test or import. Our team is looking into it and will update the status as we investigate and resolve it.
Nov 30, 12:59 UTC