May be related to recent usage query changes, or may have been there before those changes, not 100% sure. Most likely the issue is we are selecting a latest stat somewhere with a 0ms instead of correctly selecting max from the period. Most likely related to a specific type of session since it only seems to affect some users.