The tz Database Explained: IANA Time Zone Data (2026f)
The tz database (also called tzdata, the IANA time zone database or the Olson database) is the public record of every region’s clock rules, past and present, that phones, computers and programming languages use to turn UTC into local time. It is where names like America/New_York, Europe/London and Asia/Kolkata come from. IANA describes it as code and data that “represent the history of local time for many representative locations worldwide” (IANA). The current release is 2026f, published on October 27, 2026; it contains 345 zones and 253 alias links, and it has had six releases in 2026 alone, five of them because governments in Canada, Morocco and Cuba changed their rules. This guide explains what is in it, how the names work, who maintains it, how a change reaches your device, and how to use it in code. Facts are as of November 2026.
Key facts (as of November 2026)
- Version 2026f (October 27, 2026) defines 345 zones and 253 links in its compact tzdata.zi file (our count).
- zone1970.tab lists 312 zones for regions whose clocks agree since 1970; zone.tab has 418 rows; iso3166.tab has 249 country codes (our count, tzdata 2026f).
- The NEWS file lists 258 release entries from 1997a (January 21, 1997) to 2026f, counting separate code-only and data-only releases; the busiest year was 2009, with 21 (our count).
- Maintenance follows RFC 6557 (BCP 175): a TZ Coordinator, an IANA Designated Expert chosen by the IESG, decides changes with the public tz mailing list.
- The project itself says: “The tz database is not authoritative, and it surely has errors.” Governments set time; tz records it (theory.html).
What is in the database
A release is a set of plain-text source files plus some tables. The ones most people meet are these (counts from the tzdata 2026f package, made with a script and re-checked with Python’s zoneinfo, which found all 345 zone names and 253 link names among the 598 keys it can load):
| File | What it holds | Size in 2026f |
|---|---|---|
| tzdata.zi (compiled from africa, asia, europe, northamerica, and others) | Zone lines (offsets and their history), Rule lines (daylight saving rules), Link lines (aliases) | 345 zones, 253 links, 1974 rules |
| zone1970.tab | One row per zone used for a region whose clocks have agreed since 1970, with country codes and coordinates | 312 rows |
| zone.tab | The older table: one row per zone per country code | 418 rows |
| iso3166.tab | Country and territory names used by the tables | 249 codes |
| backzone | Older data for zones that were merged; theory.html warns it “is less reliable” | not in the default build |
| NEWS | Release notes for every version | entries back to 1997a |
The source files are heavily commented. Those comments are where the database explains each decision, often quoting newspapers, laws and emails from residents; our US time zones by state guide and many of our country guides quote them.
How the names work
The project’s design notes say: “Names normally have the format AREA/LOCATION, where AREA is a continent or ocean,” and they advise: “Use cities or small islands, not countries or regions” (tz theory.html). A city is chosen because countries split and merge, and their names change, while a city’s clock history is easier to pin down. That is why the US Mountain zone is America/Denver, not “US/Mountain”.
Old names survive as links: “The database defines each timezone name to be a zone, or a link to a zone” (same source). In 2026f, US/Michigan is a link to America/Detroit, and Asia/Calcutta to Asia/Kolkata. A new zone is added only when a region’s clocks have differed from every existing zone since 1970, which is why the database has zones like America/North_Dakota/Beulah for a single county that moved in 2010. Fixed-offset names exist too, but with a trap: in Etc/GMT-3 the sign is reversed, and that zone is three hours ahead of UTC. The “etcetera” file explains that “POSIX has positive signs west of Greenwich” (tz “etcetera”).
Who maintains it
RFC 6557, “Procedures for Maintaining the Time Zone Database” (BCP 175, February 2012), moved the project under IANA. It defines a TZ Coordinator, “an IANA Designated Expert”, chosen by the IESG, who makes updates “in consultation with the TZ mailing list”. The list is “the forum where matters relating to the TZ database and supporting code are discussed” and is used to “announce releases”. Anyone can propose a change; corrections often come from residents, journalists and engineers who spot a new law.
The database does not decide anything. Its documentation warns that “Any attempt to pass the tz database off as the definition of time should be unacceptable to anybody who cares about the facts” (theory.html). Governments make the rules; tz writes them down.
The six releases of 2026
Releases come when needed: “There is no fixed schedule for tzdb releases,” though “typically a release occurs every few months” (tz-link.html). 2026 was busy because of short-notice government decisions:
| Release | Date | First headline in the NEWS file |
|---|---|---|
| 2026a | Mar 1, 2026 | Moldova has used EU transition times since 2022. |
| 2026b | Apr 22, 2026 | British Columbia moved to permanent -07 on 2026-03-09. |
| 2026c | Jul 8, 2026 | Alberta moved to permanent -06 on 2026-06-18. |
| 2026d | Sep 11, 2026 | Canada’s Northwest Territories moved to permanent -06 on 2026-08-21. |
| 2026e | Sep 29, 2026 | Manitoba moves to permanent -05 on 2026-10-31. |
| 2026f | Oct 27, 2026 | Cuba will not fall back 2026-11-01; stays on -04 through 2027-11-07. |
Release counts over the last decade, from the NEWS file:
| Year | 2016 | 2017 | 2018 | 2019 | 2020 | 2021 | 2022 | 2023 | 2024 | 2025 | 2026 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Releases | 10 | 3 | 9 | 3 | 6 | 5 | 7 | 4 | 2 | 3 | 6 |
Western Canada drove four of the six 2026 releases: British Columbia, Alberta, the Northwest Territories and Manitoba all stopped changing their clocks (our Canada 2026 guide covers what that means). Morocco moved to permanent UTC+0, and Cuba cancelled its November fall-back (see Cuba’s 2026 time change).
How a change reaches your phone
A new rule takes three hops: the government announces it, tz publishes a release, and each operating system or software vendor ships an update. The project notes that “Changes to the tz code and data are often propagated to clients via operating system updates” and that “Many downstream timezone data distributors wait for a tzdb release before they produce an update” (tz-link.html). That is why it asks governments to act early: “any rule change should be promulgated at least a year before it affects how clocks operate.”
2026 showed what happens when that is not possible. In release 2026e, tz modelled Manitoba’s change “on 2026-11-01 at 02:00” rather than its legal date, as a “temporary hack” that “works around a limitation in Unicode CLDR 48.2.2 (2026-09-21) and ICU 78.3”, the libraries many apps use to display time zone names (tz NEWS). On November 8, 2026, an unreleased change in the development repository removed that workaround, replacing the delayed transitions with the legal dates “in America/Vancouver on 03-09, in America/Edmonton on 06-18, in America/Inuvik on 08-21, and in America/Winnipeg on 10-31”, noting it “does not affect UT offsets” (tz commit eb40bc6). Clock times for now and the future are the same either way; only labels during summer 2026 change.
If a device shows the wrong time after a rule change, the usual cause is an old copy of the database. Our guide how does my phone know the time? explains the network side, and changing the time zone on a phone shows the manual fix.
Using the tz database in code
- Store UTC, convert with a zone name. Save timestamps in UTC (or with an offset) and the user’s zone as a name such as Europe/Madrid, never as a fixed offset. Offsets change with the seasons and with laws.
- Python: “The zoneinfo module provides a concrete time zone implementation to support the IANA time zone database”; when the system has no data, it falls back to the “first-party tzdata package available on PyPI”, which is recommended for Windows (Python docs). Check the version with
tzdata.IANA_VERSION; ours read “2026f”. - Know which copy you run. Operating systems, browsers, Java and the Python package can each carry a different release. After a change like Cuba’s (2026f), test with a known future date.
- Pick names from zone1970.tab for user menus, and accept links as input so old saved settings keep working.
- Do not invent abbreviations. Since a series of releases in 2016 and 2017 (from 2016b to 2017a), many zones use numeric abbreviations such as “+03” in place of invented English ones; see our abbreviations guide. For writing times, see ISO 8601.
How we checked
Counts come from the tzdata 2026f package (pip, IANA_VERSION asserted “2026f”): lines beginning “Z “, “L ” and “R ” in tzdata.zi, and non-comment rows of the three .tab files, cross-checked with Python’s zoneinfo.available_timezones(). Release counts (every “Release” heading, including separate code and data releases) and headlines are parsed from the NEWS file in a clone of the official tz repository (github.com/eggert/tz, head of November 8, 2026). All quotations were read on iana.org, rfc-editor.org and docs.python.org on November 9, 2026.
Sources
- IANA, Time Zone Database (current release 2026f)
- tz theory.html, “Theory and pragmatics of the tz code and data”
- tz-link.html, “Time zone and daylight saving time data”
- tz NEWS file
- tz “etcetera” source file
- RFC 6557 / BCP 175, Procedures for Maintaining the Time Zone Database
- tz development commit eb40bc6 (Nov 8, 2026)
- Python documentation, zoneinfo
Frequently asked questions
What is the tz database?
The IANA time zone database: a public, regularly updated record of the clock rules of regions worldwide, used by operating systems and software to show local time.
What is the latest tz database version?
2026f, released October 27, 2026, as of November 2026.
How many time zones are in the tz database?
Release 2026f defines 345 zones plus 253 links (alternative names). zone1970.tab lists 312 of the zones for user selection.
Who maintains the tz database?
A TZ Coordinator appointed under RFC 6557 (an IANA Designated Expert), working with the public tz mailing list.
Why is it called the Olson database?
After Arthur David Olson, whose name appears throughout its source comments and documentation; the project’s own tz-link page refers to the “Olson/Zoneinfo/tz database”.
Why are time zones named after cities?
The project recommends cities or small islands, not countries, because a city’s clock history is easier to define and city names change less often.