could it be that you are just connecting to an "off-time" computer... (Some fast hubs report things like "location NewYork", though you are net-fast and through a fiber-hub in "California". Thus, it might be "assuming" your IP is in another timezone that doesn't match the one on your computer. Irrelevant to your actual connection.)

You would have to do a reverse DNS look-up of "what it thinks your IP" actually is. (As some blocks are/were once locked to specific areas, but have been recently "released" for resale since they started using IPV6, or you may be going through an IPV6->IPV4 or IPV4->IPV6 external "router" on your network. Which I think can also be detected, but not avoided in all instances.)

One way to find-out.... is to change your time/date to another time zone, and another... and another.. until you find the one it "Thinks" you are in.

Time is irrelevant on the net... Pings should be the time-adjustment to any single computer that is "asking for a sync". Dates should never be trusted. Stuff gets there, when it gets there. No matter the time. That is horrible code if it depends on any user-set times... then goes so far to tell you that you are wrong... Well, if it is wrong, the fix it for me, or ignore it, or stop looking at it... Stupid program. lol.