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
Wed 17 Jun 16:55:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   603   +296us[ +296us] +/- 6344us
^+ 2a10-3781-08CC.connected>     2   9   377   467   +446us[ +446us] +/- 6355us
^- ntp-public-2.oma.be           2  10   377    16   +738us[ +738us] +/-   27ms
^+ ntp0.rrze.uni-erlangen.de     1   9   377   184  -3841us[-3841us] +/-   11ms
^* d54c70bd3.static.telenet>     1  10   377   783  +2670us[+2894us] +/- 9236us
^+ 82-64-45-50.subs.proxad.>     1  10   377   136  +1010us[+1010us] +/- 9858us

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

NTP4 error
Wed 17 Jun 16:55:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   885  -1816us[-1816us] +/- 9023us
^- time.fu-berlin.de             1  10   377   735   -513us[ -513us] +/-   64ms
^- ntp1.hetzner.de               2   9   377   219   -210us[ -210us] +/-   28ms
^- ntp2.hetzner.de               2  10   377   723    +46us[  +46us] +/-   45ms
^- ntp3.hetzner.de               2  10   377   26m   -320us[ -326us] +/-   29ms

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

NTP4 error
Wed 17 Jun 16:55:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   373   -151us[ -164us] +/- 7957us
^- time.fu-berlin.de             1  10   377   576    -97us[ -109us] +/-   67ms
^- ntp1.hetzner.de               2  10   377   674   -125us[ -137us] +/-   34ms
^- ntp2.hetzner.de               2   8   377   224    -71us[  -71us] +/-   24ms
^+ ntp3.hetzner.de               2  10   377   171    -71us[  -71us] +/-   34ms

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

NTP4 error
Wed 17 Jun 16:55:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ ntp0.nl.uu.net                1  10   377   135    +12us[  +12us] +/- 3740us
^* time1.esa.int                 1   9   377   287   -141us[ -186us] +/- 3367us
^+ ntp1.time.nl                  1   9   377   307   -293us[ -337us] +/- 4503us

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
Wed 17 Jun 16:55:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   108  -1691us[-1684us] +/- 8916us
^- time.fu-berlin.de             1   9   377   103    -17us[  -17us] +/-   58ms
^- ntp1.hetzner.de               2   8   377   233   -266us[ -259us] +/-   28ms
^- ntp2.hetzner.de               2   9   377   880    -62us[  -56us] +/-   43ms
^- ntp3.hetzner.de               2   9   377   955    -45us[  -39us] +/-   24ms

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

NTP16 error
Wed 17 Jun 16:55:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^- ntp-public-2.oma.be           2   9   377   331  -1019us[-1094us] +/-   23ms
^* ntp0.rrze.uni-erlangen.de     1   9   377   130    +15us[  -64us] +/- 9306us

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

NTP17 error
Wed 17 Jun 16:55:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   529   -382us[ -372us] +/- 8271us
^- time.fu-berlin.de             1  10   377   105   -178us[ -178us] +/-   59ms
^- ntp1.hetzner.de               2   9   377   349   -197us[ -197us] +/-   27ms
^- ntp2.hetzner.de               2   8   377   178    -64us[  -64us] +/-   24ms
^- ntp3.hetzner.de               2  10   377   511   -194us[ -194us] +/-   29ms

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

NTP18 error
Wed 17 Jun 16:55:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^- ntp-public-2.oma.be           2  10   377     6  -1379us[-1379us] +/-   28ms
^* ntp0.rrze.uni-erlangen.de     1  10   377   787    +26us[ +127us] +/- 9129us

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

NTP20 error
Wed 17 Jun 16:55:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   887   -208us[ -355us] +/- 7776us
^- time.fu-berlin.de             1  10   377   391   -320us[ -320us] +/-   70ms
^- ntp1.hetzner.de               2  10   377   769   -291us[ -291us] +/-   33ms
^- ntp2.hetzner.de               2   9   377   140   -156us[ -156us] +/-   25ms
^+ ntp3.hetzner.de               2   9   377   397   -196us[ -196us] +/-   31ms

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

NTP21 error
Wed 17 Jun 16:55:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2   9   377   404  -9936ns[-9936ns] +/- 9132us
^+ 2A10-3781-08CC.connected>     2  10   377   170   -187us[ -187us] +/- 8714us
^- ntp-public-2.oma.be           2  10   377   216  -1557us[-1557us] +/-   25ms
^+ ntp0.rrze.uni-erlangen.de     1  10   377   184   -103us[ -103us] +/- 9052us
^+ d54c70bd3.static.telenet>     1  10   377  1087  +2378us[+2275us] +/- 9268us
^* 82-64-45-50.subs.proxad.>     1  10   377   800    +52us[  -52us] +/- 7236us

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

NTP22 error
Wed 17 Jun 16:55:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   325  +1082us[+1087us] +/-   13ms
^+ 2A10-3781-08cc.connected>     2  10   377   782  -2563us[-2555us] +/-   12ms
^- ntp-public-2.oma.be           2  10   377   292   -166us[ -161us] +/-   27ms
^* ntp0.rrze.uni-erlangen.de     1  10   377    56   -494us[ -490us] +/- 8174us

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

NTP23 error
Wed 17 Jun 16:55:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   234   -632us[ -712us] +/-   11ms
^+ 2A10-3781-08cc.connected>     2  10   377   874   -124us[ -409us] +/-   11ms
^- ntp-public-2.oma.be           2  10   377   804   +353us[  +67us] +/-   19ms
^* ntp0.rrze.uni-erlangen.de     1  10   377    86   -214us[ -294us] +/- 7970us

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

NTP24 error
Wed 17 Jun 16:55:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   563   -542us[ -589us] +/-   11ms
^? 2a10-3781-08cc.connected>     0  10     0     -     +0ns[   +0ns] +/-    0ns
^- ntp-public-2.oma.be           2  10   377   728  +1282us[+1166us] +/-   22ms
^+ ntp0.rrze.uni-erlangen.de     1   9   377   130   -591us[ -591us] +/- 7767us
^+ d54c70bd3.static.telenet>     1  10   377   751  +5725us[+5609us] +/-   13ms
^* 82-64-45-50.subs.proxad.>     1   9   377   154   -117us[ -165us] +/- 5677us

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

NTP25 error
Wed 17 Jun 16:55:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   692   -490us[ -500us] +/- 7932us
^- time.fu-berlin.de             1  10   377   134   -540us[ -540us] +/-   58ms
^- ntp1.hetzner.de               2   8   377   161   -572us[ -572us] +/-   30ms
^- ntp2.hetzner.de               2   7   377    63   -399us[ -399us] +/-   26ms
^- ntp3.hetzner.de               2   9   377   385   -422us[ -422us] +/-   31ms