On October 30, 2026, Apple published an official support article about a Daylight Saving Time (DST) bug on Apple Watch. After the clocks change, the Always On display can show the wrong hour. Apple’s article, If your Apple Watch shows the wrong time after daylight saving time changes, offers two quick fixes and says the glitch clears up on its own at midnight. Apple updated it on November 1, 2026, the same day most U.S. clocks fell back to standard time, according to MacRumors.
The short answer: if your watch looked an hour off this morning, don’t worry. Your Apple Watch isn’t broken. Only the dimmed screen you see with your wrist down shows the wrong hour. Raise your wrist or tap the screen and the correct time appears. Apple’s support article says alarms aren’t affected. To clear it now, switch to a different watch face and back, or restart the watch. If you do nothing, Apple says it fixes itself at midnight after the time change. Sources cited below were retrieved November 2, 2026.
Quick Reference: Apple Watch daylight saving time bug at a glance
| Question | What Apple’s support article says |
|---|---|
| What’s wrong? | The Always On display (wrist down) can show the wrong hour after a DST change |
| Is the real time wrong? | No. The active display (wrist raised or screen tapped) shows the correct time |
| Are alarms affected? | No |
| Official fix #1 | Switch to a different watch face, then switch back |
| Official fix #2 | Restart your Apple Watch |
| If you do nothing | The Always On display corrects itself at the midnight following the time change |
| Specific watchOS build or model named? | No |
What Happened: The Apple Watch DST Bug and Apple’s Fix
The timeline is short. It follows the two separate DST changes in Europe and the U.S.
- October 25, 2026: After clocks changed in the UK and Europe, Apple Watch owners started reporting that their Always On display showed the wrong hour. Threads appeared on r/AppleWatch, including one titled “WatchOS is wonky after daylight saving time change”.
- October 26, 2026: MacRumors covered the reports in Apple Watch users report DST glitch on watchOS 27.
- October 30, 2026: Apple published support article 149603. It confirms the issue and lists the fixes.
- November 1, 2026: Apple updated the article. The same day, most U.S. clocks changed back to standard time, and MacRumors reported on Apple’s fix steps. Forbes also published its own explainer.
What the bug actually looks like
With Always On turned on, your watch dims the screen when your wrist is down. That saves power. In this dimmed state, it may show the hour from before the time change, so it’s an hour off.
Wake the watch by raising your wrist or tapping the screen, and it shows the correct time. Apple’s support article says the bug doesn’t affect alarms or the active display. So the watch keeps time correctly. The glitch is in what the dimmed screen shows.
What Apple did not say
These gaps matter, so here they are plainly:
- No specific watchOS build is named. MacRumors’ October 26 headline links the reports to watchOS 27, but Apple’s support article doesn’t list an affected or fixed watchOS version.
- No specific Apple Watch model is named. Apple doesn’t say whether some models are affected more than others.
- No root cause is given. Apple describes the symptom and the fixes. It doesn’t explain why it happens.
- No press release found. We found no Apple Newsroom post about this issue, and the support article is the only official Apple statement we located. We can’t confirm that no other official statement exists elsewhere.
Who This Affects
Apple’s support article describes this as a watchOS issue tied to the Always On display. The article doesn’t specify which exact Apple Watch models or settings are covered beyond requiring Always On to be turned on, so the full scope isn’t confirmed.
Apple’s article doesn’t mention iPhone, iPad, or Mac, and nothing in the reporting we reviewed points to the bug on other Apple devices. That said, Apple’s documentation doesn’t explicitly state that no equivalent issue exists on other platforms, so we can’t call this strictly watchOS-only based on what Apple has published.
If your watch doesn’t support Always On, or you’ve turned it off, you shouldn’t see this symptom. Without Always On, the screen goes dark when your wrist is down. There’s no dimmed clock to get wrong. That’s our reading of Apple’s scope, though Apple’s article doesn’t state it directly.
Where you live changed the timing, too. People in the UK and Europe hit the bug first in late October. U.S. users could see it after November 1. That’s why Apple’s update that day was well timed.
The Details: Apple’s Two Official Fixes
Apple’s support article lists two fixes, plus a third “do nothing” option. None of them costs anything, and for this particular glitch Apple’s guidance doesn’t call for a repair or a new watch.
Switch watch faces and back. Press and hold the watch face, swipe to a different face, and select it. Then switch back to the face you normally use. Apple lists this first. It’s the least disruptive option because you don’t lose anything and the watch stays on.
Restart your Apple Watch. If switching faces doesn’t clear the wrong hour, press and hold the side button until the power-off option appears. Turn the watch off. Then press and hold the side button again to turn it back on. It’s more thorough, just a bit slower.
Wait until midnight. Apple says the Always On display corrects itself at the midnight following the time change. If the wrong hour doesn’t bother you, you can ignore it. The trade-off? You might glance at your lowered wrist during the day and read the wrong time.
Apple also has a broader support page, If you can’t change the time or time zone on your Apple device. It covers general date, time, and time zone problems. Use it if your watch shows the wrong time even when awake. That’s a different issue from this DST display glitch.
How It Stacks Up
We usually compare Apple’s handling with Google’s Pixel Watch, Samsung’s Galaxy Watch, Microsoft’s products, and Apple’s own past behavior. For this story, the evidence is thin. We’d rather tell you that than make something up.
| Platform | Equivalent DST display bug documented in our research? | Official vendor fix found? |
|---|---|---|
| Apple Watch (watchOS) | Yes: Always On display shows the wrong hour after DST | Yes: support article 149603 (Oct 30, 2026; updated Nov 1, 2026) |
| Google Pixel Watch (Wear OS) | No verified reports found in our research | Not applicable |
| Samsung Galaxy Watch (Wear OS) | No verified reports found in our research | Not applicable |
| Microsoft / Windows | No verified equivalent found in our research | Not applicable |
Android smartwatches: We found no verified reports of a similar bug on the Pixel Watch or Galaxy Watch this season. That doesn’t prove they’re immune. Our research just didn’t turn up a documented equivalent, so we can’t say whether Apple did better or worse here.
Windows: Microsoft doesn’t make a smartwatch. We found no documented DST display bug on Windows to compare against.
Previous Apple versions: Apple’s support article doesn’t say whether earlier watchOS releases had this issue. Our research didn’t include any data on past Apple Watch DST glitches, so we can’t compare before and after.
What we can compare is Apple’s response. It took about five days to go from the first wave of reports (October 25) to an official support document (October 30). Apple then refreshed that document before the U.S. time change. It gave users fixes they can do themselves instead of making them wait for a watchOS update. If you’re switching from Android or Windows, that’s a useful look at how Apple sometimes handles small, visible bugs: a public support note comes first.
The Reaction
So far, most of the discussion has come from Apple Watch owners confirming they saw the glitch. Several r/AppleWatch threads appeared as the clocks changed, including “Daylight savings glitch?”. Broader opinion on how Apple handled it is still forming. We didn’t find a Hacker News discussion, and we don’t have verified commentary we can fairly sum up.
Our Take
Verdict: Apple responded well, but a support note is still only a workaround.
Did Apple do better, later, or worse than the competition? We can’t fairly answer that part. There’s no verified Wear OS or Windows equivalent in the evidence. What we can judge is Apple against its own standard. Apple confirmed the bug publicly within about a week of the first reports.
It told users plainly that alarms and the active display were unaffected, offered two simple fixes plus a “just wait” option, and updated the guidance before the U.S. change hit. For a cosmetic bug, that’s a solid, honest response.
The weak spot is what’s missing. Apple hasn’t named a watchOS version that permanently fixes the problem, and it hasn’t explained the cause. Switching faces or restarting is fine for a one-off glitch. But a watch should show the right time on every screen without your help, and DST changes happen twice a year. We’d like Apple to confirm a permanent software fix before the next spring change.
Should you upgrade? No. Nothing in Apple’s guidance suggests a hardware fault, and you don’t need a new Apple Watch to fix this. Checking for updates in Settings > General > Software Update on your watch is always sensible. Just know that Apple hasn’t said any update fixes this bug.
Quick Answers
Is my Apple Watch broken? No. Apple describes this as a display issue limited to the Always On screen. The active display shows the correct time.
Will this mess up my alarms or calendar? Apple’s support article says alarms aren’t affected. It doesn’t mention the calendar specifically. The bug only affects what the dimmed Always On screen shows. The watch’s actual time is correct.
Do I need to update watchOS or buy a new Apple Watch? Neither is required. Apple’s fixes are switching watch faces or restarting. No specific watchOS update is named as the fix.
How long until it fixes itself if I do nothing? Apple says the Always On display corrects itself at the midnight following the time change.
Did other smartwatches have this problem too? We found no verified reports of an equivalent bug on Galaxy Watch or other Wear OS watches. That only means we found no evidence. It doesn’t prove they’re unaffected.
Wrapping Up
If your Apple Watch showed the old hour on its dimmed screen after the clocks changed, now you know why. It’s a known display glitch, it doesn’t affect your alarms, and you can clear it in seconds. Apple lists switching faces as one of its two fixes, and a restart is the other. If you do nothing, Apple says the display corrects itself at midnight after the time change. Apple handled the communication well, but we’d still like a permanent watchOS fix before the next time change.
| Step | Action | Applies To |
|---|---|---|
| 1 | Raise your wrist or tap the screen to confirm the correct time | Apple Watch with Always On enabled |
| 2 | Switch to a different watch face, then back | Apple Watch running watchOS |
| 3 | Restart with the side button if the hour is still wrong | Apple Watch running watchOS |
| 4 | Or do nothing; Apple says it corrects at the following midnight | Apple Watch running watchOS |