If you are absolutely sure nothing else has changed, the reason is as simple as it is frustrating: your server's realtime clock has drifted more than 15' to the universal time. Please ask your host to fix their server's realtime clock.
In all similar cases we have seen over the years, it's invariable one of two issues:
- The host messed up an update which means their servers are no longer running
ntpd
, the network time protocol daemon which updates the realtime clock from atomic clocks around the world, countering the (inevitable) time drift of the hardware realtime clock.
- The host messed up the timezones and the issue happens around the switch-over date from standard time to daylights saving time, or vice versa.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!