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)
Mon 13 Jul 22:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 34 +720us[ +720us] +/- 6553us ^* 2A10-3781-08Cc.connected> 2 10 377 696 +404us[ +596us] +/- 6313us ^- ntp-public-2.oma.be 2 7 377 10 +1194us[+1194us] +/- 31ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 332 -2820us[-2820us] +/- 10ms ^+ d54c70bd3.static.telenet> 1 10 377 146 +5635us[+5635us] +/- 11ms ^? 82-64-171-216.subs.proxa> 0 10 0 - +0ns[ +0ns] +/- 0ns
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Mon 13 Jul 22:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 126 -39us[ -365us] +/- 7271us ^- time.fu-berlin.de 1 10 377 425 -182us[ -508us] +/- 59ms ^- ntp1.hetzner.de 2 8 377 49 -337us[ -337us] +/- 32ms ^- ntp2.hetzner.de 2 10 377 1022 -111us[ -434us] +/- 40ms ^- ntp3.hetzner.de 2 10 377 579 -355us[ -680us] +/- 31ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Mon 13 Jul 22:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 944 +186us[ +310us] +/- 8197us ^- time.fu-berlin.de 1 9 377 307 +93us[ +93us] +/- 62ms ^+ ntp1.hetzner.de 2 9 377 200 -80us[ -80us] +/- 31ms ^- ntp2.hetzner.de 2 8 377 25 -75us[ -75us] +/- 29ms ^- ntp3.hetzner.de 2 10 377 998 -66us[ +56us] +/- 23ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Mon 13 Jul 22:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 91 +225us[ +225us] +/- 3795us ^* time1.esa.int 1 9 377 223 +119us[ +150us] +/- 3524us ^+ ntp1.time.nl 1 9 377 223 -7952ns[ +23us] +/- 4787us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Mon 13 Jul 22:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 178 -1354us[-1247us] +/- 8394us ^- time.fu-berlin.de 1 9 377 53 -234us[ -234us] +/- 65ms ^+ ntp1.hetzner.de 2 8 377 89 -459us[ -459us] +/- 32ms ^- ntp2.hetzner.de 2 9 377 440 -406us[ -303us] +/- 24ms ^- ntp3.hetzner.de 2 10 377 705 -500us[ -401us] +/- 29ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Mon 13 Jul 22:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 446 -1792us[-1792us] +/- 25ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 514 +21us[ +47us] +/- 7176us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Mon 13 Jul 22:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 317 27m -262us[ -281us] +/- 7981us ^- time.fu-berlin.de 1 10 377 127 -200us[ -200us] +/- 64ms ^- ntp1.hetzner.de 2 9 377 507 -409us[ -409us] +/- 26ms ^- ntp2.hetzner.de 2 10 377 318 -316us[ -316us] +/- 24ms ^- ntp3.hetzner.de 2 8 377 247 -336us[ -336us] +/- 34ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Mon 13 Jul 22:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 8 377 143 -2776us[-2818us] +/- 31ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 124 -41us[ -84us] +/- 6893us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Mon 13 Jul 22:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 244 -424us[ -424us] +/- 12ms ^+ 2A10-3781-08cC.connected> 2 9 377 223 -565us[ -565us] +/- 12ms ^- ntp-public-2.oma.be 2 9 377 446 -3019us[-3144us] +/- 26ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 445 -110us[ -235us] +/- 6893us ^+ d54c70bd3.static.telenet> 1 10 377 912 +3762us[+3655us] +/- 9846us ^? 82-64-171-216.subs.proxa> 0 10 0 - +0ns[ +0ns] +/- 0ns
Current performance for ntp22.linocomm.net (Paris, FR)
Mon 13 Jul 22:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 715 -52us[ +524us] +/- 11ms ^+ 2A10-3781-08cC.connected> 2 10 377 583 -1763us[-1763us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 172 -1201us[-1201us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 691 +489us[+1069us] +/- 7928us
Current performance for ntp23.linocomm.net (Paris, FR)
Mon 13 Jul 22:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 314 +693us[ +693us] +/- 15ms ^+ 2A10-3781-08cC.connected> 2 10 377 996 +305us[ +404us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 154 +2164us[+2164us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 834 +519us[ +634us] +/- 7847us
Current performance for ntp24.linocomm.net (Paris, FR)
Mon 13 Jul 22:28:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 372 +400us[+1198us] +/- 15ms ^+ 2a10-3781-08cC.connected> 2 10 377 498 +271us[+1031us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 597 +642us[+1372us] +/- 27ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 274 +586us[+1415us] +/- 8017us ^+ d54c70bd3.static.telenet> 1 10 377 584 +4618us[+5352us] +/- 12ms ^? 82-64-171-216.subs.proxa> 0 10 0 - +0ns[ +0ns] +/- 0ns
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Mon 13 Jul 22:28:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 535 -133us[ +203us] +/- 7994us ^- time.fu-berlin.de 1 10 377 818 -309us[ +27us] +/- 69ms ^- ntp1.hetzner.de 2 10 377 591 -449us[ -113us] +/- 25ms ^- ntp2.hetzner.de 2 8 377 17 -305us[ -305us] +/- 29ms ^- ntp3.hetzner.de 2 8 377 43 -313us[ -313us] +/- 37ms