When Does Daylight Savings Time End: The 2025 Clock-Shift Science and Schedule

Daylight saving time ends on the first Sunday of November. In 2025, that is November 2, when clocks in most US states fall back one hour at 2:00 a.m. local time. The official change happens at 2:00 a.m. local standard time, which instantly becomes 1:00 a.m. That single repeated hour is the mechanical heart of the whole event.

The 2 A.M. Mechanism and the Repeated Hour

The fall transition is not a gradual fade. It is a discrete reset of civil time, and the government defines the exact instant it occurs. Under the current federal rule, daylight saving time ends at 2:00 a.m. local time on the first Sunday in November. At that moment, clocks are set back one hour to 1:00 a.m. standard time.

The result is a local hour that occurs twice. A clock reading 1:30 a.m. can refer to two different real moments, one before the reset and one after. Software engineers call this the "fall-back ambiguity," and it is why time-zone libraries store offsets rather than simple wall-clock strings. The offset changes from daylight time to standard time in a single step. In US Eastern Time, the offset moves from UTC−4 to UTC−5. That is the whole mechanism: a legislated offset change, applied at a fixed local instant, producing a duplicated hour.

The spring transition is the mirror image. Clocks jump from 1:59 a.m. to 3:00 a.m., and an hour of local time never occurs. Fall repeats an hour; spring deletes one. Both are administrative events, not astronomical ones. The sun does not change; the label on the clock does.

The Numbers Behind the Shift

The scale of the change is easy to underestimate. For most Americans, the fall shift adds one hour to the calendar day, making it 25 hours long. Sunset appears to arrive about one hour earlier on the clock, even though the physical sunset time changes by only a minute or two day to day. The abrupt jump is the clock, not the sun.

The annual cycle has two fixed anchors in the US: daylight saving time begins on the second Sunday in March and ends on the first Sunday in November. That is roughly 238 days of daylight time and 127 days of standard time in a typical year. The November end date has been the rule since 2007, when the Energy Policy Act of 2005 took effect. Before that, the fall-back date was the last Sunday in October.

The geographic reach matters too. Daylight saving time is observed in most, but not all, US states. Hawaii and most of Arizona skip it. So do Puerto Rico, Guam, American Samoa, and the US Virgin Islands. That means the November 2 change affects a large majority of the country but not all of it, and the map of who shifts is a patchwork rather than a uniform national event. (Source: US Department of Transportation, which oversees time zones.)

Edge Cases: Where the Rule Bends

The clean "first Sunday in November" rule hides several complications. The first is the difference between local time and the instant of change. The transition happens simultaneously across a time zone, but the local clock reading at that instant differs by zone. Eastern, Central, Mountain, and Pacific zones all fall back at their own 2:00 a.m. local time, which are different real-world moments.

The second edge case is the repeated hour itself. Any event scheduled during 1:00–1:59 a.m. local time on November 2 is genuinely ambiguous. A meeting at 1:30 a.m. could mean either occurrence. Systems that rely on timestamps without offsets can misorder events, double-count transactions, or fire a scheduled job twice. This is not hypothetical; it is a known class of software bug that reappears every fall.

A third case is the state-level exception. Arizona's choice to stay on standard time year-round means its residents do not experience the November reset. Travelers crossing from Arizona into a neighboring state during the transition window can encounter a one-hour discrepancy that depends on direction and timing. The same applies at the national level, where countries set their own dates. Europe, for example, ends its summer time on a different schedule, so there are weeks each year when US and European offsets are not what travelers expect.

Misconceptions About the November Change

Several persistent beliefs about the fall transition are wrong or oversimplified. The most common is that the change is about farmers. In fact, the modern US rules trace to energy policy and standardization, and the farm lobby has historically been ambivalent or opposed. The November end date is a legislative schedule, not an agricultural one.

A second misconception is that the change affects sunrise and sunset themselves. It does not. The sun rises and sets at the same physical times; only the clock labels shift. A third is that the repeated hour is harmless. For most people it is a minor annoyance, but for systems that schedule by wall-clock time, it is a real failure mode. A fourth is that everyone in the US changes on the same date. The Arizona and Hawaii exceptions, plus the territories, make that false.

A counterintuitive detail worth flagging: the fall transition is generally easier on sleep than the spring one. Falling back adds an hour of potential sleep, while springing forward removes one. The spring change is the one associated with short-term sleep disruption in the days after the shift. The fall change is less disruptive for most people, though the earlier sunset can affect evening routines and mood for some. That asymmetry is a useful professional caveat: do not treat the two transitions as equivalent.

Comparison of Time-Keeping Options

The table makes the trade-off explicit. Every option removes the repeated hour but changes when daylight lands. Year-round standard time favors morning light. Year-round daylight time favors evening light. The current rule splits the difference twice a year at the cost of two clock resets.

Timeline of the 2025 Fall Transition

The timeline shows why the hour is ambiguous. The same wall-clock labels appear twice, separated by the reset. Systems that log only the label cannot tell the two passes apart. Systems that log the offset can.

Practical Actions Before the Change

The fall transition is low-stakes for most people but worth a short checklist. The goal is to avoid the two failure modes: missed schedules and ambiguous timestamps.

Set clocks back one hour before bed on Saturday, November 1, or let networked devices update automatically. Check devices that do not auto-update, including some appliances, car clocks, and older watches. Review any scheduled task or automation set between 1:00 and 2:00 a.m. local time on November 2 for duplicate-run risk. Confirm the time zone on calendars and meeting invites for early-morning November 2 events. Note the earlier sunset and adjust evening outdoor plans, commutes, and lighting accordingly. If you travel across state lines near the transition, verify the destination's observance rules.

The thresholds here are simple. Any automated job scheduled in the 1:00–1:59 a.m. window is the main risk. Any device without network time is the second. Everything else is routine.

Limits and What the Rule Does Not Cover

The federal rule sets dates, but it does not settle every question. It does not guarantee that all states observe daylight time, and it does not resolve the repeated-hour ambiguity for software. It also does not address the health and behavioral effects of the shift, which are studied but not fully settled. The evidence on sleep disruption is strongest for the spring transition and weaker for the fall one. Claims that the fall change causes broad harm should be treated cautiously.

The rule can also change. Congress has repeatedly considered permanent daylight time or permanent standard time, and no change is guaranteed. The current dates are the ones to plan around until legislation says otherwise. That is the honest limit: the schedule is stable now, but it is a policy choice, not a physical constant. For anything scheduled near 2:00 a.m. on the first Sunday in November, the safe assumption is that the hour is ambiguous and the offset must be stored explicitly.