Tucson Arizona Time Zone All You Need To Know Mst Daylight Saving And Why It Never Changes

The Time Zone Situation in Southern Arizona

Arizona sits entirely in the Mountain Time Zone, but most of the state doesn't observe Daylight Saving Time. That leaves a weird strip of the country stuck on UTC-7 year-round while everywhere else around it shifts between UTC-7 and UTC-8 depending on the calendar. The exception is the Navajo Nation, which does go with the flow and switches twice a year. If you're trying to schedule a call with someone in Phoenix during the summer, you need to pay attention or you'll be twelve minutes early. Tucson follows Mountain Standard Time all year. That's UTC-7, the same offset as Phoenix and the rest of non-DST Arizona. The reason dates back to 1968 when the state legislature passed a permanent exemption from the Uniform Time Act. They did it because saving daylight in summer is mostly pointless when it's one hundred ten degrees outside and everyone stays indoors anyway. The energy savings argument that drove DST adoption nationally just doesn't apply here. I've lost count of the number of times people text me saying "we're five minutes late" to a video call, and then I realize they're on Pacific Daylight Time thinking we're three hours apart when we're actually only two. The practical reality is that Tucson runs on MST constantly. No spring forward, no fall back. When the rest of the country shifts, the time gap between Tucson and places like Los Angeles, Denver, or New York changes seasonally. In winter, Tucson and LA are both on standard time so they share Mountain Standard and Pacific Standard offsets, making them two hours apart. In summer, LA moves to PDT at UTC-7 while Tucson stays at UTC-7, so they're effectively on the same clock. Denver goes to MDT at UTC-6 in summer, which means Tucson falls one hour behind it instead of being two hours behind like it is in winter. This flips the usual assumption that mountain time is always ahead of pacific time by a fixed amount.

Here's the part nobody warns you about until it bites you. Most scheduling tools and calendar apps default to detecting DST based on your operating system's timezone database. If you set your computer to "Mountain Time" without specifying Arizona, it will automatically shift twice a year. I ran into this directly when building a deployment pipeline for a client who had servers in Tucson and a monitoring dashboard in Dallas. The alerting system was pulling time from the server's locale setting, which was configured as America/Denver instead of America/Phoenix. For six months everything looked fine because both locations were on Mountain Standard Time during winter. Then March came, Denver jumped ahead, and the log timestamps showed events happening before they actually occurred. The fix was straightforward — change the timezone identifier to America/Phoenix in the container config and rebuild — but catching it required comparing actual event sequences against ground truth, not just trusting the displayed hours. Another edge case that catches people off guard: when Arizona is on the same clock as Pacific Daylight Time in summer, it's also the same as Eastern Standard Time. That means a noon meeting in Tucson is 10 AM PDT, 9 AM EST, and 7 AM PST. If you're coordinating across those zones without writing down the offsets, you will make mistakes. I recommend just converting everything to UTC in your head and working from there. It takes a week to get used to but eliminates the seasonal confusion entirely. The down side of Arizona's position is that it creates fragmentation in any system that assumes uniform DST behavior across a time zone region. Database queries that group by date across state lines will produce incorrect results if the timezone conversion logic doesn't account for the Arizona exception. Cron jobs scheduled with default settings on cloud platforms sometimes fail in Arizona because the platform's scheduler assumes standard DST rules. You have to explicitly set the timezone to America/Phoenix in your infrastructure configs rather than relying on generic "MT" or "MST" labels. This is true for AWS, GCP, and Azure — all of them treat Mountain Time as a single zone with DST by default unless you override it.

If you need to communicate this to other people, just say Mountain Standard Time and add that Arizona doesn't change. That covers it. Most confusion comes from people expecting the clock to shift in spring or fall and showing up an hour early or late to appointments. There's no official resource that explains this clearly to the general public, which is why you end up reading forum posts like this one at midnight trying to figure out why your calendar invite is wrong.