Understanding US Time Zones

Most people think there are four time zones in the US. There are actually six if you count Alaska and Hawaii-Aleutian properly. Eastern, Central, Mountain, Pacific, Alaska, and Hawaii-Aleutian. That is the baseline. But the real friction happens when you are scheduling something across those zones and someone forgot Daylight Saving exists this year.

The Basics You Already Know

Eastern is UTC-5 standard, UTC-4 during DST. Central is UTC-6 standard, UTC-5 during DST. Mountain stays a weird outlier for most of Arizona but does shift with the Navajo Nation. Pacific is UTC-8 standard, UTC-7 during DST. Alaska is UTC-9 standard, UTC-8 during DST. Hawaii-Aleutian is UTC-10 standard, UTC-9 during DST and the Aleutian Islands cross into the other side of the international date line. I used to write scripts that assumed every zone observed DST uniformly. This caused problems. In 2021 I had a deployment schedule that landed at 2 AM instead of 12 AM because I mapped everything to a single UTC offset without checking whether the target zone was currently observing DST. The fix was switching to IANA timezone database identifiers like America/New_York instead of raw offset calculations. Once I did that, the whole system stopped breaking at the March and November boundaries.

Unwind The Time A Comprehensive Guide To Us Time Zones

If you are looking for a structured way to handle this, Unwind The Time A Comprehensive Guide To Us Time Zones covers the mechanics without padding it with filler content. It walks through how the federal rules actually work, not just the textbook definitions. The guide breaks down which states observe DST and which do not, the current uniform federal rules, and the historical oddities that still trip people up. One thing the guide gets right is explaining the switch dates. DST starts on the second Sunday in March and ends on the first Sunday in November. This has not always been the rule. It changed in 2007 under the Energy Policy Act. Before that, the dates were different. If you are working with legacy systems or old records, this matters.

Where It Gets Messy

Arizona does not observe DST except for the Navajo Nation. That means when the rest of the state shifts to UTC-7, most of Arizona stays on UTC-7 year-round, but the Navajo Nation shifts too, creating a pocket of confusion inside the state. I have seen meeting invites sent to Phoenix addresses show up in the wrong local time because the sender assumed uniform state behavior. Indiana is another mess. Before 2006, some counties observed DST and others did not. The state standardized it, but the history shows up in old databases. If you are parsing historical appointment data from Indiana, you might find entries that imply two different time conventions depending on which side of a county line the location sits.

How I Use This Stuff Daily

I maintain a shared calendar for a distributed team across four states. I use explicit IANA identifiers for every event. When a timezone change is proposed at the federal level, I check what actually takes effect before updating any automation. The guide mentions tools like timezoneconverter.com for quick lookups, but I rely on libraries like moment-timezone or date-fns-tz in code. The principle is the same: do not store raw offsets. Store zone identifiers. There is also the issue of military time zones, which the guide touches on briefly. Zulu time is UTC. Local military time uses letters J, M, etc. These rarely come up outside defense contracting, but if you are coordinating with DoD systems, you will encounter them and they do not follow civil DST rules.

Limits Of Any Single Reference

No guide covers every edge case because the rules change. Congress can alter DST dates or exemptions at any time. The current framework is stable now, but the last major change happened in 2007. If you need guaranteed accuracy for legal deadlines or compliance reporting, cross-reference with current federal registers rather than relying solely on a static document. The guide itself warns against treating it as permanent law, which is the honest approach.