Custom Timezone: UTC (no DST) #1054

Open
opened 2026-02-28 02:08:30 -05:00 by deekerman · 7 comments
Owner

Originally created by @JacksonChen666 on GitHub (May 1, 2022).

⚠️ Please verify that this feature request has NOT been suggested before.

  • I checked and didn't find similar feature request

🏷️ Feature Request Type

UI Feature

🔖 Feature description

A timezone that is based off of UTC+00:00 and does not use DST does not exist, and I think it should be added for convenience sake (for those who want to use UTC)

✔️ Solution

Add a custom timezone that is called UTC that is based off of UTC+00:00 and does not have DST.

Alternatives

Using the Africa/Abidjan timezone (should be the equivalent)

📝 Additional Context

I personally prefer over having UTC and then doing my own timezone addition in my head, and do it that way pretty much for other things too (like my website).
I was looking for an option for UTC, but couldn't find one.

Originally created by @JacksonChen666 on GitHub (May 1, 2022). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type UI Feature ### 🔖 Feature description A timezone that is based off of UTC+00:00 and does not use DST does not exist, and I think it should be added for convenience sake (for those who want to use UTC) ### ✔️ Solution Add a custom timezone that is called UTC that is based off of UTC+00:00 and does not have DST. ### ❓ Alternatives Using the [Africa/Abidjan](https://time.is/Abidjan) timezone (should be the equivalent) ### 📝 Additional Context I personally prefer over having UTC and then doing my own timezone addition in my head, and do it that way pretty much for other things too (like my website). I was looking for an option for UTC, but couldn't find one.
Author
Owner

@CommanderStorm commented on GitHub (Jun 10, 2023):

There is no advantage to this feature request, right?

I think this should be left as is
image

@CommanderStorm commented on GitHub (Jun 10, 2023): There is no advantage to this feature request, right? I think this should be left as is ![image](https://github.com/louislam/uptime-kuma/assets/26258709/9af2abb3-0dc5-4d59-a506-813ef6e9d85a)
Author
Owner

@JacksonChen666 commented on GitHub (Jun 10, 2023):

feature request is about adding UTC so people who want UTC can easily choose UTC instead of having to go through many hoops to find something that is similar to UTC

@JacksonChen666 commented on GitHub (Jun 10, 2023): feature request is about adding UTC so people who want UTC can easily choose UTC instead of having to go through many hoops to find something that is similar to UTC
Author
Owner

@CommanderStorm commented on GitHub (Jun 10, 2023):

So basically you want UTC+00 which is here:
image

@CommanderStorm commented on GitHub (Jun 10, 2023): So basically you want UTC+00 which is here: ![image](https://github.com/louislam/uptime-kuma/assets/26258709/1bdbc05d-46ae-4a20-a518-f4d539c58ccc)
Author
Owner

@CommanderStorm commented on GitHub (Jun 10, 2023):

Note that having an extra selection for UTC would be worse, given that we have changed the display of messages to include the timezone marker if an embed is present.
See https://github.com/louislam/uptime-kuma/issues/3153 for more details

@CommanderStorm commented on GitHub (Jun 10, 2023): Note that having an extra selection for `UTC` would be worse, given that we have changed the display of messages to include the timezone marker if an embed is present. See https://github.com/louislam/uptime-kuma/issues/3153 for more details
Author
Owner

@JacksonChen666 commented on GitHub (Jun 10, 2023):

So basically you want UTC+00 which is here:

Yes but it's not as clear cut as "choose one and it is UTC". Scoresbysund (now known as Ittoqqortoormiit) is not UTC because it has DST (https://time.is/Ittoqqortoormiit) and UTC does not have DST.

@JacksonChen666 commented on GitHub (Jun 10, 2023): > So basically you want UTC+00 which is here: Yes but it's not as clear cut as "choose one and it is UTC". Scoresbysund (now known as [Ittoqqortoormiit](https://en.wikipedia.org/wiki/Ittoqqortoormiit)) is not UTC because it has DST (<https://time.is/Ittoqqortoormiit>) and [UTC](https://en.wikipedia.org/wiki/Coordinated_Universal_Time) does not have [DST](https://en.wikipedia.org/wiki/Coordinated_Universal_Time#Daylight_saving_time).
Author
Owner

@CommanderStorm commented on GitHub (Jun 10, 2023):

DST is not supported upstream.
Unless we switch to a different library or dayjs supports this one day, this will not be a feature.

See https://day.js.org/docs/en/manipulate/utc-offset#docsNav
See also https://github.com/iamkun/dayjs/issues/1437

Here is upstream: https://github.com/iamkun/dayjs/blob/dev/src/plugin/timezone/index.js
Here is our clone: https://github.com/louislam/uptime-kuma/tree/master/src/modules/dayjs/plugin/timezone

@CommanderStorm commented on GitHub (Jun 10, 2023): DST is not supported upstream. Unless we switch to a different library or dayjs supports this one day, this will not be a feature. See https://day.js.org/docs/en/manipulate/utc-offset#docsNav See also https://github.com/iamkun/dayjs/issues/1437 Here is upstream: https://github.com/iamkun/dayjs/blob/dev/src/plugin/timezone/index.js Here is our clone: https://github.com/louislam/uptime-kuma/tree/master/src/modules/dayjs/plugin/timezone
Author
Owner

@Xyem commented on GitHub (Jul 29, 2025):

I would also like to have a simple UTC option because the server's timezone is UTC (as are all my servers, so all logs are temporally consistent). Uptime Kuma somehow 'auto-detecting' Europe/London resulted it storing all the timestamps incorrectly, making comparison between its timestamps and log files to determine the cause of an issue unnecessarily difficult.

@Xyem commented on GitHub (Jul 29, 2025): I would also like to have a simple `UTC` option because the server's timezone is `UTC` (as are all my servers, so all logs are temporally consistent). Uptime Kuma somehow 'auto-detecting' `Europe/London` resulted it storing all the timestamps incorrectly, making comparison between its timestamps and log files to determine the cause of an issue unnecessarily difficult.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#1054
No description provided.