G'day,
We just noticed the same thing on a new install of DSS Lite.
The only extra clue I have is I think the Date/time may have been wrong at the start, ie in the first few minutes, until the right TimeZone/NTP were setup. So it may have been active for perhaps 30 minutes before we made the NTP change?

Now I recall that MRTG (which I assume DSS uses) used to have a problem if the dates changed, and generated a "Time warp" error, warning that it had data from the future.

But I can't see any logfile that may help out....

So its a bit of a mystery to us as well....

Cheers Ben