CST is three different time zones

The abbreviation CST is used for United States Central Standard Time, for China Standard Time and for Cuba Standard Time. Those are three different offsets, fourteen hours apart at the extremes, and nothing in the abbreviation distinguishes them.

It is not an isolated case. IST covers India, Israel and Ireland. A meeting invitation quoting an abbreviation is quoting something ambiguous, which is why every system that handles time properly uses region names instead.

What should be used instead?

A zone name from the maintained database of them — a continent and a city, like Europe/Amsterdam or America/Chicago. Those names are unambiguous and, crucially, they carry the rules rather than a fixed offset.

That distinction matters because offsets change. A zone name means "whatever the local rule says at that moment", so it stays correct across daylight saving transitions and across a government changing its mind.

The city in the name is a representative rather than a claim about importance. It exists so that the name stays stable when countries and borders do not.

Is UTC a time zone?

No. It is the reference everything else is expressed against, and no country uses it as its civil time — the ones closest to it sit at a zero offset by their own rule rather than by adopting UTC.

The practical use of that distinction is in storage. An instant stored against UTC is unambiguous forever; the same instant stored as a local time and an abbreviation may not be recoverable at all.

It is also why an offset written as +00:00 and a zone named for a European capital are not interchangeable, even during the months when they agree.

Are all offsets whole hours?

No, and the exceptions are more common than people expect.

The full range spans 26 hours, which means there are moments when three different calendar dates exist somewhere on earth at once.

Any code assuming offsets are whole hours breaks on about a fifth of the world’s population, and the 45-minute ones break code that assumed half hours were the worst case.

How often do the rules change?

Several times a year, somewhere. Governments move their offsets, adopt or abandon daylight saving, and occasionally change dates at short notice — and the database that records all this is updated whenever they do.

That is why time zone handling is a data problem rather than an arithmetic one. A system with an out-of-date copy computes confident, wrong answers for the affected regions until it is updated.

It is also why converting a future local time to an instant and storing that is risky. The rule may not be the same when the date arrives, and the timestamp article covers which of the two forms to keep.

What breaks around a transition?

The hour that does not exist and the hour that happens twice. In spring a local clock jumps forward, so a time in that gap is not a real instant; in autumn it goes back, so an hour repeats and a local time in it is ambiguous.

Anything scheduled in that window needs a decision rather than a calculation, which is the subject of its own article on recurring meetings. The short version is to avoid scheduling there.

The transitions do not happen simultaneously worldwide, so for a few weeks each year the gap between two regions is an hour different from usual. That is when a recurring cross-border meeting moves without anyone changing it.

How should a meeting be written down?

With the zone attached to the time, and preferably with a second zone alongside it. "Fifteen hundred in Amsterdam" is unambiguous; "3pm CET" is nearly so and stops being true for half the year, since the summer offset has a different abbreviation.

That seasonal switch is the reason abbreviations mislead even when they are unambiguous. A standing invitation quoting a winter abbreviation is wrong from spring to autumn, and the people who notice are the ones in a different region.

Calendar software handles all of this correctly when given a zone, which is the strongest argument for letting it own the conversion rather than writing times into the description.

Questions people ask

Why do zone names use a city? Because cities outlast the political boundaries around them, so the name stays valid when a country changes its rules or its borders.

Do all countries observe daylight saving? Fewer than half, and several have abandoned it recently. Assuming a transition exists is as wrong as assuming it does not.

What is the widest gap between two zones? Twenty-six hours, between the earliest and latest offsets in use.

Can I just store an offset? It records what the offset was, not which rules apply. For a past instant that is enough; for a future one it is not.

Why does my calendar show the wrong hour? Usually an event created with an offset rather than a zone, then read after a transition.

Which zone should a server use? UTC, always. Local time is a display concern.

Do abbreviations ever appear correctly? In writing for a known audience, yes. In data, never.

Convert against a named zone, not an abbreviation. The time zone converter works between named regions with their current rules applied, and the world clock shows several at once for finding an hour that works everywhere.