Public lab note: one instant, two calendar days
A reproducible timezone observation using synthetic timestamps, with a narrow statement of what it proves.
Public lab note: one instant, two calendar days
This is a public worked example, prepared for reproduction. It contains synthetic timestamps and makes no claim about anyone's activities or private journal.
The question
Does a UTC timestamp determine the same displayed calendar day everywhere? Compare the instant immediately before and after midnight in Bangkok using a named zone rather than the machine's default.
const day = new Intl.DateTimeFormat("en-CA", {
timeZone: "Asia/Bangkok", year: "numeric", month: "2-digit", day: "2-digit"
});
console.log(day.format(new Date("2024-02-28T16:59:59Z")));
console.log(day.format(new Date("2024-02-28T17:00:00Z")));
The fields change from February 28 to February 29. The input values differ by one second; the calendar boundary belongs to the selected zone. Locale formatting may change punctuation, so application logic should extract fields with formatToParts rather than split a formatted string.
What this establishes
A date display needs both an instant and a timezone decision. This example does not measure clock accuracy, network delay or future timezone policy. Record the zone and the inputs when sharing a date bug so another reader can reproduce the boundary without personal records.
Reference: Intl.DateTimeFormat.formatToParts.