Why Your Calendar Shows the Wrong Meeting Time After Crossing Time Zones

The real reason meetings show up at the wrong hour

Every calendar event is stored on the server (Google's or Microsoft's) as a UTC timestamp plus a timezone identifier, like America/New_York or Europe/Lisbon. Your app then does math at display time: it takes that UTC timestamp and re-renders it in whatever timezone your device currently reports itself as being in. When you land in a new country, three separate systems have to agree on what that timezone is: your phone's OS-level timezone (usually auto-detected from cell tower or GPS), your laptop's OS timezone (often set manually or stuck on a stale Wi-Fi-based guess), and your calendar app's own internal timezone setting, which on some Outlook and Google Calendar installs is a completely separate preference from the device clock.

When any one of those three disagrees with the other two, you get a calendar that looks correct on your phone and wrong on your laptop, or vice versa — which is exactly the symptom most people report and the reason it feels so confusing. It's not memory corruption or a sync failure; it's three clocks with three different opinions, and the app is faithfully rendering whichever opinion it was told to trust.

Why timezone auto-detection fails on planes, in roaming, and on VPN

Phones typically auto-detect timezone from a combination of cell network signaling and GPS. That works fine on a normal SIM, but it breaks down in a few predictable situations: you land and haven't yet connected to a local carrier so the phone is still reporting your home network's timezone; you're on an eSIM or roaming SIM that's technically registered to a different regulatory region than where you're standing; or you're running a VPN for remote work that some apps mistakenly use as a location signal instead of the device's actual GPS. Laptops are worse — most laptop OSes only auto-update timezone if you explicitly enable location-based time, and a lot of remote workers have that turned off because it drains battery or because IT locked it down years ago at a previous job.

The practical result: your phone corrects itself within an hour of landing, your laptop sits on the old timezone for days until you manually fix it, and every meeting you view on the laptop is off by however many hours separate the two zones. This is the single most common calendar-timezone ticket we see from clients who just crossed 6+ time zones.

When the meeting invite itself is stamped with the wrong zone

A second, separate failure mode has nothing to do with your device: it's about how the invite was created. If a colleague in London sends you a Google Calendar invite while their laptop is set to Europe/London, and you accept it while your calendar app is set to Asia/Bangkok, Google's servers do the timezone conversion once, at acceptance time, and lock it in. If that colleague's laptop timezone was itself wrong when they hit "send" — a common issue for teams with people constantly moving between countries — the invite carries the wrong base UTC time forward permanently, and no setting on your end will fix it. You have to ask the sender to check what timezone their calendar app was actually reporting when they created the event, then have them delete and resend it, or manually adjust the specific event's time on your end (which desyncs it from their copy and can cause a second round of confusion).

This is worth diagnosing separately from device-level timezone bugs because the fix is completely different — no amount of correcting your own phone or laptop settings will move an invite that was created wrong at the source.

Recurring meetings that drift after one region changes for DST and another doesn't

Daylight Saving Time is the quiet killer of recurring meetings for anyone working across regions. The US and Canada typically shift DST on different calendar dates than the EU, and countries like most of Asia, most of Africa, and all of mainland China, India, and Japan don't observe DST at all. If you set up a weekly recurring meeting anchored to "9am my time" while your time is US Eastern, and the US springs forward a week before or after the EU does (this happens most years), every attendee whose calendar is anchored to a fixed local time in a non-DST-observing country will suddenly see the meeting shift by an hour for that transition week, then shift back — while US and EU attendees see no change at all. Nobody gets an error. The meeting just silently moves for a subset of people, which is how you end up with half the team on the call and half missing it.

The only real prevention is anchoring recurring meetings to UTC or to a specific named timezone (not "local time") when you create them, and double-checking the event during the two- to three-week windows each year when different regions' DST rules are out of sync with each other.

Google Calendar vs Outlook: where the settings actually live

Google Calendar's timezone behavior is controlled almost entirely by a single web setting under Settings > General > Time zone, plus a "secondary time zone" toggle a lot of frequent travelers turn on by accident and then forget is there, which shows two time columns and confuses people into thinking the app is broken. Outlook is messier: desktop Outlook reads the Windows OS timezone by default unless you've explicitly set a calendar-specific timezone in Outlook's own Options > Calendar menu, and Outlook on the web (which syncs with Microsoft 365) has yet another independent timezone setting that can silently diverge from the desktop app if you use both. Outlook mobile adds a third layer with its own auto-detect toggle. This is why "just check your settings" advice from generic troubleshooting guides so often fails — there are genuinely three to four different places timezone lives depending on which combination of Outlook clients you use, and they don't always sync with each other automatically.

If your work depends on accurate scheduling across time zones, our timezone support service is built specifically to audit all the layers on a given account rather than guessing at one setting and hoping.

Get your calendar back to showing the right time, today