Thanks @mccartney436 for the report, that was a useful one.

The timezone normally comes from the weather API, which returns the offset for the location itself. When that call fails, the site was falling back to a rough estimate based on longitude, which ignores daylight saving time. For Warsaw that gives UTC+1 instead of UTC+2, so everything shows one hour early. Exactly what you saw.

It’s now fixed: the fallback uses a real timezone table instead of the longitude guess. Reload the page and you should get the right times.

One thing I’m curious about, if you still have it open: did the panel show “UTC+1” instead of “GMT+2” at the bottom, and did you get a message about the weather being unavailable? That would confirm the diagnosis.