Definitely! I thought we had fixed this, but apparently, it persists.
The data is likely logged correctly (we store everything in UTC). It's just the web UI that doesn't query the data correctly (for whatever reason doesn't take into account your timezone). I'll take a look at this.