Check System Date, Time and NTP Sync on Linux

Updated: 2025-11-17

Check System Date, Time and NTP Sync on Linux

Step-by-step guide to monitor system date and time on your Linux server? Need to ensure accurate timestamps and detect time synchronization issues automatica...

Ready-made task for Zuzia

Get an alert when the server clock drifts

Create a free account and connect your server. The Free plan includes 1 monitored task.
In Tasks, create a task, paste the command below, pick the server and run it every 30 minutes.
Turn on “Monitor the result”. You get OK, warning or critical, and an alert when it changes.

z(){ printf '%s - %s' "$1" "$2"; [ -n "$3" ] && printf ' | %s' "$3"; printf '\n'; case $1 in OK|SKIP) exit 0;; WARNING) exit 1;; CRITICAL) exit 2;; *) exit 3;; esac; }; lv(){ if [ "$1" -ge "$3" ]; then echo CRITICAL; elif [ "$1" -ge "$2" ]; then echo WARNING; else echo OK; fi; }; num(){ case $1 in ''|*[!0-9]*) return 1;; esac; }; wr(){ case $1 in CRITICAL) s=CRITICAL;; WARNING) [ "$s" = OK ] && s=WARNING;; esac; }; if command -v chronyc >/dev/null 2>&1; then r=$(chronyc tracking 2>/dev/null); echo "$r" | grep -q 'Not synchronised' && z CRITICAL "chrony not synchronised"; o=$(echo "$r" | awk '/^System time/{printf "%d",($4<0?-$4:$4)*1000}'); num "$o" || z UNKNOWN "cannot read chrony offset"; z "$(lv $o 100 1000)" "clock offset ${o} ms" "offset_ms=$o;100;1000"; elif command -v timedatectl >/dev/null 2>&1; then if [ "$(timedatectl show -p NTPSynchronized --value 2>/dev/null)" = yes ]; then z OK "clock synchronised"; else z CRITICAL "clock not synchronised"; fi; else z SKIP "no chrony or timedatectl"; fi

The same command is in the panel's public commands as “Check: Clock drift”, so you can also add it from there.

Set up this check free Free plan · no credit card

Why Monitoring System Date and Time Matters

Monitoring system date and time on your Linux server is crucial for accurate logging, security, and system coordination. Incorrect system time can cause log entries to be out of order, SSL certificates to appear invalid, scheduled tasks to run at wrong times, and distributed systems to fail. Regular time monitoring helps detect time drift, verify NTP synchronization, and ensure accurate timestamps for all system operations.

Method 1: Check Current Date and Time

The date command displays the current system date and time. This is the simplest way to check system time.

Basic Date and Time Check

To see current date and time:

# Check current date and time
date

# Check date and time in specific format
date +"%Y-%m-%d %H:%M:%S"

# Check date and time with timezone
date +"%Y-%m-%d %H:%M:%S %Z"

Check Timezone

To see current timezone settings:

# Check timezone with timedatectl
timedatectl

# Check timezone file
cat /etc/timezone

# Check timezone link
ls -la /etc/localtime

Check System Clock

To see detailed system clock information:

# Show system clock status
timedatectl status

# Show all time-related information
timedatectl show

Method 2: Check NTP Synchronization

Network Time Protocol (NTP) synchronizes system time with time servers. Monitoring NTP synchronization ensures accurate time.

Check NTP Status with timedatectl

# Check NTP synchronization status
timedatectl status

# Check if NTP is active
timedatectl | grep "NTP"

# Show NTP synchronization details
timedatectl show-timesync

Check NTP with chrony (if using chronyd)

# Check chrony sources
chrony sources

# Check chrony tracking
chrony tracking

# Check chrony statistics
chrony sourcestats

Check NTP with ntpdate

# Query NTP server (doesn't change time)
ntpdate -q pool.ntp.org

# Check multiple NTP servers
ntpdate -q 0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org

Method 3: Automated Time Monitoring with Zuzia.app

Manual checks work while you are looking. To keep running them without you, Zuzia uses its agent and scheduled tasks.

How it works in Zuzia

Install the Zuzia agent on the server with one command. CPU, RAM, disk, load and network metrics start reporting on their own, with alerts on a threshold, on drift from the server's normal, or on a disk fill-up forecast.
Save the commands from this guide as a scheduled task and choose how often it runs, from every minute to once a year. The agent runs it on every host you pick.
If a command fails, you get an alert right away by email, Slack, Discord, push (through your Pushover account) or SMS (through your Vonage account).
The output of every run is kept, so you can look back at what changed. On paid plans, AI can read the output and alert you only when it spots a problem.

Setting it up

Add the server in the Zuzia dashboard and install the agent.
Create a scheduled task with the check commands below, then choose the hosts and how often it runs.
Choose your notification channels. Turn on maintenance mode during planned work so it doesn't trigger alerts.

Method 4: Advanced Time Monitoring Techniques

Track Time Drift Over Time

To identify time drift patterns:

# Save current time
date +"%Y-%m-%d %H:%M:%S" > /tmp/time-$(date +%Y%m%d-%H%M%S).txt

# Compare with previous snapshot
diff /tmp/time-old.txt /tmp/time-new.txt

# Calculate time drift
date1=$(cat /tmp/time-old.txt | date +%s -f -)
date2=$(cat /tmp/time-new.txt | date +%s -f -)
echo "Drift: $((date2-date1)) seconds"

Monitor Timezone Changes

To detect timezone changes:

# Check timezone
timedatectl | grep "Time zone"

# Save timezone
timedatectl | grep "Time zone" > /tmp/timezone-$(date +%Y%m%d).txt

# Compare timezone
diff /tmp/timezone-old.txt /tmp/timezone-new.txt

Check Hardware Clock

To check hardware clock (RTC):

# Show hardware clock
sudo hwclock --show

# Compare hardware clock with system clock
sudo hwclock --compare

Real-World Use Cases for Time Monitoring

Log Accuracy

For accurate log timestamps:

# Check system time
date

# Verify log timestamps match
tail -5 /var/log/syslog | awk '{print $1, $2, $3}'

SSL Certificate Validation

For SSL certificate validation:

# Check system time
date

# Verify certificate validity
openssl x509 -in certificate.crt -noout -dates

Scheduled Task Coordination

For coordinating scheduled tasks:

# Check system time
date

# Verify cron job timing
crontab -l

Best Practices for Time Monitoring

1. Monitor Time Regularly

Check system time every hour or every few hours. Time should remain stable if NTP is properly configured. Use Zuzia.app automated monitoring to check time continuously without manual intervention.

2. Monitor NTP Synchronization

Verify NTP synchronization regularly. Alert if NTP synchronization fails or time drift exceeds thresholds.

3. Set Appropriate Alert Thresholds

Configure alerts for time drift:

Warning: 5-10 seconds drift
Critical: 30+ seconds drift
Emergency: 60+ seconds drift

4. Monitor Timezone Changes

Alert on timezone changes as they can cause confusion and scheduling issues.

5. Compare with Multiple NTP Servers

Use multiple NTP servers for redundancy and accuracy verification.

Troubleshooting Common Time Issues

Time Drifting

If time is drifting:

# Check NTP status
timedatectl status

# Restart NTP service
sudo systemctl restart chronyd
# or
sudo systemctl restart ntpd

# Force NTP synchronization
sudo chrony makestep

NTP Not Synchronizing

If NTP is not synchronizing:

# Check NTP service status
sudo systemctl status chronyd
# or
sudo systemctl status ntpd

# Check NTP configuration
cat /etc/chrony.conf
# or
cat /etc/ntp.conf

# Check firewall rules
sudo iptables -L | grep ntp

Timezone Issues

If timezone is incorrect:

# List available timezones
timedatectl list-timezones

# Set timezone
sudo timedatectl set-timezone Europe/Warsaw

# Verify timezone
timedatectl

FAQ: Common Questions About Monitoring System Time

How often should I check system time?

We recommend checking system time every hour or every few hours. Time should remain stable if NTP is properly configured. Use Zuzia.app automated monitoring to check time continuously without manual intervention.

What if time drifts significantly?

You'll receive notifications when time drifts beyond acceptable thresholds through Zuzia.app. You may need to check NTP configuration, restart time synchronization services, or verify network connectivity to NTP servers. Use timedatectl status to check NTP synchronization status.

Can I check NTP synchronization?

Yes, you can use timedatectl status to check NTP synchronization status, or chrony sources if using chronyd. For detailed NTP information, use ntpdate -q pool.ntp.org to query NTP servers without changing system time.

How do I detect time synchronization issues?

Set up automated monitoring in Zuzia.app that compares system time with NTP servers. Alert if time drift exceeds thresholds or if NTP synchronization fails. Monitor timedatectl status output for NTP synchronization status.

What's the difference between system time and hardware clock?

System time is maintained by the kernel and synchronized with NTP. Hardware clock (RTC) is maintained by the hardware and persists across reboots. System time should be synchronized with hardware clock on boot and with NTP during operation.

How can I monitor time across multiple servers?

Zuzia.app allows you to add multiple servers and monitor system time across all of them simultaneously. Each server executes commands independently, and all results are stored in Zuzia.app's database for centralized monitoring and analysis. This helps ensure all servers maintain synchronized time.

Does Zuzia.app use AI to analyze time patterns?

On paid plans, AI can read the output of your scheduled tasks and commands, explain it in plain language and alert you only when it spots a problem. Metric alerts work without AI: Zuzia alerts when CPU, RAM or load drifts from the server's normal and forecasts when a disk will fill up.

Check System Date, Time and NTP Sync on Linux