Kazakhstan: One Country, One Clock
Kazakhstan historically operated on two UTC offsets: western regions used UTC+5 (Asia/Aqtau, Asia/Aqtobe, Asia/Atyrau, Asia/Oral) while eastern regions used UTC+6 (Asia/Almaty, Asia/Qyzylorda). On 1 March 2024, Kazakhstan unified the entire country on UTC+5 year-round, eliminating an internal one-hour split that had complicated cross-country logistics for decades. The IANA tzdata 2024a release merged affected zones and added historical records for the transition.
Paraguay: Permanent Standard Time
Paraguay had observed daylight saving time since 1975, advancing clocks to UTC-3 in summer and retreating to UTC-4 in winter. In 2024 the Paraguayan government decided to adopt permanent UTC-3 year-round, abolishing the seasonal clock change. The change was included in tzdata 2025a alongside a correction to the historical transition dates. Paraguay joins a growing list of South American countries -- including Chile (for most regions) and Argentina -- that have eliminated seasonal time changes.
Chile: A New Timezone for the Aysén Region
Chile's Aysén Region (Region XI), a vast and sparsely populated territory in Patagonia, adopted permanent UTC-3 in 2025 after previously following the national DST schedule (-04/-03). The tzdata 2025b release created a new IANA zone identifier for the region. The change reflects a broader Chilean review of regional timekeeping prompted by the country's geography -- Chile spans more than 38 degrees of latitude, making a single national timezone rule a poor fit for all regions.
Why These Changes Matter for Developers
Each of these changes affects any software that uses IANA timezone identifiers for these regions. Applications that cached "UTC+6 for Almaty" or hard-coded Paraguay's DST schedule will silently display wrong times for past events or fail to compute future meeting times correctly. The correct practice is to always use IANA timezone identifiers (Asia/Almaty, America/Asuncion, America/Coyhaique) and keep the tzdata database current. Docker images, language runtimes, and cloud function environments all need to be updated to pick up tzdata 2024a/2025a/2025b.