# Historian: Who dictates timestamp?

**URL:** <https://forum.inductiveautomation.com/t/historian-who-dictates-timestamp/116136>\
**Category:** Ignition\
**Created:** [June 24, 2026, 4:37pm UTC](https://forum.inductiveautomation.com/t/historian-who-dictates-timestamp/116136 "2026-06-24T16:37:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eugene49](https://avatars.discourse-cdn.com/v4/letter/e/c6cbf5/32.png) [@Eugene49](https://forum.inductiveautomation.com/u/Eugene49)\
**Post date:** [June 24, 2026, 4:37pm UTC](https://forum.inductiveautomation.com/t/historian-who-dictates-timestamp/116136/1 "2026-06-24T16:37:34Z")

</div>

Acting as Ignition SME, and was asked,  
Who dictates the timestamp?  
Gateway Timezone?  
DB (Historian) Timezone?  
Relating to both Tag Historian and SQL Bridge Logging.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [June 24, 2026, 5:28pm UTC](https://forum.inductiveautomation.com/t/historian-who-dictates-timestamp/116136/2 "2026-06-24T17:28:11Z")

</div>

The tag historian uses the timestamps on values supplied by the OPC Server. If that is the Ignition loopback connection, then the Ignition gateway is supplying them. In recent versions of Ignition, an OPC Client connection can be set to use the gateway time instead of the OPC server time, but that breaks backfill IIRC.

The SQL Bridge module always uses the gateway time, I think.

---

<div class="post-metadata">

**Author:** ![Eugene49](https://avatars.discourse-cdn.com/v4/letter/e/c6cbf5/32.png) [@Eugene49](https://forum.inductiveautomation.com/u/Eugene49)\
**Post date:** [June 24, 2026, 5:47pm UTC](https://forum.inductiveautomation.com/t/historian-who-dictates-timestamp/116136/3 "2026-06-24T17:47:51Z")

</div>

Thanks.. It's always been the timestamp/timezone (giving me a headache), always coming back to this..
