# Timezone bug with GMT?

**URL:** https://meta.discourse.org/t/timezone-bug-with-gmt/226180
**Category:** Support
**Created:** [May 5, 2022, 3:02am UTC](https://meta.discourse.org/t/timezone-bug-with-gmt/226180 "2022-05-05T03:02:37Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [May 5, 2022, 6:53am UTC](https://meta.discourse.org/t/timezone-bug-with-gmt/226180/2 "2022-05-05T06:53:10Z")

</div>

I think this has cropped up before:

> [@Conflict between timezones in "Insert date / time"](https://meta.discourse.org/t/conflict-between-timezones-in-insert-date-time/208539/2):
>
> I’m afraid the technical reason here is pretty confusing - you can read about it at [Moment Timezone | Docs](https://momentjs.com/timezone/docs/#/zone-object/offset/) POSIX compatibility requires that the offsets are inverted. Therefore, Etc/GMT-X will have an offset of +X and Etc/GMT+X will have an offset of -X . This is a result of IANA’s [Time Zone Database](https://github.com/eggert/tz/blob/2017b/etcetera#L36-L42) and not an arbitrary choice by Moment.js. Thus, using locality based identifiers is preferred over fixed-offset identifiers. So, in IANA’s Time Zone database, Europe/Oslo is currently equivalent…

---

_[View the full topic](https://meta.discourse.org/t/timezone-bug-with-gmt/226180)._