---
title: "#timezone articles | Hashnode"
description: "Explore 45 articles tagged #timezone on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/timezone"
---

Tag

# #timezone

45 posts · 1 followers

[Payyavula Balanagaraju](https://hashnode.com/@nagaraju2506) · [Nov 7](https://hashnode.com/posts/dates-timezones-beginners-guide/6aef7b245a14a48f32ff1251)

### [Save the moment in UTC, save the place by name: a beginner’s guide to dates and timezones](https://depthfirst.hashnode.dev/dates-timezones-beginners-guide?utm_source=hashnode&utm_medium=feed)

Store the moment in UTC and the place by name. Learn who keeps timezone rules, why Vancouver shows MST, and when UTC alone breaks

9 min read · [depthfirst.hashnode.dev](https://depthfirst.hashnode.dev/dates-timezones-beginners-guide?utm_source=hashnode&utm_medium=feed)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 28](https://hashnode.com/posts/agent-scheduled-nightly-job-local-time-container-utc/6ae232202bd24a55cdb0ffe1)

### [The agent scheduled the nightly job in its own local time, and the container ran it seven hours off](https://blogs.powerduck.com/agent-scheduled-nightly-job-local-time-container-utc?utm_source=hashnode&utm_medium=feed)

The agent scheduled a nightly report at 02:00, ran it by hand, and committed. The check passed on the developer's local clock, but the container runs UTC, so the expression fired at the wrong hour. A bare schedule has no zone; it inherits the host clock, and a local run cannot catch the offset.

3 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-scheduled-nightly-job-local-time-container-utc?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/agent-scheduled-nightly-job-local-time-container-utc/6ae232202bd24a55cdb0ffe1)

[TradingLookup](https://hashnode.com/@tradinglookup) · [Oct 17](https://hashnode.com/posts/is-the-exchange-open-handling-trading-hours-holidays-and-dst-across-six-markets/6ad39da1ad133d10348ae019)

### [Is the exchange open? Handling trading hours, holidays and DST across six markets](https://tradinglookup.hashnode.dev/is-the-exchange-open-handling-trading-hours-holidays-and-dst-across-six-markets?utm_source=hashnode&utm_medium=feed)

Exchange hours in code: DST gaps, half days, split Friday sessions and holidays for NYSE, LSE, NSE, PSX, NGX and JSE, with zoneinfo and Intl examples.

8 min read · [tradinglookup.hashnode.dev](https://tradinglookup.hashnode.dev/is-the-exchange-open-handling-trading-hours-holidays-and-dst-across-six-markets?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/is-the-exchange-open-handling-trading-hours-holidays-and-dst-across-six-markets/6ad39da1ad133d10348ae019)

[Rushikesh Jadhav](https://hashnode.com/@rushiii) · [Oct 2](https://hashnode.com/posts/the-timezone-bug-that-moved-my-bookings/6abfc151b37b5c733b00cfc9)

### [My Laptop Was in India, My Server Was in UTC, and My Bookings Were in Yesterday](https://codeandcuriosity.hashnode.dev/the-timezone-bug-that-moved-my-bookings?utm_source=hashnode&utm_medium=feed)

A real timezone bug from a production booking platform: how I found it, how I debugged it, how I fixed it, and whether my fix was the right one

13 min read · [codeandcuriosity.hashnode.dev](https://codeandcuriosity.hashnode.dev/the-timezone-bug-that-moved-my-bookings?utm_source=hashnode&utm_medium=feed)

[Hussain Fakhruddin](https://hashnode.com/@hussainanjar) · [Aug 20](https://hashnode.com/posts/mena-date-time-calendars-zones-qa/6a86e2366ca5090b10ff8ab7)

### [Dates and time zones in MENA apps: calendars, DST and QA](https://www.sultanbyte.com/mena-date-time-calendars-zones-qa?utm_source=hashnode&utm_medium=feed)

A practical guide to named zones, Arabic calendars and civil-time rule changes.

7 min read · [sultanbyte.com](https://www.sultanbyte.com/mena-date-time-calendars-zones-qa?utm_source=hashnode&utm_medium=feed)

[Chukwuemeka Aladimma](https://hashnode.com/@Acel) · [Jul 13](https://hashnode.com/posts/it-worked-on-every-environment-except-prod-getting-daily-reports-right-across-timezones/6a54b77aca05dfb1082ca1aa)

### [It Worked on Every Environment Except Prod: Getting Daily Reports Right Across Timezones](https://blog.acel.dev/it-worked-on-every-environment-except-prod-getting-daily-reports-right-across-timezones?utm_source=hashnode&utm_medium=feed)

Every day, a report runs: "what did each store sell yesterday?" One of the stores is in Lagos, the other in London. The report showed both stores as having zero sales for the last two hours of the day

7 min read · [blog.acel.dev](https://blog.acel.dev/it-worked-on-every-environment-except-prod-getting-daily-reports-right-across-timezones?utm_source=hashnode&utm_medium=feed)

[Mani Raju](https://hashnode.com/@unixlytools) · [Jun 13](https://hashnode.com/posts/why-utc-exists-and-why-gmt-isn-t-enough/6a2d56ec259eb6cbf8e75cf1)

### [Why UTC Exists (And Why GMT Isn't Enough)](https://unixlytools.hashnode.dev/why-utc-exists-and-why-gmt-isn-t-enough?utm_source=hashnode&utm_medium=feed)

For a long time, I assumed UTC and GMT were basically the same thing. Whenever I saw: UTC+00:00 or GMT+00:00 I treated them as interchangeable. Most developers do. And honestly, for many application

6 min read · [unixlytools.hashnode.dev](https://unixlytools.hashnode.dev/why-utc-exists-and-why-gmt-isn-t-enough?utm_source=hashnode&utm_medium=feed)

[mikemaittech](https://hashnode.com/@mike-mait) · [Apr 29](https://hashnode.com/posts/the-timezone-bugs-you-don-t-know-you-have-and-how-to-find-them/69f237336e0124c05e372f66)

### [The timezone bugs you don't know you have (and how to find them)](https://mike-mait.hashnode.dev/the-timezone-bugs-you-don-t-know-you-have-and-how-to-find-them?utm_source=hashnode&utm_medium=feed)

Most production apps quietly corrupt data on DST transition day. The 5 timezone bugs hiding in your code — with one-liner tests to find them.

5 min read · [mike-mait.hashnode.dev](https://mike-mait.hashnode.dev/the-timezone-bugs-you-don-t-know-you-have-and-how-to-find-them?utm_source=hashnode&utm_medium=feed)

[Shantanu Badmanji](https://hashnode.com/@ShantanuBadmanji) · [Apr 20](https://hashnode.com/posts/why-date-updated-at-broke-timezones-and-killed-postgresql-index-performance/69e697e2c9501dd01036ca18)

### [Why DATE(updated\_at) Broke Timezones and Killed PostgreSQL Index Performance](https://shantanubadmanji.hashnode.dev/why-date-updated-at-broke-timezones-and-killed-postgresql-index-performance?utm_source=hashnode&utm_medium=feed)

A real-world deep-dive into how a single SQL wrapper caused wrong dates for international users and made indexes completely useless — and the SARGable fix that resolved both.

7 min read · [shantanubadmanji.hashnode.dev](https://shantanubadmanji.hashnode.dev/why-date-updated-at-broke-timezones-and-killed-postgresql-index-performance?utm_source=hashnode&utm_medium=feed)

[Damola Nelson](https://hashnode.com/@damolanelson) · [Apr 13](https://hashnode.com/posts/the-day-my-calendar-lied-by-one/69dd2061217f5dfcbd1b3395)

### [The Day My Calendar Lied by One](https://daily-flutters.hashnode.dev/the-day-my-calendar-lied-by-one?utm_source=hashnode&utm_medium=feed)

A Flutter diary on UTC drift, timezone lookups, and calendar caching that turned a “one day off” bug into real architectural clarity.

5 min read · [daily-flutters.hashnode.dev](https://daily-flutters.hashnode.dev/the-day-my-calendar-lied-by-one?utm_source=hashnode&utm_medium=feed)
