mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Custom Timezone: UTC (no DST) #1054
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#1054
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JacksonChen666 on GitHub (May 1, 2022).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ 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.
@CommanderStorm commented on GitHub (Jun 10, 2023):
There is no advantage to this feature request, right?
I think this should be left as is

@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
@CommanderStorm commented on GitHub (Jun 10, 2023):
So basically you want UTC+00 which is here:

@CommanderStorm commented on GitHub (Jun 10, 2023):
Note that having an extra selection for
UTCwould 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
@JacksonChen666 commented on GitHub (Jun 10, 2023):
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.
@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
@Xyem commented on GitHub (Jul 29, 2025):
I would also like to have a simple
UTCoption because the server's timezone isUTC(as are all my servers, so all logs are temporally consistent). Uptime Kuma somehow 'auto-detecting'Europe/Londonresulted it storing all the timestamps incorrectly, making comparison between its timestamps and log files to determine the cause of an issue unnecessarily difficult.