Apple spent a week saying nothing while Apple Watch owners compared the time on their wrist to the time on the same wrist one second later. On Sunday it published a support document about it.
The document is titled "If your Apple Watch shows the wrong time after daylight saving time changes," and it confirms exactly what the forum threads described: your watch is not confused about the time. It is confused about one rendering layer of the time.
"This incorrect time appears only on the Always On display when your wrist is down," Apple says. "When you activate the display by tapping it or raising your wrist, the time changes to the correct hour."
That is a small admission with a big detail in it. Your watch knows what time it is. The dimmed frame it paints when your arm is at your side does not.
The timing was not accidental
European clocks went back on Sunday, October 25. US clocks went back on Sunday, November 1. Apple's document landed on the US date, which is the moment the audience for this bug grew from a few forum posters in the UK and central Europe to tens of millions of watches resetting themselves overnight.
We covered the first wave in our piece on the watchOS 27 daylight saving glitch, when the only evidence was a MacRumors forum thread with seven posters describing identical symptoms and one r/AppleWatch report on a Series 12. At that point Apple had said nothing, and the fixes circulating were user discoveries: restart the watch, or swap the face and swap back.
Those are now official.
What Apple actually tells you to do
The support document lists two fixes and one thing that happens on its own:
- Switch to any other watch face, then switch back to your preferred face. This is the one Apple lists first, which suggests it is the fastest path.
- Restart the Apple Watch. The old standby, still on the list.
- Do nothing, and the issue resolves itself at midnight following the time change. Apple states this plainly, and it is the most reassuring line in the document.
Apple also says alarms are not affected, and adds the usual note to keep the watch updated for bug fixes and security updates.
That last line is worth reading carefully. "Keep your watch updated" is not the same as "an update fixes this." Apple has not said a software update addresses the fault, and it has not named a version.
What Apple left out
Three things are missing from the document, and they are the three things owners keep asking.
Which watchOS versions are affected. Apple's language is generic: "after daylight saving time changes in your area." Our October reporting found it on watches running watchOS 27, including current hardware like a Series 12. Whether it reaches back into watchOS 26 installs is not stated anywhere official.
Which models. No list. The forum reports clustered on recent Apple Watches, but that may reflect who upgrades and who posts, not which hardware has the defect.
Why it happens. Apple describes the symptom and skips the mechanism. The best guess, and it is a guess, is that the Always On layer holds a cached timezone offset and only rebuilds when the face is redrawn or the watch reboots. That would explain both fixes working and would explain why the active display renders correctly the whole time.
The practical side effect of that gap: if you noticed the bug three days after the change and did nothing, the midnight cure has already passed you by. Do the face swap.
This is not a new class of bug
9to5Mac noted that daylight saving problems go back to the Apple Watch Series 4, with fixes shipped and the issue returning in later cycles. That history matters for how you read this one.
A time zone transition is one of the rare events where every device in a household changes state at the same instant, and it happens twice a year, at 2am, on a weekend. It is exactly the kind of condition that survives a year of testing because nobody on the test team happens to be wearing the watch when the offset flips.
For a phone that is a minor annoyance. For a watch it cuts deeper. The whole contract of a wristwatch is that a glance tells you the truth. A watch that is right when you look properly and wrong when you glance is arguably worse than one that is simply wrong, because it teaches you not to trust the glance. We made that point in October and it still holds.
If yours is still off
Check the two displays against each other, deliberately. Raise your wrist, read the time, then lower it and look again at the dimmed face. If the minute matches and the hour does not, you have the bug and not a timezone setting.
Then try the face swap first, because it takes five seconds. Watch face, hold, swipe to a different one, then come back. If that does not clear it, restart the watch. If it comes back after a reboot, Apple's document has nothing further to offer, and you should report it, because the company has now formally acknowledged the symptom and has somewhere to file the next one.
For anyone thinking about a new watch this month rather than nursing an old one through a second time change, the Apple Watch Series 12 and the Apple Watch Ultra 4 are both in the mix, and both are on the hardware the reports have come from. Black Friday timing may matter more than the model choice, given what has happened to pricing this year.
Bottom Line
Apple has confirmed the bug, published two fixes that owners had already worked out for themselves, and quietly pointed at a third that requires patience and a midnight. What it has not done is name the affected software versions or ship a patch.
That makes this a documented, officially acknowledged, still-unfixed defect. Which is progress, and also not a fix. If your watch is one hour fast with your wrist down, swap the face, restart if you need to, and know that Apple is at least now on the record about it. We will be watching whether watchOS 27.2 or a later build actually addresses it, and whether the same render bug shows up again at the next switch, which for Europe and the US alike is March.
Sources: Apple Support document 149603, "If your Apple Watch shows the wrong time after daylight saving time changes" (the primary source for every quote and fix step here, reported as published on November 1, 2026), MacRumors' report of November 1, 2026, 9to5Mac's report of November 2, 2026 (which traces the daylight saving pattern back to the Series 4), MacTrast's write-up of November 1, 2026, Forbes' coverage of November 1, 2026, and Firstpost's report of the same day. The original symptom reports came from a MacRumors forums thread opened October 25, 2026 and an r/AppleWatch post on a Series 12 46mm. Apple has not named the affected watchOS versions or models, and no outlet has independently established the cause, so the mechanism described above is labeled as a guess.
