---
title: "Time Synchronization"
description: "Keep the host clock synchronized with NTP for accurate, comparable timestamps"
source_url: https://ai-ops.com/docs/installation/time-synchronization
---

# Time Synchronization

We strongly recommend keeping the host clock synchronized with NTP (Network Time Protocol). Koios timestamps every device read, model prediction, event, and historical sample using the host clock, so a well-synchronized clock keeps your trends, model history, and event timelines aligned with reality. Koios runs fine without it, but accurate time makes the data far more trustworthy and easier to compare against other systems.

## What Synchronized Time Gives You

| Area | Benefit |
|------|---------|
| **On-host accuracy** | Time-series data is written with correct timestamps, so trends, model history, and event timelines line up with reality. |
| **UI freshness** | The UI compares its clock against the server clock. Large drift can trigger a warning on the System Overview page and make "live" values look stale or future-dated. |
| **Cross-system comparison** | Comparing Koios timestamps against PLC, SCADA, or third-party historians stays reliable when both sides share accurate time. |

## Check and Enable It

Ubuntu enables `systemd-timesyncd` automatically on a clean install. Verify it is running and synchronized:

```bash
timedatectl status
```

The output should show `System clock synchronized: yes` and `NTP service: active`. If it isn't, enable it:

```bash
sudo timedatectl set-ntp true
```

For air-gapped sites, point the host at an internal NTP server by editing `/etc/systemd/timesyncd.conf`:

```ini
[Time]
NTP=ntp.internal.example.com
FallbackNTP=ntp.ubuntu.com
```

Then restart the service:

```bash
sudo systemctl restart systemd-timesyncd
```

## What's Next

- [Installing Docker Engine](https://ai-ops.com/docs/installation/installing-docker.md): install the Docker runtime on the host