time.0xt.ca

Public stratum 2 NTP & Roughtime server in Toronto Canada.

• Server Stratum:Stratum Two
• Hostname:time.0xt.ca
• IPv4 Address:172.105.97.188
• IPv6 Address:2600:3c04::f03c:92ff:fe5e:06e5
• Use DNS:Yes
• Pool Member:Yes (monitoring)
• Server Location:Toronto, Ontario, Canada
• Network:AS63949 Linode
• Synchronization:NTP V4 secondary (stratum 2), BSD
• Service Area:Worldwide
• Access Policy:Open Access
• Server Contact:Tanner Ryan

Roughtime Service

This server also provides secure Roughtime service. It is monitored and maintained at the same service level as the NTP service provided. The time is synchronized with stratum 1 upstreams.

Address:

time.0xt.ca:2002
ED25519 Public Key:
iBVjxg/1j7y1+kQUTBYdTabxCppesU/07D4PMDJk2WA=
The public key may also be fetched by performing a DNS TXT request to time.0xt.ca.
$ dig TXT time.0xt.ca +short
"iBVjxg/1j7y1+kQUTBYdTabxCppesU/07D4PMDJk2WA="

Here is a valid ecosystem.json file to use Roughtime provided by this server.

{
  "servers": [
    {
      "name": "time.0xt.ca",
      "publicKeyType": "ed25519",
      "publicKey": "iBVjxg/1j7y1+kQUTBYdTabxCppesU/07D4PMDJk2WA=",
      "addresses": [
        {
          "protocol": "udp",
          "address": "time.0xt.ca:2002"
        }
      ]
    }
  ]
}

Multiple servers are recommended. Here is a community contributed list provided by Cloudflare.

Upstream Providers

I would like to thank all of the NTP upstreams that keep Caesium ticking (literally):

I would also like to thank Linode for providing rock solid hosting and network connectivity.


NTP Utilization

The number of incoming NTP requests and outgoing responses. A one second packet capture is performed every 5 minutes.

NTP Utilization graph

Network Utilization

The bandwidth utilization generated from the NTP requests and responses. A one second packet capture is performed every 5 minutes.

Network Utilization graph

System Time

The difference between the system clock and synchronized UTC. A positive value indicates that the system clock is ahead of UTC. A negative value indicates that the system clock is behind.

System Time graph

Last Offset

The estimated system clock offset on the last clock update. A positive value indicates that the system clock is ahead of UTC. A negative value indicates that the system clock is behind.

Last Offset graph

Root Mean Square Offset

The long-term average of the offset value.

RMS Offset graph

Frequency

The rate by which the system clock would be wrong if correction was not applied. A positive value indicates that the system clock would be running faster without frequency correction. A negative value indicates that the system clock would be running slower.

Frequency graph

Residual Frequency

The difference between the weighted stratum 1 upstreams and the system frequency. A positive value indcates that the system clock frequency is being increased to match UTC time, correcting a slow clock. A negative value indicates that the system clock frequency is being decreased, correcting a fast clock.

Residual Frequency graph

Skew

The estimated error bound on the frequency. A lower value indicates a greater system clock frequency precision.

Skew graph

Root Delay

The total network path delays to the stratum 1 upstreams. A lower value results in greater system clock accuracy.

Root Delay graph

Root Dispersion

The total dispersion accumulated through root delays, statistical variation, and clock resolution. A lower value indicates a greater system clock accuracy.

Root Dispersion graph

Statistical Accuracy

The absolute error bound on the system clock's accuracy. This takes into consideration the system time offset, root delay, and root dispersion. This indicates the accuracy of the stratum 2 NTP service that time.0xt.ca is currently offering.

Statistical Accuracy graph