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: 3, Touché) by Rosco P. Coltrane on Thursday April 06 2017, @12:20AM (2 children)
I bet their telemetry servers don't either.
(Score: 2) by MostCynical on Thursday April 06 2017, @12:50AM
More likely they have cache servers (your own WinPC, for the telemetry), which will wait and send when the main server is back up.
Now we know why PCs never know how long a download is going to take - sometimes seconds are a lot further apart than others...
"I guess once you start doubting, there's no end to it." -Batou, Ghost in the Shell: Stand Alone Complex
(Score: 2) by NotSanguine on Thursday April 06 2017, @12:51AM
I bet their telemetry servers don't either.
Because reasons. [xkcd.com]
No, no, you're not thinking; you're just being logical. --Niels Bohr