Delay in populating data needed for reporting purposes
Incident Report for CorpU
Postmortem

The network connections used by the production services to update the reporting database had to be re-created this weekend due to a dropped server. No data was lost within the production environment, however, services that needed the reporting database (i.e. dashboards) were using stale data until these connections could be re-established. The majority of the re-created connections were properly working by late Sunday. Backend server tasks were then initialized to populate the machine calculations needed by some of the dashboards. Automated processes are now back-in-place to keep this data in-sync.

Posted Oct 13, 2020 - 19:34 UTC

Resolved
This incident has been resolved.
Posted Oct 13, 2020 - 19:10 UTC
Monitoring
A fix has been implemented and we are monitoring the results.
Posted Oct 11, 2020 - 06:37 UTC
Identified
Our data processing infrastructure is running behind which is causing inaccuracies in the reporting tools. No data has been lost and we are working on the connections needed to keep the reporting system up-to-date.
Posted Oct 11, 2020 - 04:22 UTC
Investigating
We are currently investigating this issue.
Posted Oct 11, 2020 - 02:40 UTC
This incident affected: Data Services.