# Kibana Security Timeline bad timestamp parsing

**URL:** <https://discuss.elastic.co/t/kibana-security-timeline-bad-timestamp-parsing/298991>\
**Category:** Elastic Security\
**Created:** [March 7, 2022, 4:44pm UTC](https://discuss.elastic.co/t/kibana-security-timeline-bad-timestamp-parsing/298991 "2022-03-07T16:44:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Silver137](https://avatars.discourse-cdn.com/v4/letter/s/839c29/32.png) [@Silver137](https://discuss.elastic.co/u/Silver137)\
**Post date:** [March 7, 2022, 4:44pm UTC](https://discuss.elastic.co/t/kibana-security-timeline-bad-timestamp-parsing/298991/1 "2022-03-07T16:44:42Z")

</div>

I'm trying to investigate custom security events using Kibana timeline security features.  
My surprise when I see that the temporal searched works, but the timestamp is interpreted without adding the epoch offset, for example a event that matching 8 Jan 2022 is represented as Jan 20, 1970

All other features and querys in Kibana parsed the timestamp correctly but this case is not working.

Kibana Version 7.15.1

Thanks !

![imagen](https://us1.discourse-cdn.com/elastic/original/3X/3/3/3320ab0ed4d5aa02b44ea19c9a30683b1af63070.png)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 4, 2022, 4:44pm UTC](https://discuss.elastic.co/t/kibana-security-timeline-bad-timestamp-parsing/298991/2 "2022-04-04T16:44:46Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.