NTP internet time servers at linocomm.net
You may delay, but time will not.Benjamin Franklin (1706-1790)
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)
Thu 9 Jul 17:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 478 +835us[ +734us] +/- 6782us ^* 2A10-3781-08cc.connected> 2 9 377 358 +812us[ +713us] +/- 6437us ^- ntp-public-2.oma.be 2 8 377 64 +563us[ +563us] +/- 19ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 709 -3091us[-3195us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 191 +5194us[+5194us] +/- 10ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 703 +1247us[+1143us] +/- 9380us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Thu 9 Jul 17:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 139 -1742us[-2263us] +/- 9207us ^- time.fu-berlin.de 1 10 377 970 +5282ns[ -410us] +/- 62ms ^- ntp1.hetzner.de 2 8 377 184 -70us[ -586us] +/- 23ms ^- ntp2.hetzner.de 2 10 377 1017 -159us[ -569us] +/- 25ms ^- ntp3.hetzner.de 2 10 377 586 -57us[ -521us] +/- 45ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Thu 9 Jul 17:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 38 -987us[-1027us] +/- 8916us ^- time.fu-berlin.de 1 10 377 926 -333us[ -390us] +/- 63ms ^- ntp1.hetzner.de 2 10 377 566 -241us[ -291us] +/- 19ms ^+ ntp2.hetzner.de 2 9 377 156 -576us[ -618us] +/- 15ms ^- ntp3.hetzner.de 2 9 377 388 -656us[ -703us] +/- 48ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Thu 9 Jul 17:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 943 -27us[ -246us] +/- 3507us ^* time1.esa.int 1 9 377 48 -338us[ -369us] +/- 3536us ^+ ntp1.time.nl 1 10 377 757 -2379us[-2612us] +/- 7583us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Thu 9 Jul 17:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 22m +39us[ +64us] +/- 7342us ^- time.fu-berlin.de 1 9 377 263 +90us[ +90us] +/- 57ms ^- ntp1.hetzner.de 2 8 377 36 +266us[ +266us] +/- 25ms ^+ ntp2.hetzner.de 2 10 377 384 -103us[ -103us] +/- 21ms ^- ntp3.hetzner.de 2 10 377 271 +326us[ +326us] +/- 50ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Thu 9 Jul 17:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 1007 -1710us[-1696us] +/- 39ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 66 +2734ns[ +16us] +/- 7121us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Thu 9 Jul 17:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 728 -877us[ -896us] +/- 8379us ^- time.fu-berlin.de 1 10 377 85 -633us[ -633us] +/- 60ms ^- ntp1.hetzner.de 2 9 377 317 -579us[ -579us] +/- 22ms ^- ntp2.hetzner.de 2 8 377 194 -755us[ -755us] +/- 15ms ^- ntp3.hetzner.de 2 10 377 849 -540us[ -560us] +/- 40ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Thu 9 Jul 17:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 1011 -2803us[-2783us] +/- 40ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 428 +14us[ +22us] +/- 6921us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Thu 9 Jul 17:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 26 -17us[ -17us] +/- 11ms ^+ 2a10-3781-08cC.connected> 2 9 377 189 +2357ns[+2357ns] +/- 12ms ^- ntp-public-2.oma.be 2 9 377 201 -3196us[-3196us] +/- 19ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 166 -460us[ -460us] +/- 7057us ^* d54c70bd3.static.telenet> 1 10 377 33m +4753us[+4792us] +/- 9843us ^+ 82-64-45-50.subs.proxad.> 1 10 377 842 +93us[ +93us] +/- 7595us
Current performance for ntp22.linocomm.net (Paris, FR)
Thu 9 Jul 17:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 848 +247us[ +328us] +/- 11ms ^+ 2a10-3781-08cC.connected> 2 10 377 983 +77us[ +158us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 387 -186us[ -102us] +/- 19ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 141 -147us[ -61us] +/- 7907us
Current performance for ntp23.linocomm.net (Paris, FR)
Thu 9 Jul 17:04:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 425 -86us[ -86us] +/- 11ms ^+ 2A10-3781-08CC.connected> 2 10 377 859 -1471us[-1471us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 314 -1908us[-1908us] +/- 21ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 435 +288us[ +288us] +/- 8009us
Current performance for ntp24.linocomm.net (Paris, FR)
Thu 9 Jul 17:04:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 321 -323us[ -323us] +/- 11ms ^+ 2A10-3781-08cc.connected> 2 10 377 1038 -2110us[-1999us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 647 -549us[ -549us] +/- 29ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 835 -223us[ -223us] +/- 8035us ^+ d54c70bd3.static.telenet> 1 10 377 703 +3654us[+3654us] +/- 10ms ^* 82-64-45-50.subs.proxad.> 1 10 377 884 +20us[ +134us] +/- 5436us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Thu 9 Jul 17:04:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 27m -1413us[-1431us] +/- 8836us ^- time.fu-berlin.de 1 10 377 870 -872us[ -872us] +/- 64ms ^- ntp1.hetzner.de 2 9 377 159 -859us[ -859us] +/- 25ms ^- ntp2.hetzner.de 2 8 377 140 -1093us[-1093us] +/- 15ms ^- ntp3.hetzner.de 2 9 377 143 -864us[ -864us] +/- 51ms