Clocks Go Back November 1: Why Your Security Camera Won't Fix Itself — and What Else the Time Change Quietly Breaks

At two o'clock in the morning on Sunday, November 1, 2026, the clocks go back an hour. NIST — the federal agency that keeps official time for the United States — puts it precisely: "During 2026, daylight saving time is in effect from March 8 at 2 a.m. (local time) to November 1 at 2 a.m. (local time)." At that moment, in NIST's own words, "the local time becomes 1 a.m. and that hour is repeated, so there is an extra hour in that day."

Your laptop, your phone and your tablet will deal with this by themselves while you are asleep, and you will never think about it again. That is genuinely the end of the story for most of the technology in a modern house.

The problem is the other category: the things with their own little clock inside, configured once by somebody else, that nobody has logged into since. Camera recorders. Alarm panels. Irrigation controllers. The timer that runs the shop's sign. A time clock on a back-office wall. These are the devices that turn up exactly one hour wrong, stay that way for months, and get discovered at the worst possible moment — which, for a camera system, is the afternoon you finally need to hand footage to somebody.

This is the one piece of annual household tech maintenance that genuinely pays for itself, and it takes about ten minutes. Here is what breaks, why, and what to actually check.

The single fact that explains almost every device that ends up an hour off

Nearly every connected device in your house sets its clock over the internet using something called NTP — Network Time Protocol. People assume that because a device is "syncing with an internet time server," it must be getting the right local time. It is not, and this is the heart of the whole thing.

NIST says it plainly on its own daylight saving time page: "All NIST time services broadcast Coordinated Universal Time (UTC). Corrections for your local time zone and for daylight saving time are provided by your computer's operating system." And more bluntly still: NTP "contains no information about DST, and relies on your computer's operating system to determine whether DST or ST is in effect."

Read that twice, because it inverts how most people picture the problem. The time server does not tell your camera that it is November. It hands over one number — the current time at the Greenwich meridian — and then the device itself has to know two things on its own: which time zone it sits in, and whether daylight saving is currently running. The time server is not involved in either decision.

So a device can be syncing perfectly, every hour, to an impeccable federal time source, and still display the wrong hour for five months. It is not a sync failure. It is a device applying the wrong local rule to a perfectly good number.

This also kills a piece of advice you will find repeated on half the camera forums and vendor blogs on the internet: that you should fix an hour-off camera by switching to "an NTP server that supports daylight saving." There is no such thing. NTP does not carry daylight saving information at all, so no server you choose can supply it. Changing time servers will fix a clock that is off by seconds or minutes. It cannot fix one that is off by exactly an hour.

That word "exactly" is the diagnostic, and it is worth keeping. A clock that drifts by minutes is a sync problem. A clock that is wrong by a precise, unchanging hour is a rule problem — a time zone or a daylight saving setting — and you will never fix it by poking at the network.

Why your computer and phone are fine, and what that depends on

If NTP carries no daylight saving information, why do your laptop and phone always get it right? Because they carry the rules themselves. Your operating system holds a table of every time zone in the world and the daylight saving rules that go with each one, and that table gets updated along with everything else when the machine installs updates.

NIST attaches exactly that condition: "There shouldn't be any problems if your operating system has the latest updates," and "it is important that you have the latest software updates for your operating system." The automatic, invisible, nothing-to-do-here behaviour you are used to is a service your operating system performs for you, and it is one of the quieter reasons that a computer left years behind on updates becomes unreliable in ways that have nothing to do with security.

If your actual Windows PC is showing the wrong time — before the clock change, after it, or permanently — that is a different and much more fixable problem, and usually one setting or a three-dollar battery. We have a separate walk-through for that, and it is worth doing first so you are not debugging two things at once.

The exception that proves the rule: the clock that really does know

There is one kind of household clock that genuinely receives daylight saving information over the air, and the contrast is useful. Radio-controlled clocks — the "atomic clock" on the wall or the bedside alarm that sets itself — listen to NIST's WWVB radio signal, and NIST confirms that "the WWVB broadcast contains information that tells your clock whether DST or ST is currently in effect." Those will change on their own, correctly, on the right date.

But NIST also documents the failure mode that matters for every other appliance in the house, and it is the same failure mode as the camera recorder. Some clocks ignore the broadcast flag and instead have the calendar rule burned into their firmware. The rules changed in 2007 — NIST notes they were "enacted by the Energy Policy Act of 2005," which lengthened daylight saving by about a month, so it now runs 238 days, roughly 65% of the year. Any device built with the pre-2007 rule in it is still obediently following a law that no longer exists. In NIST's words: "Some clocks have the old date rule programmed in... These clocks will switch on the wrong date."

NIST is blunt about the remedy for clocks like that, too — the self-setting "AUTOSET" and "SMARTSET" types that are not radio-controlled: "your only recourse is to adjust the clock manually, or to contact the manufacturer and ask for an upgrade or a replacement."

For a microwave this is a shrug. For anything that runs a schedule off that clock, it is not.

Security cameras: the setting that is really a copy of federal law, typed in by hand

This is the one worth your attention, and the camera makers document it themselves in a way that makes the problem obvious once you see it.

Reolink's own instructions for setting daylight saving — which the page says applies to "All Reolink cameras and NVRs" — describe three things you configure yourself. You turn DST on. You set the "Offset," which Reolink defines as "the number of hours added to the current time," and which you can set to one hour or two. Then you set the start and the end: "Start Time refers to when the DST settings take effect. You can specify the month, week, day, hour, minute, and second," and "End Time refers to when the DST settings stop."

On the recorder itself, through a monitor, it is the same shape — Reolink's NVR instructions say to go to System, then Time and Language, and "Enable Adjust for Daylight Saving Time... Select the Time Offset, Start Time and End Time according to your local time."

Sit with what that actually is. You are not switching on an automatic feature. You are hand-entering your own private copy of United States daylight saving law into a settings page, down to the minute and second, and the box will follow whatever you typed, forever, without ever checking whether it is still correct.

Which means there are a lot of ways for it to be wrong, and all of them are mundane. It was set up with the pre-2007 dates, so it changes in April and October instead of March and November. It was configured by an installer working from a different country's rules. Somebody turned it off during a troubleshooting session two years ago to see if that helped, and never turned it back on. Or it was simply never touched at all, so the camera has been an hour out since the day it went up and everyone assumed that was normal.

None of those get fixed by the device. There is no update that corrects it, because the rule is not software — it is a value you entered.

The symptom, in the vendor’s own words — and the fastest fix

Reolink has a dedicated troubleshooting page for this, and it is refreshingly direct. Under "Applies to: All Reolink device," it describes the "phenomenon" as "the time displayed on the camera differs from the local time by 1 hour" and gives the cause as, simply, "Daylight Saving Time (DST) Setting." The fix it recommends is to "check whether the start and end dates of DST setting are consistent with the local setting."

There is one shortcut buried in the same page that is worth knowing, because it is much quicker than editing date fields on a phone. Reolink notes that in the mobile app "it only has a synchronization button. After synchronization, it will be synchronized to the Camera according to the daylight saving time on the mobile phone." In other words, the app does not configure the rule — it copies your phone's current idea of the time onto the camera.

That is genuinely useful on the Sunday morning after the change: if your phone is right, one tap pushes the right time onto the camera and you are done for now. But understand what you have and have not done. You have corrected today's time. You have not corrected the rule, so unless the start and end dates in the settings are actually right, the same thing will happen again in March. A sync button is a patch. The date fields are the fix.

Other brands use different words for the same three settings, so do not expect the menu to match. What you are looking for on any recorder is a daylight saving or DST section with an enable switch, an offset, and a pair of dates — and a separate time zone setting, which is the other place an exact-hour error hides.

Why one hour matters more than it sounds: the footage you have to give somebody else

An hour of error on a camera feels cosmetic right up to the moment the recording stops being for you.

The whole reason to own cameras is the handful of days a decade when something happens and the footage becomes evidence — a break-in, a hit-and-run in front of the house, a package that never arrived, a delivery driver who says they knocked, a contractor dispute, an insurance claim. In every one of those situations you do not watch the video yourself. You give somebody a time, and they search for it.

So you tell the adjuster or the deputy it happened just after seven in the evening. They scroll to seven in the evening. The file sits at six. Depending on who is looking and how patient they are, the outcome ranges from an awkward extra twenty minutes to "there is no footage of that," and the second outcome is the one that costs you the claim. A timestamp that is confidently and consistently wrong is worse than no timestamp, because nobody thinks to doubt it.

The repeated hour adds a specific, strange wrinkle on November 1 itself. Because 1 a.m. to 2 a.m. happens twice that morning, anything your system records in that window exists twice, with the same label — two different real moments both stamped 1:30 a.m. If you ever need to establish exactly when something happened overnight on the first of November, that ambiguity is real and essentially unresolvable from the timestamp alone.

The check costs nothing and you should do it today rather than in November. Open time.gov on your phone — that is NIST's own clock — hold it up next to the recorder's display or the app's live view, and see whether they agree. Then do the same again on the Monday after the change. Two minutes, twice a year, and you find out while it is a chore instead of while it is an emergency.

Schedules: the ones that follow the clock, and the ones that follow the sun

The second thing the time change breaks is not a clock at all. It is everything you have told to happen at a particular time.

The distinction worth learning is simple. A schedule set to a clock time — "on at 6 p.m." — stays exactly where you put it on the clock, which means it moves an hour relative to actual daylight. A schedule set to sunset or sunrise tracks the sky and ignores the clock change entirely.

After November 1, sunset in our area arrives around an hour earlier by the clock than it did the week before. So every outside light, every illuminated sign, every camera spotlight you set to a fixed evening time is now switching on roughly an hour after dark instead of at dusk. Nothing is broken, nothing shows an error, and for about a month the front of the house is simply dark during the exact window — late afternoon into early evening — when people are coming home and porch thefts are easiest.

The fix is a habit rather than a repair: anything whose job is tied to daylight should be scheduled off sunset or sunrise, not off a number. Most modern lighting, camera and smart-plug apps offer that option, and once it is set it survives both clock changes and the slow drift of the seasons without you touching it again. Keep clock-based timing for the things that really are tied to human routine — the coffee maker, the thermostat setback when the house empties, the shop lights that come on with the first shift.

Irrigation deserves its own mention, because it is the schedule nobody watches. A controller set to water before dawn can quietly end up running after sunrise once the clock moves, which wastes water to evaporation and is the sort of thing that matters during restrictions. Worth a look while you are walking around anyway.

For a shop or small office: avoid the hour that happens twice

Small businesses have a handful of systems where a one-hour error is not cosmetic, and one scheduling trap that is easy to design out once you know about it.

The systems: card terminals and point-of-sale, where the receipt and batch timestamps are what you reconcile against and what you cite in a chargeback dispute. Door access and alarm schedules, which auto-lock and auto-arm at set times — an hour late means an hour unlocked. Time clocks, where the hour is somebody's pay. Scan-to-email on the copier, where the timestamp on a scanned contract may be the only date anyone has. And anything with an unlock schedule or an opening routine that runs before staff arrive.

The trap is the overnight window, and it follows directly from the mechanics. On November 1, the hour from 1:00 to 1:59 a.m. runs twice, so a job scheduled in there can fire twice. Going the other way in March, NIST notes that "at 2 a.m. the local time time skips ahead to 3 a.m." — the 2 o'clock hour simply does not exist that day, so a job scheduled in there does not run at all.

That gives you a clean rule with no judgement required: keep anything you actually depend on out of the 1 a.m. and 2 a.m. hours. A backup, a sync, a report, a nightly export or a scheduled reboot set for 3 a.m. or later is unambiguous on both clock-change dates, every year, in both directions. If your overnight backup currently runs at half past one, move it. It is a one-minute change that removes an entire category of "the backup ran twice" and "the backup never ran" mysteries — and the second one is the sort of thing you discover months later, when you need the backup.

The boxes nobody logs into: alarm panels, gates and installer-configured kit

The devices most likely to be wrong are the ones you were never given the password for.

An alarm panel, a gate controller, an access-control box, a recorder in a closet, a networked signage player — these were configured once, by whoever installed them, possibly years ago, and then deliberately left alone because they work. They each hold their own clock and their own daylight saving setting, and they are subject to exactly the same hand-entered-rule problem as the camera, with the added difficulty that getting into them requires credentials somebody wrote on the back of a manual in 2019.

You usually do not notice. An alarm that auto-arms an hour late still arms. A gate that unlocks an hour early still unlocks. The schedule is wrong in a way that produces no error message, which is why these can sit misaligned for years. If a system of yours has a schedule that matters — arming, locking, unlocking, recording at particular hours — the week after the clock change is the right time to confirm it is happening when you think, and to find out now rather than later whether anyone still has the login.

The ten-minute round of the house, done on the Sunday

Do this after the change, not before, because you want to see what the devices actually did rather than what you hope they will do. Sunday, November 1, over coffee.

Open time.gov on your phone first so you have a reference you trust. Then walk the house and compare: the camera recorder or camera app, the thermostat, the alarm panel, the irrigation controller, the outdoor lighting timer, the shop's sign or signage player, any time clock, the copier or printer that stamps scans, and the car if its clock is not pulling time from your phone. You are not reading these carefully — you are looking for one specific thing, a device that is off by precisely one hour, which tells you its rule is wrong rather than its clock.

Where you find one, fix the rule and not just the display: correct the time zone, confirm the daylight saving switch is on, and check the start and end dates if the device exposes them. Then check your schedules while you are in there, and move any outdoor lighting onto sunset rather than a fixed time.

If you want a prompt you will not forget, this pairs naturally with the smoke-alarm battery round that already happens at the clock changes. One walk, two jobs, twice a year.

Why this still happens at all

Worth knowing, because people reasonably assume this has been abolished by now. It has not. The current rules come from the Energy Policy Act of 2005 and took effect in 2007 — the first change in more than twenty years — and NIST records that Congress "retained the right to revert to the prior law" but has not done so. Daylight saving time and time zones are set federally, and NIST points out that they are regulated by the U.S. Department of Transportation rather than by NIST itself. So November 1, 2026 is a real date, and March 8, 2027 will be too.

One footnote that matters if you have property or family elsewhere, or a camera watching a second home: not everywhere does this. NIST lists the places that do not observe daylight saving time as Hawaii, American Samoa, Guam, Puerto Rico, the Virgin Islands and Arizona — "with the exception of the Navajo Indian Reservation, which does observe DST." If you are watching a camera in Phoenix from Los Angeles, the gap between the two changes twice a year, and the daylight saving switch on that device should be off, not on.

How we can help

Most of this is a walk around your own house with your phone, and if you have read this far you can do it yourself. The parts people hand to us are the ones behind a password nobody has.

The common one is a camera system where the time has been wrong for a while and nobody can get into the recorder. We will get into it, set the time zone and the daylight saving dates properly rather than just nudging the clock, point it at a sensible time source, and — while we are in there — tell you how far back your footage actually goes, which is the other thing people discover too late. If we installed or service your cameras, this is part of the job and not an extra visit.

For smart homes, we will do a schedule pass: move outdoor lighting and security-shaped automations onto sunset and sunrise, check the thermostat and irrigation schedules still match how you actually live, and clear out the automations that have been fighting each other since the last time somebody reorganised the app.

For small businesses, the useful version is an hour spent on the systems where a timestamp is a record rather than a convenience: the card terminal and point-of-sale, door and alarm schedules, the time clock, and the overnight backup window — which we will move out of the 1 and 2 o'clock hours so it stops being a question twice a year. If you are not certain your backup ran last night at all, start there, and we will check it with you.