time.sshlab.net
Server status
The guaranteed bound is the most the time could be off if every network delay were lopsided. The observed figures show how closely independent paths actually agree, which is usually a far better guide to real accuracy but is not a guarantee. The stated accuracy of time.sshlab.net is ±100 ms; the clock shown on this page is also limited by your own connection.
Usage
History
Requests per minute
Active clients (last hour)
Cross-check against Z&D servers (ms)
Root dispersion (ms)
Upstream time sources
| Server | State | Reach | Offset | ||
|---|---|---|---|---|---|
| Loading… | |||||
The server only adjusts its time when at least three NIST/USNO sources agree. time.ross and time.lan are independent Z&D servers it watches as a cross-check but never takes time from.
Use this server
server time.sshlab.net iburst ntsserver time.sshlab.net nts iburstNTP=time.sshlab.netw32tm /config /manualpeerlist:time.sshlab.net /syncfromflags:manual /updateAbout
| Hostname | time.sshlab.net |
| Protocols | NTS (RFC 8915) and NTP v4 |
| Ports | TCP 4460 (NTS-KE), UDP 123 (NTP), UDP 1123 (NTS) |
| Stratum | 2 |
| Accuracy | ±100 ms of UTC |
| Upstream | NIST Gaithersburg, Boulder & WWV; US Naval Observatory |
| Software | chrony |
| Operator | Z&D CA · ca@sshlab.net |
Time served is kept within ±100 ms of UTC, traceable to NIST and USNO; if that cannot be assured the status above shows unsynchronized. Free for public use on a best-effort basis, with no guarantee of availability. Please poll no more often than once every 64 seconds; clients that poll too fast are rate-limited. No client addresses are published here.