What Time Zone Is Las Vegas Actually In
Las Vegas sits in the Pacific Time Zone. That means standard time is UTC-8 and during daylight saving it flips to UTC-7. The state of Nevada follows DST, so clocks go forward one hour on the second Sunday in March and back on the first Sunday in November. Nothing complicated about that part. The actual standard keeps everything on Pacific Time. The city is not on a weird offset or anything. It tracks the same schedule as Los Angeles and Seattle. If you are scheduling a call with someone in Vegas, treat it like Pacific Time. Full stop. Here is the thing most people get wrong though. Nevada as a state is not entirely on one time zone. The panhandle around West Wendover runs Mountain Time because it is closer to Utah and Denver. Elko and some rural northeastern counties also observe Mountain Time. Las Vegas itself has never been an exception. It stays Pacific.
I ran into a problem a few years back when I was setting up a distributed deployment across multiple regions. The build pipeline had a hardcoded offset for a Nevada-based server we had listed in our config. I assumed it was Pacific because Vegas is Pacific. It turned out the server was racked at a facility just outside the city limits in a zone that observes Mountain Time. My cron jobs were firing an hour early every single day. I caught it when log timestamps started drifting against our monitoring alerts. The workaround was straightforward. I stopped relying on geographic assumptions and started verifying the TZ environment variable directly on each host. Running `timedatectl` or checking `/etc/timezone` on the machine itself tells you exactly what the system thinks its zone is. It takes about two minutes and saves you from hours of debugging. Another detail that trips people up involves the IANA timezone database. You should always reference America/Los_Angeles rather than using a raw UTC offset like UTC-8. Offsets don't account for DST changes and they vary by year. The IANA zone identifier carries the full history of rule changes. If you are storing timestamps in your application, use UTC internally and convert to America/Los_Angeles only at the presentation layer. Storing local time in your database is a mistake I still see in production codebases. There is also a practical limitation worth noting. When the US Congress changes DST dates, which it occasionally proposes doing, systems that rely on the Olson database need to be updated. Old versions of the tzdata package on Linux servers will still apply the previous year's transition dates. I had a container running an outdated Alpine image once and it stayed on PST for another week after the spring shift. The fix was simply pulling the latest tzdata package and rebooting the service. For most hosted environments this happens automatically but if you manage your own infrastructure you need to make sure your image base stays current.
If you need to check what time it is in Las Vegas right now against another location, the most reliable method is using the IANA name rather than guessing offsets. Python gives you this cleanly with `zoneinfo.ZoneInfo("America/Los_Angeles")`. JavaScript uses the same identifier in `Intl.DateTimeFormat`. These approaches handle the transitions without any manual calculation on your part. The bottom line is that Las Vegas is Pacific Time, Nevada has some exceptions nearby, and treating every location as a simple offset will cost you time later. Verify the actual zone on the machine you are working with and use the proper timezone identifiers in your code.
