⏱️

Ternis Time Service

ntp.home.ternis.net • time.home.ternis.net

NTP ONLINE
STRATUM 3
PORT 123 UDP
🌐 Coordinated Universal Time (UTC) Standard Reference
00:00:00 .000
YYYY-MM-DD UTC / GMT
🖥️ Server Time (mini3) UTC
00:00:00 .000
YYYY-MM-DD Uptime: --
📱 Your Browser Clock & Drift
00:00:00 .000
Offset: Measuring... RTT: --
Upstream Reference Pool
pool.ntp.org
Sync cycle every 3600s (8 samples)
Last Sync Offset
-- ms
Calculated via RFC 5905
Upstream Delay (RTT)
-- ms
Round-trip network transit time
Server Clock Precision
~0.95 µs
2⁻²⁰ s precision resolution

🔍 Live NTP Packet Probe (RFC 5905)

Sends a real-time binary NTPv4 client request over UDP socket to 127.0.0.1:123 and decodes all 48 header bytes.

Target Endpoint ntp.home.ternis.net (127.0.0.1:123 / UDP)
Leap Indicator (LI) 0 (No warning)
NTP Version & Mode Version 4 • Mode 4 (Server)
Stratum Level Stratum 3 (Secondary server synchronized to upstream pool)
Poll Interval & Precision Poll: 1s (raw 0) • Precision: 2⁻²⁰ s (~0.954 µs)
Root Delay -- ms
Root Dispersion -- ms
Reference Identifier (Peer) --
Server Transmit Timestamp --
Local Probe Latency (RTT) -- ms

📊 Upstream Sync Telemetry Log

Recent NTP synchronization cycles executed by the local daemon against pool.ntp.org.

-- cycles recorded
Sync Timestamp (UTC) Valid Replies Measured Offset Round-Trip Delay
Loading sync records...

🛠️ Client Setup & Integration Guide

Configure any computer, server, or IoT device on the network to use ntp.home.ternis.net as its authoritative time provider.

Default time synchronization daemon on Ubuntu, Debian, Arch, and Raspberry Pi OS:

# 1. Update /etc/systemd/timesyncd.conf
sudo tee /etc/systemd/timesyncd.conf <<EOF
[Time]
NTP=ntp.home.ternis.net
FallbackNTP=pool.ntp.org
EOF

# 2. Restart and verify
sudo systemctl restart systemd-timesyncd
timedatectl timesync-status

Recommended for hypervisors, database hosts, and servers requiring microsecond stability:

# Add Ternis NTP server to /etc/chrony/chrony.conf
echo "server ntp.home.ternis.net iburst prefer" | sudo tee -a /etc/chrony/chrony.conf

# Restart chrony and verify synchronization
sudo systemctl restart chrony
chronyc sources -v
chronyc tracking

Run in an Administrator PowerShell prompt:

# Configure Windows Time Service to point to Ternis NTP
w32tm /config /manualpeerlist:ntp.home.ternis.net /syncfromflags:manual /reliable:YES /update
Restart-Service w32time
w32tm /resync

# Verify status
w32tm /query /status

Run in Terminal or configure via System Settings > General > Date & Time:

# Set network time server via systemsetup
sudo systemsetup -setnetworktimeserver ntp.home.ternis.net
sudo systemsetup -setusingnetworktime on

# Test immediate synchronization
sudo sntp -sS ntp.home.ternis.net

DHCP Option 42 (Automatic Distribution):
The local DHCP server on mini3 is already configured with dhcp-option=option:ntp-server,0.0.0.0, which tells all DHCP clients on the local network (192.168.1.0/24) to automatically use this server as their default NTP clock!

# Manual router NTP peer setting (OpenWrt / pfSense / MikroTik / Fritz!Box):
NTP Server:   ntp.home.ternis.net  (or 192.168.1.23)
Port:         123
Protocol:     NTPv4 / SNTP

🚀 JSON REST APIs for Scripts & Automation

Integrate time and telemetry into bash scripts, IoT sensors, Home Assistant, and health monitoring:

⚡ GET /api/time 📊 GET /api/status 🔍 GET /api/ntp