Clocks went back in the UK and central Europe on Sunday morning, and for most people every device in the house quietly handled it. Then there is the Apple Watch that woke up an hour ahead of itself.
Not all the time. That is the strange part. Raise your wrist, and the time is right. Let the screen drop into the always-on state, and it flips back to summer time, an hour fast. Two clocks, one watch, disagreeing with each other.
The reports all describe the same thing
The thread that started it went up on the MacRumors forums early Sunday, from a user in central Europe: correct time when the watch is activated, summer time again on the always-on display. The reply underneath came from the UK and said exactly the same thing, then another UK owner, then two more in Europe. By Sunday evening seven separate posters in that thread had reported the same behaviour, and at least three of them had already tried the obvious fix and found it worked.
The same split showed up on Reddit. One r/AppleWatch post from Sunday describes an Apple Watch whose always-on display and active display show different times, on a Series 12 in 46mm.
That last detail is the one worth flagging. This is not a story about a three-year-old watch that never got a proper update. It is being reported on current hardware running the current release.
A couple of people also noticed it in standby mode. Same symptom, same hour of error.
Two fixes, both crude and both working
Nobody has a proper solution, because Apple has not acknowledged the problem. What users have found is closer to the old IT joke about turning it off and on again.
- Restart the watch. This is the fix that comes up most in the MacRumors thread. Three separate posters report that a restart cleared it, and it stayed cleared.
- Swap the watch face and swap back. One poster fixed it by changing to a different face and then returning to the original, without a restart.
Neither of those is a setting. That tells you something about where the bug likely lives. The watch knows the correct time, because the active display renders it correctly. What is wrong is the always-on rendering, which paints a dimmed frame of the face rather than driving the full display. A restart or a face change forces that layer to be rebuilt from scratch, which is why both work and why neither feels like a real repair.
Until Apple says otherwise, treat that as an educated guess rather than an explanation. The company has not commented on the reports, and the thread does not establish which watchOS 27 builds or which Apple Watch models are affected. Our own coverage of the reboot bug that hit Series 12 and Ultra 4 on watchOS 27.0.1 is a reminder that the first weeks of a new watchOS cycle have not been smooth this year.
The US should pay attention this week
Europe changing its clocks is a small inconvenience for a small number of people. What makes this relevant to a much larger group is the calendar.
US clocks go back on Sunday, November 1, 2026. If the same always-on glitch is sitting in watchOS 27 waiting for a time zone transition, a lot more people are going to meet it next weekend, and most of them will not have read a MacRumors thread about it.
So it is worth knowing the routine before it happens, rather than discovering it at 7am on a Sunday with somewhere to be.
What Apple's own guidance actually says
Apple's support documentation on time and time zone problems is written for the general case, not for this specific bug, but the steps are the right place to start. In order:
- Make sure the iPhone is connected to the internet and running the latest software.
- Turn on Set Time Automatically. On iPhone that is Settings, then General, then Date & Time. This is what lets the phone pass the correct offset to the watch in the first place.
- Turn on Setting Time Zone. That lives in Settings, then Privacy and Security, then Location Services, then System Services. It is easy to switch off and forget, and without it a device relies on the offset it last knew about.
- If you get a message that updated time zone information is available, restart the iPhone and the paired Apple Watch. Apple says this explicitly, and it is the step most people skip.
- Restart the watch anyway, or cycle the watch face, per the fixes above.
If none of that holds, Apple's manual fallback is to turn Set Automatically off and set the time zone by hand. That is a workaround for a device that will not correct itself, not a fix, and it means remembering to turn automatic time back on afterwards.
The wider pattern
Time zone handling is one of those jobs where a bug is invisible for 364 days and then very visible for one. Every operating system has shipped a daylight saving defect at some point, and the failure tends to look exactly like this one: the system clock is fine, the offset is fine, but one rendering path is holding a stale value.
For a watch, that is a worse place to have a bug than on a phone. The whole point of the thing on your wrist is that glancing at it tells you the truth without you having to think. A watch that is right when you look properly and wrong when you glance is worse than a watch that is simply wrong, because you stop trusting the glance.
If you are on watchOS 27 and your time zone just shifted, check the always-on display against the active one before you assume everything is fine. Then restart the watch and check again.
Bottom Line
This is a real but narrow glitch: always-on display stuck on summer time after the European switch, reported across seven posters in one forum thread plus Reddit, on current watches, with a restart or a watch face swap as the working fix.
The reason to care now is November 1. If you are in the US and you want your Apple Watch Series 12 or Apple Watch Ultra 4 to be right when you wake up next Sunday, the two minutes it takes to restart it on Saturday night are cheap insurance. We will be watching whether the same reports appear on this side of the Atlantic, and whether Apple says anything about watchOS 27 before then.
Sources: MacRumors forums thread "WatchOS 27 DST glitch" (opened October 25, 2026, seven posters reporting the symptom and the fixes that worked), MacRumors report of October 26, 2026, an r/AppleWatch post from October 25, 2026 on a Series 12 46mm, and Apple Support document 101619, "If you can't change the time or time zone on your Apple device." One independent write-up of the reports exists alongside MacRumors; no second outlet has independently verified the cause, and Apple has not commented, so the symptom description here rests on the public forum threads.
