---
title: "Discussion on \"My Laptop Was in India, My Server Was in UTC, and My Bookings Were in Yesterday\" | Hashnode"
description: "Discussion on \"My Laptop Was in India, My Server Was in UTC, and My Bookings Were in Yesterday\". 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"
url: "https://hashnode.com/posts/the-timezone-bug-that-moved-my-bookings/6abfc151b37b5c733b00cfc9"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [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

Oct 2 · 13 min read · codeandcuriosity.hashnode.dev  
Read the article

-   [#javascript](https://hashnode.com/tag/javascript)
-   [#postgresql](https://hashnode.com/tag/postgresql)
-   [#nextjs](https://hashnode.com/tag/nextjs)
-   [#debugging](https://hashnode.com/tag/debugging)
-   [#software-development](https://hashnode.com/tag/software-development)
-   [#timezone](https://hashnode.com/tag/timezone)

## Written by

[Rushikesh Jadhav](https://hashnode.com/@rushiii)

@rushiii · Pune

  
[View profile](https://hashnode.com/@rushiii)

where sand meets the water 🌊

the topics and concepts which i learn and get more fascinated i write about them here...

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
