Should your server run on UTC or local time? Decide and change it
Short answer: For most business servers, set the system clock's time zone to UTC and handle local time in your application and reports. UTC never jumps for daylight saving, so logs stay in order, scheduled jobs don't skip or double up at the changeover, and servers in different places agree. Where you genuinely need local-time scheduling, such as a 7 am reminder in New Zealand, specify the time zone on that schedule rather than changing the whole server. If you change a running server's time zone, check cron jobs, logs and applications first, and keep the hardware clock in UTC.
Why the choice matters
New Zealand shifts its clocks twice a year. On a server set to local time:
- Logs gain an hour that happens twice in autumn and lose an hour in spring, making incident timelines confusing.
- Scheduled jobs at times inside the changeover hour can run twice or not at all.
- Multiple servers in different regions or clouds may disagree about "now", and comparing logs becomes guesswork.
- Developers and suppliers abroad have to convert every timestamp.
UTC avoids all of this: it has no daylight saving, and most cloud servers start in UTC by default.
The case for local time is mostly convenience: reading logs and cron entries in familiar hours. That convenience usually costs more than it saves once something goes wrong around a clock change.
Check your current setting
On most modern Linux systems, timedatectl shows the current settings. Its manual describes status as showing the system clock and real-time clock (RTC) settings, including whether network time synchronisation is active. timedatectl list-timezones lists available zones, and set-timezone sets the system time zone, which, the manual notes, changes the /etc/localtime link.
Keep the hardware clock in UTC
The timedatectl manual is explicit about the RTC, the clock kept by the hardware or virtual machine: maintaining it in local time is not fully supported and will create problems with time zone changes and daylight saving adjustments, and if at all possible it should be kept in UTC. Its set-local-rtc option controls this. Leave it on UTC.
Keep time synchronised
The same manual describes set-ntp to enable network time synchronisation. Accurate time matters for logs, certificates, two-factor codes and scheduled jobs, whatever time zone you choose.
Schedule local-time jobs explicitly
When a job must run at a local time, such as sending appointment reminders at 7 am Auckland time, express that in the schedule:
- systemd timers: the
systemd.timemanual explains that calendar specifications can include a time zone, either the literalUTC, the local zone, or an IANA time zone name, so a timer can say "7:00 Pacific/Auckland" on a UTC server. - Application schedulers: many frameworks let each scheduled task specify a time zone.
- Hourly check: run hourly and let the code decide whether it's the right local time.
This keeps the server in UTC while customers get messages at sensible local times.
Handle time zones in your application
- Store timestamps in UTC or with explicit offsets in the database.
- Convert for display to the customer's or business's time zone at the last moment.
- Configure the application's time zone setting separately from the server's, if your framework has one, and set it deliberately.
- Show time zones in reports that staff use, so "09:00" is never ambiguous.
Changing the time zone on a live server
If a server currently runs in local time and you want UTC:
- List scheduled jobs in crontabs, systemd timers and application schedulers, and note which depend on local time.
- Adjust their times or add explicit time zones before the change.
- Check applications that read the system time zone, especially older code that formats dates without specifying one.
- Change the time zone with
timedatectl set-timezone UTCduring a quiet period. - Restart services that cache the time zone at startup.
- Watch the next scheduled runs and logs closely.
- Tell your team that logs are now in UTC.
Tools that make UTC easy to read
- Configure log viewers and monitoring dashboards to display in local time while storing UTC.
- Add a small "UTC now" clock to your team's dashboard or chat.
- Use ISO 8601 timestamps with offsets in logs, such as
2026-11-10T09:00:00Z.
Containers and managed services
Containers have their own idea of the time zone, usually UTC unless the image sets otherwise, regardless of the host. Managed databases, queues and serverless platforms often run in UTC with no option to change. That's another reason to treat UTC as the default everywhere and convert at the edges: your servers, containers and managed services will then agree without per-service configuration. If an image does need a local zone, set it explicitly in the image definition and document why, rather than relying on whatever the base image happens to include.
Write the decision down
Record the decision in your technical documentation: servers in UTC, hardware clocks in UTC, time sync enabled, application time zone set to the business's zone for display, and local-time jobs scheduled with explicit time zones. A short note like this prevents a future developer from changing one server back to local time to make a log easier to read, and reintroducing the daylight saving problems you solved.
An illustrative example
A hypothetical Tauranga tour operator's booking server ran on New Zealand time. Each April, a nightly 2:30 am export ran twice, sending duplicate files to a partner; each September it didn't run at all. The developer switched the server to UTC, rescheduled the export with an explicit Pacific/Auckland time in a systemd timer set to a time outside the changeover hour, confirmed the RTC was in UTC and time sync was active, and set the monitoring dashboard to display local time.
FAQ
Will changing to UTC change my data?
Stored UTC timestamps stay the same. Data stored as local times without offsets needs care.
Do cloud servers default to UTC?
Many do. Check with timedatectl.
What about Windows servers?
The same principles apply; the tools differ.
Does the database have its own setting?
Often, yes. Check it separately.
If your servers' clocks and schedules cause confusion around daylight saving, tell us what runs on them.