We are writing to share additional context around the reporting issues that you may have experienced over the course of this incident.
MachineMetrics aggregates data for historical reporting in our data warehouse. Around the start of Daylight Savings Time, there was a scenario where time periods were created with the same start time and end time, resulting in time periods with a zero time duration and anomalous aggregation and reporting behavior which was later resolved.
Time periods with a zero time duration have been created shortly after Daylight Savings Time for the past few years. These caused no impact in previously, however, due to other changes within the past year, these blank periods caused problems with data aggregation with this time change. The underlying data was reporting and recorded properly; it was the aggregation around these time periods that was problematic. Over the past few days, we've changed the code to not create these meaningless time periods, correcting the aggregation problem.
To summarize, no data was compromised, and the data aggregates underlying the historical reports were able to be restored once we identified the problem and found a sustainable solution.
Again, thank you for your patience.