---
title: "Comment by Oliver Jones on \"4 Time Zone Bugs I Ran Into\" | Hashnode"
description: "Here&#39;s another timezone bug. With a correct timezone file, I once tried to convert a local time of 2018-03-23 02:15 to UTC time. It failed with some sort of"
url: "https://hashnode.com/posts/4-time-zone-bugs-i-ran-into/5f6b770c61f6923cac7c02e5/comment/5f6dccb660599c596c472083"
---

[Discussion](https://hashnode.com/posts/4-time-zone-bugs-i-ran-into/5f6b770c61f6923cac7c02e5)

Comment [4 Time Zone Bugs I Ran Into](https://hashnode.com/posts/4-time-zone-bugs-i-ran-into/5f6b770c61f6923cac7c02e5)

[Oliver Jones](https://hashnode.com/@OliverJones)

[Sep 25, 2020](https://hashnode.com/posts/4-time-zone-bugs-i-ran-into/5f6b770c61f6923cac7c02e5/comment/5f6dccb660599c596c472083)

Here's another timezone bug. With a _correct_ timezone file, I once tried to convert a local time of 2018-03-23 02:15 to UTC time. It failed with some sort of "incorrect date/time value" exception. It was buried in a big batch of otherwise correct data, which made it worse to track down.

It turned out that, in my timezone (America/New\_York) that time didn't exist! That was daylight time switchover day in 2018. The local clock ticks from 01:59 to 03:00 on that day.

[David Ojeda](https://hashnode.com/@david_ojeda)

[Sep 25, 2020](https://hashnode.com/posts/4-time-zone-bugs-i-ran-into/5f6b770c61f6923cac7c02e5/comment/5f6dccb660599c596c472083#reply-5f6e10caade1fb598d439634)

Yeah, it sounds like a really difficult bug to track down. DST always finds a way to ruin the day 😅

Thanks for sharing! I'll be even more cautious when the next DST change is approaching.
