A mysterious issue is affecting the default Windows NTP server (time.windows.com), according to multiple complaints coming from Reddit and Twitter users, screwing up everyone's computer clocks.
Based on reports, the time.windows.com NTP server is sending Windows users the incorrect time, sometimes off by seconds, but in other cases, off even by hours. The issue was spotted today, April 3, early in the morning, and is ongoing for at least 10 hours.
The impact was felt immediately by servers that rely on the Windows NTP service to schedule and execute tasks. Unhappy admins found their servers launching routines early or too late, botching scripts and crashing their applications.
[...] UPDATE: A Microsoft representative acknowledged the issue. "We investigated and quickly resolved the issue our time service experienced," the Microsoft spokesperson wrote in an email. Tests carried out by Bleeping Computer confirmed the Windows NTP serrvice is up and running at the time of this update.
Source: Bleeping Computer
(Score: 1, Interesting) by Anonymous Coward on Thursday April 06 2017, @12:03AM (1 child)
For example, affected people probably weren't able to visit any OCSP-stapling website, because the stapling is only valid for a fairly narrow window of time. And they might well have thought the problem was with the website.
(Score: 0) by Anonymous Coward on Thursday April 06 2017, @05:36AM
Tor refuses to work when the clock is badly wrong. "Our clock is %s behind the time published in the consensus network status document (%s GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!"