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 18:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   368   +460us[ +460us] +/- 7549us
^+ 2A10-3781-08CC.connected>     2  10   377   353   +559us[ +559us] +/- 7452us
^- ntp-public-2.oma.be           2  10   377   272   +190us[ +190us] +/-   24ms
^+ ntp0.rrze.uni-erlangen.de     1  10   377   945  -3989us[-3989us] +/-   11ms
^* d54c70bd3.static.telenet>     1  10   377   992  +3949us[+3937us] +/- 9698us
^+ 82-64-45-50.subs.proxad.>     1  10   377   407   +773us[ +773us] +/- 9771us

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

NTP4 error
Sat 13 Jun 18:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   114  -6477ns[  +16us] +/- 9762us
^- time.fu-berlin.de             1  10   377   33m   -346us[ -368us] +/-   61ms
^+ ntp1.hetzner.de               2   9   377   900   -120us[  -91us] +/-   28ms
^+ ntp2.hetzner.de               2  10   377   25m   -246us[ -265us] +/-   47ms
^- ntp3.hetzner.de               2  10   377   805    +51us[  +80us] +/-   15ms

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

NTP4 error
Sat 13 Jun 18:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   393   -834us[ -850us] +/-   11ms
^- time.fu-berlin.de             1  10   377   793   -219us[ -235us] +/-   64ms
^+ ntp1.hetzner.de               2   9   377   460   -236us[ -252us] +/-   35ms
^+ ntp2.hetzner.de               2   8   377    25   -469us[ -469us] +/-   28ms
^- ntp3.hetzner.de               2  10   377   543   +209us[ +193us] +/-   17ms

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

NTP4 error
Sat 13 Jun 18:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ ntp0.nl.uu.net                1  10   377   916   +126us[ -154us] +/- 3620us
^* time1.esa.int                 1  10   377   200   -179us[ -490us] +/- 3446us
^+ ntp1.time.nl                  1   9   377   165   -156us[ -156us] +/- 4607us

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 18:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   505   -502us[ -594us] +/- 9187us
^- time.fu-berlin.de             1  10   377   265  -1771us[-1771us] +/-   72ms
^- ntp1.hetzner.de               2  10   377   160   -539us[ -539us] +/-   39ms
^- ntp2.hetzner.de               2   9   377   238   -818us[ -818us] +/-   26ms
^+ ntp3.hetzner.de               2  10   377   890  -1246us[-1337us] +/-   23ms

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

NTP16 error
Sat 13 Jun 18:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^- ntp-public-2.oma.be           2  10   377   236  -1313us[-1387us] +/-   26ms
^* ntp0.rrze.uni-erlangen.de     1  10   377    46    -50us[ -124us] +/- 9261us

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

NTP17 error
Sat 13 Jun 18:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   27m  -4958us[-4910us] +/- 9953us
^- time.fu-berlin.de             1  10   377   471  -4796us[-4796us] +/-   69ms
^- ntp1.hetzner.de               2   8   377    15  -4751us[-4751us] +/-   42ms
^- ntp2.hetzner.de               2  10   377    67  -4983us[-4983us] +/-   28ms
^- ntp3.hetzner.de               2  10   377   809  -4612us[-4612us] +/-   13ms

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

NTP18 error
Sat 13 Jun 18:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ ntp-public-2.oma.be           2  10   377   843  -1062us[-1058us] +/-   42ms
^* ntp0.rrze.uni-erlangen.de     1  10   377   821   +433us[ +438us] +/- 9005us

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

NTP20 error
Sat 13 Jun 18:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377    88    +41us[  +47us] +/- 9752us
^- time.fu-berlin.de             1  10   377   661   -247us[ -245us] +/-   66ms
^- ntp1.hetzner.de               2   7   377    73   -165us[ -165us] +/-   41ms
^+ ntp2.hetzner.de               2   8   377   115   -394us[ -388us] +/-   27ms
^+ ntp3.hetzner.de               2  10   377   645    -54us[  -51us] +/-   16ms

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

NTP21 error
Sat 13 Jun 18:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   308   +720us[ +720us] +/- 9788us
^+ 2a10-3781-08cC.connected>     2  10   377    59   +623us[ +623us] +/- 8865us
^- ntp-public-2.oma.be           2   9   377   385  -1000us[-1000us] +/-   23ms
^+ ntp0.rrze.uni-erlangen.de     1  10   377   335   +560us[ +560us] +/- 8896us
^* d54c70bd3.static.telenet>     1  10   377   22m  +4813us[+4981us] +/- 9353us
^+ 82-64-45-50.subs.proxad.>     1  10   377   884   +601us[ +601us] +/- 7421us

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

NTP22 error
Sat 13 Jun 18:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   314   -105us[ -105us] +/-   12ms
^+ 2A10-3781-08CC.connected>     2  10   377   819   -144us[ -163us] +/-   11ms
^- ntp-public-2.oma.be           2  10   377   309   -130us[ -130us] +/-   28ms
^* ntp0.rrze.uni-erlangen.de     1  10   377   566   -255us[ -275us] +/- 8247us

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

NTP23 error
Sat 13 Jun 18:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   108  -2414us[-2515us] +/-   13ms
^+ 2A10-3781-08Cc.connected>     2  10   377   637  -1818us[-1925us] +/-   13ms
^- ntp-public-2.oma.be           2  10   377   131    -81us[ -183us] +/-   31ms
^* ntp0.rrze.uni-erlangen.de     1  10   377    76   -494us[ -595us] +/- 8085us

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

NTP24 error
Sat 13 Jun 18:10:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   914  -2012us[-2064us] +/-   13ms
^? 2a10-3781-08cc.connected>     0  10     0     -     +0ns[   +0ns] +/-    0ns
^- ntp-public-2.oma.be           2  10   377   891  +1227us[+1227us] +/-   47ms
^+ ntp0.rrze.uni-erlangen.de     1  10   377   374   -280us[ -280us] +/- 7975us
^+ d54c70bd3.static.telenet>     1  10   377   885  +3677us[+3677us] +/-   10ms
^* 82-64-45-50.subs.proxad.>     1  10   377   899   +174us[ +122us] +/- 5674us

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

NTP25 error
Sat 13 Jun 18:10:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   916   -341us[ -337us] +/- 9730us
^- time.fu-berlin.de             1  10   377   871   -557us[ -557us] +/-   63ms
^- ntp1.hetzner.de               2   8   377   109   -489us[ -489us] +/-   40ms
^- ntp2.hetzner.de               2   8   377   204   -715us[ -715us] +/-   25ms
^- ntp3.hetzner.de               2  10   377   506   -318us[ -318us] +/-   18ms