For most of history, every town kept its own time, set by the local noon. Nobody minded, because nothing moved fast enough for the differences to matter. Railways and telegraphs broke that arrangement: a train schedule is nonsense when every station’s clock disagrees by minutes. The fix — standard time zones anchored to a single reference meridian — is one of the great quiet infrastructures of modern life, and your phone negotiates it constantly without telling you.
The reference point runs through Greenwich in London, a legacy of the 1884 International Meridian Conference that chose the Greenwich meridian as longitude zero.
GMT versus UTC
Greenwich Mean Time originally meant time reckoned from the sun’s position over Greenwich — an astronomical definition tied to the Earth’s rotation. Coordinated Universal Time, UTC, is its modern successor, kept by a worldwide ensemble of atomic clocks and adjusted occasionally with leap seconds to stay close to the planet’s actual spin. For everyday purposes GMT and UTC are interchangeable, but technical fields use UTC exclusively, because atomic time is steady while the Earth’s rotation wobbles slightly. When aviation people say “Zulu time”, they mean UTC as well.
Zones, offsets, and the ideal versus the real
In theory the world divides into 24 zones of 15 degrees of longitude each, one hour apart. In practice, politics redraws the map. China spans about five theoretical zones but uses one. India sits at UTC+5:30, and Nepal at UTC+5:45. Some Pacific nations have hopped across the date line for trade reasons, and daylight saving time shifts many countries by an hour for part of the year on schedules that differ by hemisphere and by country. The full list of named zones maintained for computing purposes runs into the hundreds, precisely because offsets alone cannot capture all the history.
Why servers live on UTC
Anyone who has debugged a scheduling bug learns the golden rule: store timestamps in UTC and convert to local time only for display. A time like “1:30 a.m. on the night daylight saving ends” occurs twice in local time but only once in UTC. Aviation, shipping, astronomy, and global finance all operate internally on UTC for the same reason — it is the one clock that never jumps, repeats, or skips.
When you coordinate across borders, share the time in UTC alongside the local time, and you will sidestep nearly every classic scheduling disaster in one move.
Loading comments…