What Is The Oregon Time Zone

Oregon's Time Zone Situation

What Is The Oregon Time Zone -- honestly, it's a mess if you live here. The short version is that most of the state runs Pacific Time, but there are pockets in the northeast that stay on Mountain Time. It's not a clean boundary either. If you're driving from Burns to Pendleton, you cross into a different time zone roughly halfway there, and the signs are terrible about telling you. Here's how it breaks down in practice. Lane County, Multnomah County, Jackson County -- they're all Pacific Time. UTC-8 standard, UTC-7 during daylight saving. That covers basically anywhere west of the Cascade crest and anywhere south of about Union in Union County. Portland sits in Pacific Time, obviously. Eugene too. Even places like Medford and Ashland follow the same rules. The exceptions are in Malheur County, which covers the area around Ontario and Burns. They switched from Pacific to Mountain Time back in 2006. There's also a chunk of Harney County that went along with it. The reasoning was always about economic alignment with Eastern Oregon businesses and Idaho rather than anything to do with actual solar time or fairness. It's a business decision dressed up as convenience.

I ran into this when I was setting up a scheduling system for a client who had contractors scattered across the state. One of them was in Vale, which is technically Malheur County but functionally part of the Boise commuting zone. The other was in Klamath Falls, which is Pacific Time despite being only about an hour and twenty minutes away geographically. The scheduling app kept double-booking them because it didn't account for the county-line boundary shifting the offset. I ended up writing a small script that checked the actual latitude and longitude coordinates against a shapefile of county boundaries and then applied the correct offset. Took me about four hours to build and maybe thirty minutes to test. It's saved me countless headaches since then. The DST angle is another thing people get wrong. Oregon adopted daylight saving time statewide in 1966 when the Uniform Time Act kicked in, but Malheur and Harney counties opted out when they switched to Mountain Time. So yes, you can have two towns in the same county operating under different clock rules depending on whether they're west or east of the county line. It sounds insane until you've tried to coordinate a phone call between two people fifty miles apart and realized one is on PDT while the other is just on PST.

The Boundary Issue

The transition line isn't obvious. If you look at a map, the border between Pacific and Mountain in Oregon cuts diagonally across Malheur County from the Idaho line down toward the Malheur River. Cities like Ontario and Vale are on Mountain. Places like Pendleton, which sits just over the county line, are on Pacific. The driving distance between them is maybe twenty minutes. The clock difference is one hour. There's no official signage marking where the change happens on the highway. I learned this the hard way once when I was driving back from Portland to La Grande and decided to stop in Pendleton for lunch. My phone had already auto-switched to Mountain time, but everyone in Pendleton was still operating on Pacific. I showed up to a meeting twenty minutes early because I set my alarm based on the phone's automatic update. Nobody else was there yet. Embarrassing in a client context.

Why It Matters Practically

If you're building software, scheduling tools, or anything that deals with dates and times in Oregon, you can't just assume the whole state is Pacific. There are libraries that handle this -- moment-timezone, timezonefinder, whatever you're using -- but you need to feed it the right data. The IANA timezone database has "America/Boise" for the Mountain portion and "America/Los_Angeles" for the Pacific portion. Using a generic "America/Denver" won't work because Boise handles the DST rules differently for that corner of Oregon. I've seen people try to code around this by just subtracting an hour for eastern Oregon based on longitude, and it works until someone moves and the policy changes. Oregon has debated switching the eastern counties back to Pacific Time multiple times over the years. Nothing's stuck, but the possibility exists. Hardcoding offsets is a bad idea. Use the proper timezone identifiers and let the OS handle transitions. The takeaway is straightforward but annoying: Oregon isn't one time zone. It's two, split along county lines that don't align with anything intuitive. If you're dealing with scheduling, logistics, or anything time-sensitive across the state, verify the exact location against a county boundary map before you assign a timezone. That's it. No magic solution, just don't trust your assumptions.