NTP internet time servers at linocomm.net

You may delay, but time will not.
Benjamin Franklin (1706-1790)

Nederlands

What is this all about?

Time is one of the most important things in modern society. Without time keeping, it would be difficult to arrange meetings, take the bus or train or be on time on a wedding ceremony. Not only humans rely on time. Every computer has an internal clock which is used when time stamping your email and documents, schedule your backups and warn you when you have an appointment. Therefore also computers should know the current time with some accuracy. To synchronize computers to known good time sources over the internet, the NTP protocol has been defined which allows to obtain the current time from internet time servers.

The servers ntp1.linocomm.net to ntp9.linocomm.net are such public internet time servers, operated by the internet services company Linoplan. The servers provide NTP services to NTP and SNTP clients on the internet. All time servers are at least stratum 2 servers, which means that the servers are directly connected to other time servers which take their time from a number of official reference clocks (atomic clock, radio clock, GPS or whatever) in different geographical regions. Time server ntp4.linocomm.net is a Stratum 1 server located in the Netherlands with its own reference clock. Time synchronisation with several upstream servers in different geographical regions gives redundancy when network failures occur. In practice this means that the time these servers provide are accurate within a few milliseconds. This is good enough for most private and commercial applications.

Server ntp1.linocomm.net is located in a data center in Almaty, Kazakhstan, which makes it the ideal time server for computers in Central Asia, but clients from all over the world are allowed to connect to this server. The only drawback is that distant clients might observe a few more milliseconds error in the received time signal compared to the time served by time servers closer to their location. Time server ntp5.linocomm.net is located in Las Vegas and serves North America. All other servers are located in Western Europe and are primarily intended for the EMEA area. Time server ntp4 is the most accurate in the network because it has its own timebase with a GPS+PPS receiver.

How do I connect to your time servers?

You can add one or more of the server names to your ntpd or chronyd configuration file. With recent versions of ntpd and chronyd you can use the pool directive which adds a pool of servers to the configuration. If you use the pool directive, use the name ntppool.linocomm.net as the domain name.

How well do your time servers perform?

The lists of upstream servers are refreshed every five minutes. The values in the columns delay, offset and jitter are in milliseconds. The delay is a measurement of the network delay when retrieving the time from the remote server. The offset is the current difference between the internal clock of our timeserver and the remote clock. Finally jitter gives the variation in the time difference between subsequent requests.

Current performance for ntp1.linocomm.net (Almaty, KZ)

NTP1 error
Tue 21 Jan 02:04:01 UTC 2025
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntp.nic.kz                    1  10   377    12  -1643us[-1653us] +/-   14ms
^- 80.93.187.13                  2  10   377   266  +1420us[+1410us] +/-   38ms

Current performance for ntp2.linocomm.net (Roubaix, FR)

NTP2 error
Tue 21 Jan 02:04:02 UTC 2025
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntp-main-1.oma.be             1  10   377   270  -2082ns[ +245us] +/- 3322us
^+ ntp0.rrze.uni-erlangen.de     1   9   377    92   +110us[ +110us] +/- 7417us

Current perfomance for ntp3.linocomm.net (Falkenstein, DE)

NTP3 error
Tue 21 Jan 02:04:02 UTC 2025
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   277   592   -133us[ -102us] +/- 8004us
^- time.fu-berlin.de             1  10   377   154   -362us[ -362us] +/-   58ms
^- ntp1.hetzner.de               2  10   377   858   -261us[ -231us] +/-   29ms
^- ntp2.hetzner.de               2   8   377    46   -231us[ -231us] +/-   35ms
^- ntp3.hetzner.de               2  10   377    28   -197us[ -197us] +/-   43ms

Current performance for ntp4.linocomm.net (Donkerbroek, NL)

NTP4 error
Tue 21 Jan 02:04:02 UTC 2025
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* time1.esa.int                 1  10   377   371   +181us[ +206us] +/- 4632us
^+ ntp1.time.nl                  1  10   377     7  -3458us[-3458us] +/- 9494us
^+ ntp0.nl.uu.net                1  10   377   477    +75us[ +100us] +/- 4619us

Current performance for ntp5.linocomm.net (Naaldwijk, NL)

NTP5 error
Tue 21 Jan 02:04:02 UTC 2025
506 Cannot talk to daemon

Current perfomance for ntp6.linocomm.net (Gravelines, FR)

NTP6 error
Tue 21 Jan 02:04:02 UTC 2025
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntp-main-1.oma.be             1  10   377   21m  -2017us[-2143us] +/- 4700us
^+ ntp0.rrze.uni-erlangen.de     1   9   377   469   -510us[ -510us] +/- 7241us

Current performance for ntp7.linocomm.net (Falkenstein, DE)

NTP7 error
Tue 21 Jan 02:04:02 UTC 2025
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   177   868   -372us[ -243us] +/- 8220us
^- time.fu-berlin.de             1  10   377   968   -712us[ -584us] +/-   58ms
^- ntp1.hetzner.de               2  10   377    68   -641us[ -641us] +/-   39ms
^- ntp2.hetzner.de               2  10   377   804   -646us[ -646us] +/-   24ms
^- ntp3.hetzner.de               2  10   377  1012   -615us[ -486us] +/-   28ms

Current perfomance for ntp8.linocomm.net (Roubaix, FR)

NTP8 error
Tue 21 Jan 02:04:02 UTC 2025
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntp-main-1.oma.be             1  10   377   904   -557us[ -524us] +/- 4422us
^+ ntp0.rrze.uni-erlangen.de     1  10   377   105  +1083us[+1083us] +/- 7110us

Current performance for ntp9.linocomm.net (Nürnberg, DE)

NTP9 error
Tue 21 Jan 02:04:02 UTC 2025
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   672   -561us[ -545us] +/- 7916us
^- time.fu-berlin.de             1  10   377   158   -588us[ -588us] +/-   58ms
^- ntp1.hetzner.de               2  10   377   992   -145us[ -129us] +/-   26ms
^- ntp2.hetzner.de               2  10   377   342   -204us[ -204us] +/-   32ms
^+ ntp3.hetzner.de               2  10   377   106   -314us[ -314us] +/-   43ms