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 (Amsterdam, NL)

NTP1 error
Sat 13 Jun 12:58:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* erquy.linocomm.net            2  10   377   296   +184us[ +236us] +/- 6888us
^+ 2A10-3781-08Cc.connected>     2  10   277   223   +571us[ +571us] +/- 6902us
^- ntp-public-2.oma.be           2  10   277   208   +450us[ +450us] +/-   23ms
^+ ntp0.rrze.uni-erlangen.de     1  10   377   853  -3770us[-3719us] +/-   11ms
^+ d54c70bd3.static.telenet>     1  10   377   868  +3792us[+3843us] +/- 8726us
^+ 82-64-45-50.subs.proxad.>     1  10   377   298   +881us[ +933us] +/- 9527us

Current performance for ntp2.linocomm.net (Nuremberg, DE)

NTP4 error
Sat 13 Jun 12:58:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377  1021  +2997ns[  +25us] +/- 9511us
^- time.fu-berlin.de             1   9   377   354   +329us[ +329us] +/-   66ms
^+ ntp1.hetzner.de               2  10   377   811   +407us[ +407us] +/-   14ms
^- ntp2.hetzner.de               2  10   377   355   +496us[ +496us] +/-   16ms
^+ ntp3.hetzner.de               2  10   377   672   +329us[ +329us] +/-   33ms

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

NTP4 error
Sat 13 Jun 12:58:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   280   -592us[ -695us] +/-   10ms
^- time.fu-berlin.de             1  10   377  1013   -458us[ -525us] +/-   72ms
^+ ntp1.hetzner.de               2  10   377   301   -314us[ -416us] +/-   22ms
^- ntp2.hetzner.de               2   9   377    60   -278us[ -278us] +/-   19ms
^- ntp3.hetzner.de               2   9   377   311   -375us[ -477us] +/-   28ms

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

NTP4 error
Sat 13 Jun 12:58:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ ntp0.nl.uu.net                1  10   377   796    +50us[  -16us] +/- 3896us
^* time1.esa.int                 1  10   377    94   -260us[ -330us] +/- 3445us
^+ ntp1.time.nl                  1   9   377   100   -247us[ -317us] +/- 4312us

Current performance for ntp5.linocomm.net (Paris, FR)

NTP5 error
Sun  7 Jun 08:34:01 UTC 2026

Current performance for ntp9.linocomm.net (Nuremberg, DE)

NTP9 error
Sat 13 Jun 12:58:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   359   -334us[ -398us] +/- 8899us
^- time.fu-berlin.de             1  10   377   20m   -484us[ -543us] +/-   68ms
^- ntp1.hetzner.de               2  10   377   575   -374us[ -436us] +/-   17ms
^- ntp2.hetzner.de               2   9   377   143   -310us[ -310us] +/-   19ms
^- ntp3.hetzner.de               2  10   377   801  -2036us[-2097us] +/-   33ms

Current performance for ntp16.linocomm.net (Gravelines, FR)

NTP16 error
Sat 13 Jun 12:58:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^- ntp-public-2.oma.be           2   7   377    30  -1343us[-1343us] +/-   27ms
^* ntp0.rrze.uni-erlangen.de     1  10   377   958    -34us[  -52us] +/- 9241us

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

NTP17 error
Sat 13 Jun 12:58:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1   8   377   52m  -4962us[-3402us] +/- 9793us
^- time.fu-berlin.de             1  10   377   375  -4981us[-4981us] +/-   66ms
^- ntp1.hetzner.de               2  10   377   958  -4881us[-4881us] +/-   12ms
^- ntp2.hetzner.de               2   9   377   443  -4923us[-4923us] +/-   30ms
^- ntp3.hetzner.de               2   9   377   190  -5062us[-5062us] +/-   29ms

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

NTP18 error
Sat 13 Jun 12:58:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ ntp-public-2.oma.be           2  10   377   758  -1190us[-1208us] +/-   32ms
^* ntp0.rrze.uni-erlangen.de     1  10   377   695   +420us[ +403us] +/- 9201us

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

NTP20 error
Sat 13 Jun 12:58:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377  1017   -691us[ -681us] +/-   10ms
^- time.fu-berlin.de             1  10   377   583   -147us[ -147us] +/-   63ms
^- ntp1.hetzner.de               2   8   377   236    -12us[  -12us] +/-   13ms
^- ntp2.hetzner.de               2   9   377   233    -48us[  -48us] +/-   16ms
^+ ntp3.hetzner.de               2  10   377   542   -186us[ -186us] +/-   24ms

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

NTP21 error
Sat 13 Jun 12:58:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   221    +72us[  +72us] +/- 9638us
^+ 2a10-3781-08Cc.connected>     2   9   377   488   +256us[ +256us] +/- 9598us
^- ntp-public-2.oma.be           2  10   377   852  -1811us[-1864us] +/-   30ms
^+ ntp0.rrze.uni-erlangen.de     1  10   377   232   -242us[ -242us] +/- 8816us
^+ d54c70bd3.static.telenet>     1  10   377   238  +3483us[+3483us] +/- 9134us
^* 82-64-45-50.subs.proxad.>     1  10   377   787   -101us[ -154us] +/- 7542us

Current performance for ntp22.linocomm.net (Paris, FR)

NTP22 error
Sat 13 Jun 12:58:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   208   -402us[ -402us] +/-   11ms
^+ 2A10-3781-08cc.connected>     2   9   377   178  -1876us[-1876us] +/-   13ms
^- ntp-public-2.oma.be           2  10   377   217   -182us[ -182us] +/-   28ms
^* ntp0.rrze.uni-erlangen.de     1   9   377   504   -113us[+3152ns] +/- 8230us

Current performance for ntp23.linocomm.net (Paris, FR)

NTP23 error
Sat 13 Jun 12:58:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377    12  +1632us[+1632us] +/-   13ms
^+ 2a10-3781-08cc.connected>     2  10   377   545    -43us[  +26us] +/-   11ms
^- ntp-public-2.oma.be           2  10   377    20  -1717us[-1717us] +/-   32ms
^* ntp0.rrze.uni-erlangen.de     1   9   377   484   -244us[ -174us] +/- 8038us

Current performance for ntp24.linocomm.net (Paris, FR)

NTP24 error
Sat 13 Jun 12:58:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   779   -313us[ -313us] +/-   11ms
^? 2a10-3781-08cc.connected>     0  10     0     -     +0ns[   +0ns] +/-    0ns
^- ntp-public-2.oma.be           2  10   377   814  +1158us[+1140us] +/-   36ms
^+ ntp0.rrze.uni-erlangen.de     1  10   377   241   -572us[ -572us] +/- 7875us
^+ d54c70bd3.static.telenet>     1  10   377   812  +3616us[+3599us] +/-   11ms
^* 82-64-45-50.subs.proxad.>     1  10   377   795   -193us[ -211us] +/- 5508us

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

NTP25 error
Sat 13 Jun 12:58:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   818   +137us[ +117us] +/- 9496us
^- time.fu-berlin.de             1  10   377   743   -379us[ -379us] +/-   60ms
^- ntp1.hetzner.de               2  10   377  1018   -179us[ -193us] +/-   11ms
^+ ntp2.hetzner.de               2   8   377   153   -295us[ -295us] +/-   18ms
^- ntp3.hetzner.de               2   9   377   483   -414us[ -414us] +/-   25ms