Commit log on BitBucket shows improper timestamp

On my BitBucket git repo, the Commits page shows a commit as being "16 hours ago" when it was both committed and pushed only 22 minutes (as is reflected properly on the Overview page).

When I look at my BitBucket settings, I see:

Location: No location chosen
Update these details through your Atlassian account.

I've changed my TimeZone @ https://confluence.atlassian.com/users/viewmysettings.action but that hasn't helped at all. I see no way in all of the account management to get things to show other than "No location chosen."

I'm sure I'm missing some easy setting somewhere. Things are not tied (as I'd expect) to the settings that I have been able to find and change.

This seems to have been reported in the past. BCLOUD-16 looks related and there is a knowledge base entry @ https://confluence.atlassian.com/display/BitbucketServerKB/Timestamp+Incorrect+in+Bitbucket+Server

The KB entry seems to only apply to "on premise" BitBucket installations, so it doesn't apply to me. This article could be expanded upon to address my specific issue as they are very closely related.