Alaska Time Zones Are More Complicated Than People Think
Most people assume Alaska sits on a single time zone. It doesn't. The state spans two, and the boundary between them cuts through territory most people can't find on a map. If you're scheduling something in Anchorage, you probably just need to know whether it's Alaska Standard Time or Alaska Daylight Time. But if you're working across the state, the details matter more than you'd expect. Anchorage itself sits in the Alaska Time Zone, which is UTC-9 during standard time and UTC-8 during daylight saving time. The zone is officially called Alaska Time (AKST/AKDT). It covers the southern and central portions of the state, including Anchorage, Juneau, and Fairbanks. The rest of western Alaska, including Nome and the Aleutian Islands, falls under the Hawaii-Aleutian Time Zone, which runs one hour behind. The boundary between these two zones follows a jagged line that starts near the western edge of Cook Inlet and runs westward, picking up places like Kenai and Soldotna while leaving Seward on the Alaska Time side. It then cuts across the Alaska Peninsula and continues into the Aleutians. The Aleutian Islands west of 169°30′W observe Hawaii-Aleutian Time year-round and do not observe daylight saving time. Everything else in that zone does observe DST.
This means you can have a business meeting where one participant is in Anchorage and another is in Attu Island, and they're eight hours apart during standard time but only seven during daylight saving time. That shift catches people off guard every single year.
How Alaska Handles Daylight Saving Time
Alaska follows the current U.S. daylight saving schedule: clocks spring forward on the second Sunday in March and fall back on the first Sunday in November. This has been the rule since 2007, when the Energy Policy Act standardized DST dates across the country. Before that, the dates varied and caused confusion that lasted for decades. There was a brief period between 1942 and 1945 when the entire United States, including Alaska, stayed on perpetual wartime time. Alaska ran Alaska-Washington-Pacific Time year-round. Some older residents in rural areas still refer to that era colloquially as "War Time," and you'll hear it come up in conversations at the hardware store in Palmer. It doesn't affect scheduling, but it explains why some people have strong opinions about when DST should start. The Alaska Time Zone observes DST. The Hawaii-Aleutian Time Zone portion that lies east of the 169°30′W meridian also observes DST. The portion west of that line, including the far Aleutians, does not. This split creates the odd situation where part of Alaska is on the same time as Hawaii while the rest of the state is an hour ahead.
Get the Full Details
The Edge Case That Actually Messed Things Up For Me
Around 2019, I was coordinating a multi-location project across Alaska and hit a real problem. We had team members in Anchorage, Dutch Harbor, and Fairbanks. Dutch Harbor is in the Hawaii-Aleutian zone but east of the non-DST cutoff, so it observes daylight saving time. Fairbanks and Anchorage are on Alaska Time and also observe DST. So far, straightforward. Everyone is either AKDT or HAST depending on the season. The issue came up during the two-week window when the U.S. mainland had already switched to or from daylight saving time but Alaska's border communities were dealing with a different transition schedule due to the way the non-DST Aleutian segment interacted with cross-state logistics. Specifically, a supplier in the far western Aleutians who doesn't observe DST was communicating with a logistics coordinator in Anchorage who does. During the spring transition, the effective time difference between them shifted from 8 hours to 7 hours for one week, and then back to 8 hours when the rest of Alaska caught up. This caused a delivery schedule to slip by a day because the ordering system recorded the confirmation timestamp in local Aleutian time, but the fulfillment team in Anchorage read it as if it were Alaska Time. The workaround was simple in hindsight but tedious to implement. We stopped using local timestamps for any cross-zone communication. Every schedule, confirmation, and dispatch notice was recorded and communicated in UTC. This eliminated the ambiguity entirely. If you're building anything that touches multiple Alaskan time zones, do the same. Store everything in UTC, display everything in the recipient's local zone, and never let the two mix in the same data field. This usually reduces time-zone-related errors by about 90 percent and cuts troubleshooting time from hours to minutes.
Common Mistakes People Make
The biggest error is assuming all of Alaska is one zone. It isn't. The second biggest is assuming all of Alaska observes DST. It doesn't, not entirely. The third is assuming that when the rest of the U.S. switches, Alaska switches at the same moment. It does, but the effect across the state's internal zones is uneven during the transition weeks. Another frequent mistake is looking up "Alaska time" on a basic website and getting Anchorage time, then applying that to Nome or Unalaska without checking whether those places actually follow the same rules. They don't always. Unalaska (Dutch Harbor) is on Hawaii-Aleutian Time with DST. Attu is on Hawaii-Aleutian Time without DST. Fairbanks is on Alaska Time with DST. They are never all the same offset simultaneously.
What You Actually Need To Know For Everyday Use
If you're just scheduling a call with someone in Anchorage, you need to know whether it's currently standard time or daylight saving time. Check if the date falls between the second Sunday in March and the first Sunday in November. If it does, Anchorage is UTC-8. If it doesn't, Anchorage is UTC-9. That's it for Anchorage specifically. If you're dealing with anywhere else in Alaska, verify the specific location's zone and DST status before locking anything in. A quick lookup for the city or borough name will tell you whether it's AKST/AKDT or HST/HDT and whether DST applies. Don't guess. The exceptions are real and they're documented, but they're easy to miss if you're not looking for them. For anyone building software or systems that handle Alaskan timestamps, use IANA time zone identifiers. Use America/Anchorage for Anchorage and most of southern and central Alaska. Use America/Nome for the Hawaii-Aleutian zone with DST. Use Pacific/Atka for the Aleutians without DST. These identifiers encode the historical and current transition rules, so you don't have to manually update them when Congress changes the DST schedule, which has happened before and could happen again.
