What Is UTC?

Why UTC exists

Before globally synchronized networks existed, local time was tied much more closely to the sun and to regional observatories. That worked poorly once railways, telegraphs, aviation, software systems, and financial markets needed a shared reference. UTC exists to provide a stable standard that every local clock can relate back to.

The important practical point is that UTC does not care where you live. Local zones such as Eastern Time or Central European Time are applied on top of UTC as offset rules. That makes UTC the safest way to record an event when you need the meaning to stay constant across borders.

UTC is a standard, not a city clock

People often talk about UTC as if it were just another time zone like London or Berlin. In practice, it serves a different role. UTC is the international reference standard, while local zones are social and legal conventions built around it.

That distinction matters in software and documentation. A log entry stored as UTC can later be displayed in any local zone without losing its original meaning. A log entry stored as a naive local time can become ambiguous the moment daylight saving rules or deployment regions change.

When to use UTC

Use UTC when storing timestamps, exchanging data between services, documenting incident times, or coordinating work between regions. Use local civil time when you are speaking to people about their day: office hours, appointments, flights, and local deadlines.

A good rule is simple. Store and compare in UTC. Display in local time. That approach removes most of the avoidable date-and-time bugs that show up in distributed systems.