Who Decides What Time It Is?

A video call is set for 9:00 in the morning in New York, 2:00 in the afternoon in London and 10:00 at night in Tokyo. Everyone treats those numbers as plain facts, as fixed as the weather. Yet not one of them was handed down by nature. Nature only supplies the turning Earth and the arrival of daylight. The precise number your clock displays, and the moment it agrees to call "nine", is the output of a long chain of astronomy, engineering, law and international negotiation.

Clock time, in other words, is neither purely natural nor purely arbitrary. It is a system, and like any system it has authors, rules and seams. Pull on the thread of a simple meeting invite and you find atomic clocks in national laboratories, an international bureau in Paris, astronomers measuring the wobble of the planet, and governments quietly deciding what the law will call noon.

The short answer

No single person or organisation decides all of the world's time. Modern time is produced by overlapping systems that hand off to one another. National laboratories run atomic clocks. The Bureau International des Poids et Mesures (BIPM) in Paris combines those clocks into a single stable reference. The International Earth Rotation and Reference Systems Service (IERS) measures how the planet is actually turning. From these comes Coordinated Universal Time, the global reference. Then national governments decide which offset from that reference their country will use, and whether to shift the clocks in summer. Finally, software distributes those rules to every phone and server.¹

The crucial distinction, and the one most people miss, is that UTC is a technical standard, while the time on your wall is a legal and political choice layered on top of it.

The Sun determines day and night. Governments and international institutions determine what the clock says.

Noon was once local

For most of history, noon was an astronomical event you could see. Local solar noon is simply the moment the Sun reaches its highest point in your sky, and it happens at a different instant for every meridian of longitude. A town a little to your east sees the Sun cross first, so its noon arrives earlier than yours.

The arithmetic is clean, if idealised. The Earth turns roughly 360 degrees in about 24 hours, which works out to about 15 degrees of longitude per hour, or about four minutes per degree. Two towns 30 kilometres apart on an east-west line keep local times a minute or two apart. This is a simplification, because the Earth's rotation and the Sun's apparent motion are not perfectly uniform through the year, but it captures the shape of the thing. And for centuries it did not matter. When the fastest news travelled at the speed of a horse, every town keeping its own sun-time was perfectly workable.

Railways broke local time

The arrangement collapsed the moment things began to move fast. When railways and the telegraph arrived in the nineteenth century, a country full of towns each keeping its own solar time became a scheduling nightmare. A timetable printed in one town's time meant something different by the time the train reached the next. Connections were missed, and worse, trains running on the same line to differently-set clocks were a genuine safety hazard. Signalling depends on everyone agreeing precisely when.

The response, worked out over decades and in different countries at different times, was standard time: agreeing that a whole region would ignore the Sun's local position and keep one shared clock. British railways adopted a single standard, often called railway time, and it gradually became the country's legal time. In North America, the railways coordinated a set of standard zones in 1883 to tame a chaos of local times. It is tempting to credit one nation or one company with inventing standard time for the world, but the truth is messier and more interesting: many jurisdictions arrived at the same idea because the same technology forced the same problem on all of them.

How the world acquired time zones

The idea that tidied the map was to slice the globe into hourly bands, each 15 degrees of longitude wide, all offset from a common reference meridian by a whole number of hours. In an idealised world, time zones would be neat vertical stripes. The real map is nothing like that.

Actual civil time zones bulge, jog and split, because they follow human boundaries rather than lines of longitude. Borders keep a country on one clock. Administrative convenience keeps a province aligned with its capital. Trade pulls a territory toward the time of its main partner. Colonial history, regional identity and simple daylight preference all leave their marks. The zones are less a map of the Sun than a map of politics.

Time zones are political geography

Once you see zones as policy, the odd cases stop being trivia and start being evidence. China spans a physical width of five solar hours yet runs on a single national clock, UTC+8, a deliberate choice for unity. India, similarly vast, uses one offset of UTC+5:30 rather than splitting into two.² Russia, by contrast, stretches its civil time across many zones. Some places sit on half-hour offsets, and a few on quarter-hour ones: Nepal keeps UTC+5:45, distinct from India by fifteen minutes, and the Chatham Islands run at UTC+12:45.²

Most telling are the deliberate jumps. In December 2011, Samoa and Tokelau moved from the eastern side of the International Date Line to the western side to align their working week with Australia and New Zealand, their main trading partners. They simply deleted 30 December 2011 from the calendar; it never happened there.³ No astronomy changed. A government changed the rule, and a day vanished.

What UTC actually is

At the centre of the whole arrangement sits Coordinated Universal Time, and it is worth being precise about what it is, because it is routinely misdescribed. UTC is built from two different kinds of time.

International Atomic Time (TAI) is a supremely stable timescale calculated by combining hundreds of atomic clocks in laboratories around the world. It does not care about the Earth at all; it just counts seconds with extraordinary regularity. Universal Time (UT1) is the opposite: a measure tied to the Earth's actual rotation angle, which drifts and wobbles. UTC is the diplomat between them. It ticks at the flawless atomic rate of TAI, but it is nudged to stay close to UT1 so that the clock never wanders away from the Sun. As of 2026, UTC runs exactly 37 seconds behind TAI, the accumulated total of the adjustments made since 1972.⁴

It is a common shorthand to say UTC is just Greenwich Mean Time, but that is not quite right. GMT survives as a time-zone label and a historical idea rooted in the Greenwich meridian; UTC is the modern technical standard defined by atomic clocks. They usually agree to the ordinary eye, but they are not the same kind of thing. UTC also has no capital city and no summer-time rule of its own. It is a reference, not a place.

Who maintains the world's time?

There is no single world clock, and no one institution "sets" the time. Instead there is a chain of responsibility, and each link does one job well.

National metrology institutes and observatories run the atomic clocks. The BIPM gathers their data and computes the weighted average that becomes TAI, and from it UTC.¹ The IERS watches the planet, measuring UT1 and deciding when the gap between atomic time and Earth time needs correcting.⁵ The International Telecommunication Union has long governed how UTC is defined and broadcast for radio and telecommunications.⁶ Governments then choose their legal offset and daylight rules. And a quiet but essential last link, the maintainers of the IANA Time Zone Database, encode all of those rules so software can apply them.⁷ The clock on your phone is the end of a relay that starts with atoms and ends with law.

Why atomic clocks matter

All of this rests on a level of precision the human body cannot sense and daily life never used to need. An atomic clock does not swing a pendulum or turn a gear. It counts the astonishingly regular oscillations associated with a transition in an atom, most famously caesium, and that regularity is what makes the modern second a physical constant rather than an astronomical guess.

The reason this precision leaked out of the laboratory and into everything is that a surprising amount of infrastructure now runs on shared time rather than shared space. Satellite navigation is really a timing system. Telecommunications networks synchronise to it. Power grids timestamp measurements across the country to it. Financial markets timestamp trades against it, the internet leans on it, and data centres and distributed computers coordinate through it. As with earlier UnderStructures pieces, the flashy use is not where the deep dependence lies. Precise time is the hidden utility. And no serious system trusts a single clock; resilience means many clocks, cross-checked.

Earth is not a perfect clock

Here is the wrinkle that keeps timekeepers employed: the Earth is a wobbly, unreliable clock. Its rotation speeds up and slows down under the sloshing of the oceans and atmosphere, the pull of the Moon and Sun, and the slow redistribution of mass deep inside the planet. Over the long run, tides gradually brake the spin. Over the short run, it jitters unpredictably.

Atomic time, by contrast, is almost perfectly uniform. So the two inevitably drift apart: the flawless atomic second on one side, the imperfect turning Earth on the other. Curiously, in recent years the planet has been spinning slightly faster than the atomic standard, setting records for the shortest days measured in the atomic era, including new record-short days in 2024 and 2025.⁵ For most of the atomic era the Earth ran slow; now it is running a touch fast, which flips a long-standing assumption.

Why leap seconds exist, and why they are being retired

To stop UTC and the Earth from drifting apart, the system has, since 1972, occasionally inserted a leap second: an extra second added to UTC to keep it within 0.9 seconds of the Earth's rotational time.⁴ A minute with a leap second in it runs from 58 to 59 to 60 to 00. Harmless in principle, and a nightmare in practice for anything that assumes a minute always has 60 seconds. Distributed computer systems, telecoms, financial markets, navigation, databases and operating systems have all been tripped up by leap seconds. Some large operators quietly "smear" the extra second across a day so that no single instant breaks, a pragmatic dodge rather than a standard.

The system is now being wound down. In November 2022, the General Conference on Weights and Measures adopted Resolution 4, agreeing to stop adding leap seconds by widening the tolerance between UTC and Earth-rotation time, with the change to take effect by or before 2035.⁸ The plan is to let the two drift by far more than a second, perhaps a minute over a century, before any correction. As this article is written in 2026, the details are still being finalised, with the next General Conference expected to settle the implementation.⁸ There is a further twist: because the Earth has recently been running fast, timekeepers are now seriously discussing the once-unthinkable prospect of a negative leap second, removing a second rather than adding one, an event that has never happened and that software has never been tested against.⁵ The honest summary is that the existing rule is agreed to be ending, the replacement is agreed in principle but not yet in every detail, and an unprecedented downward adjustment is now a live possibility.

The International Date Line is a political convenience

If you walk far enough around the world, the calendar date has to change somewhere, or you would arrive home a day out of step with everyone else. That "somewhere" is the International Date Line, running broadly down the meridian opposite Greenwich, out in the Pacific. But it is not a straight line and it is not natural. It zigzags to keep island nations whole and on the date they prefer, and as Samoa showed, governments can choose which side to sit on. Cross it going west and you jump a day forward; cross it going east and you live the same date twice.

Why some offsets are 30 or 45 minutes

The assumption that every zone differs from its neighbour by a whole hour is simply wrong. Fractional offsets exist because clock time is negotiated, not gridded. India and Sri Lanka sit at UTC+5:30, a half-hour compromise across a wide country. Newfoundland keeps UTC-3:30, half an hour off its mainland neighbours. And a rare few use quarter-hour offsets, Nepal at UTC+5:45 and the Chatham Islands at UTC+12:45, each a small assertion of local identity that no line of longitude would ever have produced.²

Daylight saving does not create daylight

Daylight-saving time is the most personal seam in the system, and the most misunderstood. Moving the clocks does not add a single minute of daylight; the Sun is entirely indifferent. It simply relabels the hours, shifting human activity earlier relative to sunrise so that more waking time falls in the light. Whether a place adopts it, abolishes it or never bothered depends on latitude, energy and transport policy, business coordination, health research and public mood. Places near the equator gain little and often skip it; Iran abolished it outright in 2022.²

The changeover creates two genuinely strange moments. In the spring shift, the clock jumps forward and a local hour simply does not exist; ask for 2:30 that morning and there is no such time. In the autumn shift, the clock falls back and a local hour happens twice; 1:30 that morning occurs, then occurs again. These are not curiosities. They are the source of real bugs and disputes, and they are why a bare local time can be genuinely undefined.

What happens when a government changes time

Because civil time is law, a government can rewrite it. It can change its offset, alter or abolish daylight saving, move its transition dates, or hop across the date line. Each of those is a stroke of legislation, and each ripples outward. Transport timetables must be rebuilt. Financial systems and contractual deadlines shift. Software time-zone databases need urgent updates. International meetings quietly move. Schools, broadcasters and religious schedules adjust. What does not change is the astronomy: the Sun still rises when it always would. Samoa's vanished day and Iran's abolished summer time are the same lesson in two forms. Government power over the clock is real, and it stops exactly at the edge of the sky.

The hidden infrastructure of software time

Almost none of this would work at scale without a piece of infrastructure most people have never heard of: the IANA Time Zone Database, usually called tzdata. It is the world's shared, constantly updated record of what every place's clock has done and will do, and software everywhere depends on it.⁷

The reason a plain offset is not enough is that time zones have history and rules, not just a number. Storing "UTC+1" tells you nothing about when summer time starts, whether the rule changed last year, or what happens during a transition. A place-based identifier such as Europe/Paris carries all of that: past changes, daylight rules, and scheduled future reforms. Ask a system for a moment in Europe/Paris and it can answer correctly across decades of political edits; ask it for UTC+1 and it can only ever guess. Different languages and databases handle this with varying care, which is precisely why time bugs are so stubborn.

Why timestamps become ambiguous

Put the seams together and you reach an uncomfortable truth: a date and a clock time do not always identify a single moment. "1:30 a.m." on the night the clocks go back happens twice, an hour apart, and nothing in those four digits tells you which. To pin down one true instant, a timestamp may need the date, the local time, the time-zone identifier or offset, the legal rules in force, and sometimes an explicit UTC equivalent. This is not pedantry. It decides which of two trades came first, when a contract truly expired, whether a security log is trustworthy, and which of two identical-looking records is the real one. In law and in engineering, an incomplete timestamp is a latent dispute.

What people usually get wrong

The misconceptions cluster tightly. That zones follow longitude; they follow borders. That every zone differs by an hour; some differ by 30 or 45 minutes. That UTC is just London time, or that GMT and UTC are interchangeable; UTC is an atomic standard, GMT a time-zone label. That daylight saving makes more daylight; it only moves the labels. That the date line is fixed by nature; it is drawn by governments. That every civil day has 24 hours; leap seconds and daylight transitions say otherwise. That a date and time always name one instant; sometimes they name two, or none. That computers just understand local time; they need tzdata and still get it wrong. That one body controls all time; it is a relay of many. That atomic and Earth time are the same; they drift. And that governments cannot change legal time; they do it routinely.

Why it matters

Time coordination is one of those systems that is invisible until it fails, and then it fails everywhere at once. Aviation, shipping and railways run on shared schedules. Global markets settle on shared timestamps. Legal deadlines, telecommunications, power systems, satellite navigation, cybersecurity logs, scientific collaboration, cloud computing, emergency response and diplomacy all assume that everyone means the same thing by a given moment. When a country changes its clocks, or a leap second lands, or a timestamp is ambiguous, the cost is not philosophical. It is missed connections, mispriced trades, broken logs and contested deadlines. Time is not a number on a screen. It is shared infrastructure, quietly maintained.

The bottom line

Modern time begins with nature but does not end there. The Earth turns, atoms oscillate, laboratories compare clocks, international institutions coordinate the standard, governments draw the boundaries, and software distributes the result. The time on your phone looks like a simple fact only because an enormous system has already agreed what that fact should mean.

The Sun gives us days. Institutions decide what time they begin.