time.txryan.com

server

Public stratum 2 NTP over IPv4 and IPv6.

Hostname

time.txryan.com

Addresses

148.113.167.187 / 2607:5300:205:200::a806

NTP Port

123 / udp

roughtime

Responses are cryptographically signed. Powered by roughtime ↗.

Address

time.txryan.com:2002

Ed25519 public key

iBVjxg/1j7y1+kQUTBYdTabxCppesU/07D4PMDJk2WA=

ecosystem.json

Example config with this server and Cloudflare:

{
  "servers": [
    {
      "name": "time.txryan.com",
      "version": "IETF-Roughtime",
      "publicKeyType": "ed25519",
      "publicKey": "iBVjxg/1j7y1+kQUTBYdTabxCppesU/07D4PMDJk2WA=",
      "addresses": [{ "protocol": "udp", "address": "time.txryan.com:2002" }]
    },
    {
      "name": "Cloudflare-Roughtime-2",
      "version": "IETF-Roughtime",
      "publicKeyType": "ed25519",
      "publicKey": "0GD7c3yP8xEc4Zl2zeuN2SlLvDVVocjsPSL8/Rl/7zg=",
      "addresses": [
        { "protocol": "udp", "address": "roughtime.cloudflare.com:2003" }
      ]
    }
  ]
}

Multiple servers recommended. Full list of active Roughtime servers ↗

connect

server time.txryan.com iburst

server time.txryan.com iburst

sntp -d time.txryan.com

faq

Can I use this server?

Yes. Individual users may point a client at time.txryan.com. Contact Tanner ↗ before using it for high-volume infrastructure. No uptime or accuracy guarantees are provided. The server is monitored and maintained.

What does stratum 2 mean?

Stratum 0 is a reference clock, such as an atomic clock or GPS receiver. Stratum 1 connects directly to stratum 0. This server is stratum 2 and synchronizes with stratum 1 servers.

Why does accurate time matter?

TLS certificates, logs, distributed databases, and authentication tokens depend on correct clocks. A wrong clock can accept expired certificates, reject valid ones, and make event ordering unreliable.

How does NTP work?

NTP records four timestamps: client send, server receive, server send, and client receive. These estimate network delay and clock offset. Repeated samples keep the client clock synchronized.

What's wrong with plain NTP?

Most NTP responses are unauthenticated, so a network intermediary can alter timestamps. Moving a clock backward can make expired certificates valid. Moving it forward can make certificates valid before their start date.

How does Roughtime work?

Roughtime uses a long-term root key to sign a short-lived delegated key, which signs responses. A client sends a nonce and receives a signed timestamp and uncertainty radius. It verifies both signatures using the known root public key.

Clients can chain requests across servers. Inconsistent timestamps provide signed evidence that a server reported false time.

Why run both?

NTP provides continuous synchronization. Roughtime provides signed time without TLS or a correct local clock.

How does the clock on this page work?

The page exchanges four timestamps with this server over WebSocket. It filters samples by round-trip time and smooths the estimated clock offset. Displayed UTC is local system time plus that offset.