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
Thu 11 Jun 15:28:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   735  +1027us[+1027us] +/- 6573us
^* 2a10-3781-08cc.connected>     2  10   377  1001   +864us[+1013us] +/- 6234us
^- ntp-public-2.oma.be           2   9   377   297  +1315us[+1315us] +/-   38ms
^+ ntp0.rrze.uni-erlangen.de     1   9   377   408  -3171us[-3171us] +/-   11ms
^+ d54c70bd3.static.telenet>     1  10   377   442  +5515us[+5515us] +/-   12ms
^+ 82-64-45-50.subs.proxad.>     1  10   377   770  +1141us[+1141us] +/- 9484us

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

NTP4 error
Thu 11 Jun 15:28:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   373   963    +33us[ +782us] +/- 6648us
^- time.fu-berlin.de             1  10   377   33m  -1429us[ -557us] +/-   62ms
^- ntp1.hetzner.de               2  10   377   947  -1084us[-1084us] +/-   33ms
^- ntp2.hetzner.de               2  10   377   311  -1309us[-1309us] +/-   30ms
^- ntp3.hetzner.de               2  10   377   336  -1006us[-1006us] +/-   21ms

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

NTP4 error
Thu 11 Jun 15:28:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   422  -1817us[-1833us] +/- 9545us
^- time.fu-berlin.de             1  10   377   26m   -344us[ -464us] +/-   69ms
^- ntp1.hetzner.de               2  10   377   920   -462us[ -475us] +/-   34ms
^- ntp2.hetzner.de               2  10   377   216   -618us[ -618us] +/-   30ms
^- ntp3.hetzner.de               2   9   377    64   -625us[ -625us] +/-   24ms

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

NTP4 error
Thu 11 Jun 15:28:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ ntp0.nl.uu.net                1  10   377   353   -177us[ -196us] +/- 3950us
^* time1.esa.int                 1  10   377   108   -282us[ -302us] +/- 3595us
^+ ntp1.time.nl                  1  10   377   622   -484us[ -502us] +/- 4735us

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
Thu 11 Jun 15:28:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377  1093   -468us[ -451us] +/- 7787us
^- time.fu-berlin.de             1  10   377   771   -366us[ -366us] +/-   57ms
^- ntp1.hetzner.de               2  10   377   223   -207us[ -207us] +/-   29ms
^- ntp2.hetzner.de               2  10   377   776   -204us[ -204us] +/-   31ms
^- ntp3.hetzner.de               2  10   377   507    -85us[  -85us] +/-   19ms

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

NTP16 error
Thu 11 Jun 15:28:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^- ntp-public-2.oma.be           2  10   377    48   -886us[ -886us] +/-   43ms
^* ntp0.rrze.uni-erlangen.de     1  10   377   980    +53us[ +218us] +/- 9221us

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

NTP17 error
Thu 11 Jun 15:28:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   375   227   -936us[ -933us] +/- 7979us
^- time.fu-berlin.de             1  10   377   700  -1121us[-1118us] +/-   59ms
^- ntp1.hetzner.de               2   9   377   497  -1076us[-1073us] +/-   26ms
^- ntp2.hetzner.de               2  10   377   618  -1245us[-1242us] +/-   32ms
^- ntp3.hetzner.de               2   9   377   361  -1068us[-1065us] +/-   20ms

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

NTP18 error
Thu 11 Jun 15:28:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^- ntp-public-2.oma.be           2   9   377   269  -1370us[-1370us] +/-   39ms
^* ntp0.rrze.uni-erlangen.de     1   9   377   348   +117us[ +176us] +/- 8890us

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

NTP20 error
Thu 11 Jun 15:28:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   336   -431us[ -426us] +/- 8328us
^- time.fu-berlin.de             1  10   377   433   -506us[ -501us] +/-   63ms
^- ntp1.hetzner.de               2  10   377   291   -435us[ -435us] +/-   29ms
^- ntp2.hetzner.de               2   9   377   365   -581us[ -576us] +/-   36ms
^- ntp3.hetzner.de               2   9   377    13   -446us[ -446us] +/-   14ms

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

NTP21 error
Thu 11 Jun 15:28:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   600   +712us[ +712us] +/- 9124us
^+ 2a10-3781-08cC.connected>     2  10   377   486   +918us[ +918us] +/- 9488us
^- ntp-public-2.oma.be           2   9   377   457   -655us[ -655us] +/-   36ms
^+ ntp0.rrze.uni-erlangen.de     1  10   377   512   +865us[ +865us] +/- 9131us
^* d54c70bd3.static.telenet>     1  10   377   41m  +5164us[+5281us] +/- 9314us
^+ 82-64-45-50.subs.proxad.>     1  10   377   279   +954us[ +954us] +/- 7263us

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

NTP22 error
Thu 11 Jun 15:28:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   870  -1365us[-1365us] +/-   12ms
^+ 2a10-3781-08cc.connected>     2  10   377   837  -1468us[-1468us] +/-   13ms
^- ntp-public-2.oma.be           2  10   377   461   +299us[ +299us] +/-   40ms
^* ntp0.rrze.uni-erlangen.de     1  10   377   890   +384us[ +334us] +/- 8077us

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

NTP23 error
Thu 11 Jun 15:28:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   790  +1668us[+1668us] +/-   13ms
^? 2a10-3781-08cc.connected>     0  10     0     -     +0ns[   +0ns] +/-    0ns
^- ntp-public-2.oma.be           2  10   377   119  -1194us[-1194us] +/-   47ms
^* ntp0.rrze.uni-erlangen.de     1  10   377   916  -2517ns[  -59us] +/- 7926us

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

NTP24 error
Thu 11 Jun 15:28:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   802   -230us[ -184us] +/-   11ms
^+ 2A10-3781-08cc.connected>     2  10   377   933    -98us[  -53us] +/-   11ms
^- ntp-public-2.oma.be           2  10   377   983  -1610us[-1564us] +/-   34ms
^+ ntp0.rrze.uni-erlangen.de     1   9   377   305   -207us[ -207us] +/- 7995us
^+ d54c70bd3.static.telenet>     1  10   377   44m  +4547us[+4602us] +/-   13ms
^* 82-64-45-50.subs.proxad.>     1  10   377   477   +416us[ +462us] +/- 5523us

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

NTP25 error
Thu 11 Jun 15:28:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   937  -1182us[-1177us] +/- 8059us
^- time.fu-berlin.de             1  10   377    48  -1193us[-1193us] +/-   61ms
^- ntp1.hetzner.de               2  10   377   676  -1169us[-1169us] +/-   23ms
^- ntp2.hetzner.de               2   9   377   423  -1274us[-1274us] +/-   35ms
^- ntp3.hetzner.de               2   9   377   247  -1115us[-1115us] +/-   21ms