# Timezone offset is not working for the custom date formats

**URL:** <https://discuss.elastic.co/t/timezone-offset-is-not-working-for-the-custom-date-formats/372010>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [December 16, 2024, 7:07am UTC](https://discuss.elastic.co/t/timezone-offset-is-not-working-for-the-custom-date-formats/372010 "2024-12-16T07:07:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Muskan\_Agarwal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/muskan_agarwal/32/140035_2.png) [@Muskan\_Agarwal](https://discuss.elastic.co/u/Muskan_Agarwal)\
**Post date:** [December 16, 2024, 7:07am UTC](https://discuss.elastic.co/t/timezone-offset-is-not-working-for-the-custom-date-formats/372010/1 "2024-12-16T07:07:11Z")

</div>

On` 2012-05-18 11:41:48,452`, with a timezone offset of `+07:00`, when applying the timezone to a custom date format such as `yyyy-MM-dd HH:mm:ss,SSS`, the following timestamp is produced:  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/4/14605fe8d7f0e3aa51553a01b15250dbcde7ff96.png)

In contrast, when using a standard date format like `ISO8601`, the timestamp is as shown below:  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/1/6168262ff65ab83f59ec413c2b12b89f8a688e97.png)

Input type: Filestream, TCP,UDP  
Stack version: 8.16.0

---

<div class="post-metadata">

**Author:** ![florinsfetea](https://avatars.discourse-cdn.com/v4/letter/f/9fc29f/32.png) [@florinsfetea](https://discuss.elastic.co/u/florinsfetea)\
**Post date:** [March 21, 2025, 6:53am UTC](https://discuss.elastic.co/t/timezone-offset-is-not-working-for-the-custom-date-formats/372010/2 "2025-03-21T06:53:27Z")

</div>

I think I have the same issue, in my case it affects (seems) only windows machines where the Agent is running.

What OS are your Agent (beat) running on?