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:07:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* erquy.linocomm.net            2  10   377   340   +580us[ +678us] +/- 7184us
^+ 2a10-3781-08CC.connected>     2  10   367   270   +377us[ +377us] +/- 7319us
^- ntp-public-2.oma.be           2  10   367   270   +440us[ +440us] +/-   24ms
^+ ntp0.rrze.uni-erlangen.de     1  10   377   916  -3580us[-3484us] +/-   11ms
^+ d54c70bd3.static.telenet>     1  10   377   889  +4476us[+4572us] +/-   11ms
^+ 82-64-45-50.subs.proxad.>     1  10   377   338   +704us[ +704us] +/-   13ms

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

NTP4 error
Sat 13 Jun 12:07:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377    17   +161us[ +297us] +/- 9652us
^- time.fu-berlin.de             1   9   377   403    +44us[ +176us] +/-   65ms
^+ ntp1.hetzner.de               2  10   377   843   +846us[ +972us] +/-   24ms
^- ntp2.hetzner.de               2  10   377   386  -1307us[-1176us] +/-   25ms
^+ ntp3.hetzner.de               2  10   377   721   +186us[ +314us] +/-   27ms

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

NTP4 error
Sat 13 Jun 12:07:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   336   -632us[ -823us] +/-   10ms
^- time.fu-berlin.de             1  10   377    19   -588us[ -588us] +/-   71ms
^+ ntp1.hetzner.de               2  10   377   23m    +86us[ -103us] +/-   47ms
^- ntp2.hetzner.de               2   9   377   102   -477us[ -477us] +/-   26ms
^- ntp3.hetzner.de               2   9   377   891   -494us[ -684us] +/-   23ms

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

NTP4 error
Sat 13 Jun 12:07:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ ntp0.nl.uu.net                1  10   377   832   -446us[ -494us] +/- 3731us
^* time1.esa.int                 1  10   377   135    -44us[  -96us] +/- 3289us
^+ ntp1.time.nl                  1   9   377   151   -330us[ -382us] +/- 4560us

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:07:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   404   -670us[ -657us] +/- 9496us
^- time.fu-berlin.de             1  10   377   211   -821us[ -821us] +/-   68ms
^- ntp1.hetzner.de               2  10   377   605    -14us[ -803ns] +/-   20ms
^- ntp2.hetzner.de               2  10   377   188   -451us[ -451us] +/-   26ms
^- ntp3.hetzner.de               2  10   377   856   -514us[ -501us] +/-   25ms

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

NTP16 error
Sat 13 Jun 12:07:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^- ntp-public-2.oma.be           2   7   377    73  -1354us[-1354us] +/-   28ms
^* ntp0.rrze.uni-erlangen.de     1  10   377  1013  +3390ns[+5940ns] +/- 9257us

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

NTP17 error
Sat 13 Jun 12:07:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1   8   377    93  -4962us[-3402us] +/- 9793us
^- time.fu-berlin.de             1  10   377   420  -5031us[-3467us] +/-   65ms
^- ntp1.hetzner.de               2  10   377   997  -4387us[-2816us] +/-   22ms
^- ntp2.hetzner.de               2   8   377   231  -4869us[-3307us] +/-   24ms
^- ntp3.hetzner.de               2   9   377   226  -4987us[-3425us] +/-   33ms

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

NTP18 error
Sat 13 Jun 12:07:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ ntp-public-2.oma.be           2   9   377   277  -1097us[-1097us] +/-   25ms
^* ntp0.rrze.uni-erlangen.de     1  10   377   739   +398us[ +381us] +/- 9069us

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

NTP20 error
Sat 13 Jun 12:07:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377    21   -111us[ -104us] +/- 9584us
^- time.fu-berlin.de             1  10   377   612   -233us[ -227us] +/-   62ms
^- ntp1.hetzner.de               2   8   377    15   +308us[ +308us] +/-   25ms
^- ntp2.hetzner.de               2   6   377    18   -113us[ -113us] +/-   27ms
^+ ntp3.hetzner.de               2  10   377   592   -178us[ -171us] +/-   27ms

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

NTP21 error
Sat 13 Jun 12:07:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2   9   377   267   -155us[ -155us] +/-   10ms
^+ 2a10-3781-08CC.connected>     2   8   377    15   -509us[ -509us] +/- 8569us
^- ntp-public-2.oma.be           2  10   377   911  -2160us[-2107us] +/-   31ms
^+ ntp0.rrze.uni-erlangen.de     1  10   377   272   -533us[ -533us] +/- 9091us
^+ d54c70bd3.static.telenet>     1  10   377   262  +5089us[+5089us] +/-   10ms
^* 82-64-45-50.subs.proxad.>     1  10   377   853   -350us[ -298us] +/- 7386us

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

NTP22 error
Sat 13 Jun 12:07:07 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   177   267   -154us[ -220us] +/-   12ms
^+ 2A10-3781-08cc.connected>     2   9   377   236    +20us[  -47us] +/-   12ms
^- ntp-public-2.oma.be           2  10   377   243  +1260us[+1193us] +/-   31ms
^* ntp0.rrze.uni-erlangen.de     1   9   377    39   -170us[ -244us] +/- 7759us

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

NTP23 error
Sat 13 Jun 12:07:07 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   177    73   +993us[+1033us] +/-   12ms
^+ 2A10-3781-08cC.connected>     2   9   377    78   -205us[ -165us] +/-   10ms
^- ntp-public-2.oma.be           2  10   377    76  +1392us[+1431us] +/-   33ms
^* ntp0.rrze.uni-erlangen.de     1   8   377     7   -315us[ -276us] +/- 8019us

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

NTP24 error
Sat 13 Jun 12:07:07 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   809   -573us[ -573us] +/-   12ms
^? 2A10-3781-08cc.connected>     0  10     0     -     +0ns[   +0ns] +/-    0ns
^- ntp-public-2.oma.be           2  10   377   867   -521us[ -471us] +/-   36ms
^+ ntp0.rrze.uni-erlangen.de     1   9   377   292   -438us[ -438us] +/- 8077us
^+ d54c70bd3.static.telenet>     1  10   377   857  +3189us[+3189us] +/-   11ms
^* 82-64-45-50.subs.proxad.>     1  10   377   861   -136us[  -85us] +/- 5479us

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

NTP25 error
Sat 13 Jun 12:07:07 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   856   -140us[ -218us] +/- 9749us
^- time.fu-berlin.de             1  10   377   791   -299us[ -299us] +/-   60ms
^- ntp1.hetzner.de               2  10   377    14   +191us[ +191us] +/-   25ms
^+ ntp2.hetzner.de               2   7   377    78   -183us[ -183us] +/-   26ms
^- ntp3.hetzner.de               2   7   377    14   -329us[ -329us] +/-   36ms