Hello again,

This issue is now fixed. It was caused bug a code change that
misinterpreted milliseconds when processing data for the visualisation.