How to Stop Losing Your Mind Over Mexican Time Zones
Mexico has four official time zones, and they do not behave consistently. The country covers Eastern, Central, Pacific, and Northwest zones, but the rules for when each one switches to daylight saving time change depending on the state and the year. If you're scheduling a call with someone in Tijuana while you're in New York and assuming they're on the same clock, you will show up an hour early or late. This is not a hypothetical problem. It happens constantly in business operations that span the border. The core of the confusion starts with a 2022 policy shift. Before that year, most of Mexico observed DST, and the rules were messy but somewhat familiar to anyone who dealt with the country regularly. In 2022, the Mexican government eliminated DST for the majority of the country. States kept standard time year-round. But several border municipalities and one full state decided to keep observing DST so they would stay synchronized with their U.S. counterparts across the border. That created a situation where two cities a few miles apart could be on different clocks during part of the year. Here is the actual breakdown of how it works now. Quintana Roo stays on Eastern Standard Time all year at UTC-5. That is the only zone that never changes. Baja California, which includes Tijuana and Mexicali, follows Pacific Daylight Time during the spring and summer months and Pacific Standard Time in the winter. It matches the U.S. Pacific zone exactly. The rest of the country, which includes Mexico City, Guadalajara, Monterrey, and Cancun in most cases, runs Central Standard Time year-round at UTC-6. There is no DST switch for these areas anymore. The Pacific Time zone, used in Sinaloa, Nayarit, and parts of Michoacán, also does not observe DST under the current framework, staying at UTC-7 throughout the year.
When I was coordinating a supply chain rollout across three Mexican states last year, I built a spreadsheet that mapped each city to its time zone and flagged which ones would shift during March through November. I almost missed a detail. Los Cabos in Baja California Sur is technically in the Pacific zone, but the municipality had opted out of DST after the 2022 reform. That means during the summer, when Tijuana is on PDT and Mexico City is still on CST, Los Cabos is actually an hour ahead of Mexico City instead of being aligned with the rest of the Pacific zone. I caught it because I cross-referenced the official NOM-009-SCT2-2015 update with state-level municipal agreements instead of trusting a generic time zone chart. Those charts still show Los Cabos switching, which is wrong right now. The most practical way to handle this without going crazy is to store every schedule in UTC and let your software convert to the local zone at display time. If you are doing this manually, check the current status of the specific municipality you are dealing with, not just the state. State-level designations can be misleading because municipalities within the same state sometimes chose different options under the reform. A quick verification against the official diary published by the Secretaría de Energía takes about two minutes and prevents an hour of wasted back-and-forth on a conference call.
Why Generic Tools Get This Wrong
Most online calculators and even some operating system time zone databases still carry outdated rules from before the 2022 changes. I ran into this when I was building an automated notification system for a logistics platform. The system used a standard time zone library that assumed the entire Central zone switched twice a year. For three weeks after the policy took effect, every alert was sent an hour early to recipients in Mexico City. The fix was updating the IANA timezone database to the latest version and pinning the source of truth to the official government publication instead of letting the library auto-resolve based on historical patterns. That database update process usually takes about twenty minutes if you know where to look, and it prevents the entire class of errors that come from stale rule sets. Another issue that trips people up is the assumption that Spanish-speaking countries in the region follow similar rules. They do not. Guatemala, for example, stays on CST year-round with no DST. El Salvador does the same. Honduras, Nicaragua, and Costa Rica are all on CST with zero variation. The only country in the region that still does DST alongside Mexico's border zones is the United States and Canada. This matters because if you are building a system that serves multiple Latin American markets, you cannot batch them together and apply one set of rules. Each country needs its own configuration, and Mexico itself needs a municipality-aware configuration rather than a state-level one.
Get the Full Details
When You Should Not Rely on Automation
Time zone automation works well until it does not. The main failure point is policy changes that happen mid-year or with short notice. Mexico's 2022 reform was announced in late 2021 but took effect in April 2022, and some municipalities had grace periods to file their opt-in or opt-out decisions. Any tool that assumes static rules will break during those transition windows. If you are managing schedules that involve Mexican clients or partners, build in a manual override and a verification step during the first two weeks after any announced policy change. Do not assume the database will update fast enough. There is also a practical limitation with mobile devices. If you travel to Mexico and your phone auto-joins the local time zone, it may switch you to the wrong one depending on your carrier's default behavior and whether you are near a border. I have seen this happen at the Nogales crossing, where a phone connected to the U.S. cellular network while physically in Mexico and stayed on Mountain Time instead of shifting to Central. The workaround is simple: set your phone to manual time zone selection and pick the correct zone by city name rather than letting it auto-detect. It adds ten seconds to the setup and saves you from showing up to a meeting at the wrong hour.
A Practical Reference You Can Actually Use
Quintana Roo: UTC-5 always. No exceptions. Cancun, Playa del Carmen, and Chetumal are all on this zone. Baja California: UTC-7 in winter, UTC-8 in summer. Matches the U.S. Pacific zone. Tijuana, Mexicali, Ensenada. Mexico City, Guadalajara, Monterrey, Puebla, Querétaro: UTC-6 always. The majority of the population lives in these zones and none of them switch anymore.
Baja California Sur, including Los Cabos: UTC-7 always. This is the tricky one because it is geographically in the Pacific region but does not follow Pacific DST rules like Tijuana does. Sinaloa, Nayarit, parts of Michoacán: UTC-7 always. These areas dropped DST under the reform. Chihuahua, Ciudad Juárez: UTC-6 in winter, UTC-5 in summer. These border cities match the U.S. Mountain time zone because they opted to keep DST synchronization.
If you need a single reliable source for the current status, the official government gaceta published by the Secretaría de Energía is the authoritative reference. It is not the prettiest document, and the Spanish-only format makes it harder to parse quickly, but it is the only place where changes are announced before they appear in any database. I keep a bookmarked copy and check it once a year during the typical March adjustment window. That habit alone has prevented more scheduling errors than any tool I have tried.
