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)
Tue 23 Jun 17:19:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 832 +876us[+1057us] +/- 7451us ^+ 2A10-3781-08cc.connected> 2 10 377 623 +483us[ +664us] +/- 7819us ^- ntp-public-2.oma.be 2 10 377 955 +334us[ +513us] +/- 49ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 501 -3510us[-3327us] +/- 11ms ^* d54c70bd3.static.telenet> 1 10 377 278 +3068us[+3252us] +/- 9865us ^+ 82-64-45-50.subs.proxad.> 1 10 377 722 -397us[ -216us] +/- 12ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Tue 23 Jun 17:19:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 357 649 -1358us[-1383us] +/- 8919us ^- time.fu-berlin.de 1 10 377 28m -382us[ -407us] +/- 64ms ^- ntp1.hetzner.de 2 9 377 585 -154us[ -154us] +/- 34ms ^- ntp2.hetzner.de 2 10 377 30m +39us[ +12us] +/- 30ms ^- ntp3.hetzner.de 2 10 377 20 +22us[ +22us] +/- 32ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Tue 23 Jun 17:19:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 846 +60us[ +83us] +/- 8028us ^- time.fu-berlin.de 1 9 377 455 -328us[ -328us] +/- 68ms ^- ntp1.hetzner.de 2 8 377 174 -619us[ -619us] +/- 42ms ^- ntp2.hetzner.de 2 7 377 61 -262us[ -262us] +/- 26ms ^+ ntp3.hetzner.de 2 8 377 146 +18us[ +18us] +/- 28ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Tue 23 Jun 17:19:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 9 377 442 -780us[ -907us] +/- 3738us ^* time1.esa.int 1 10 377 431 +4222us[+4095us] +/- 8352us ^+ ntp1.time.nl 1 8 377 102 -923us[ -923us] +/- 4418us
Current performance for ntp5.linocomm.net (Paris, FR)
Sun 7 Jun 08:34:01 UTC 2026
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Tue 23 Jun 17:19:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 357 296 -312us[ -248us] +/- 7769us ^- time.fu-berlin.de 1 10 377 91 -579us[ -579us] +/- 58ms ^- ntp1.hetzner.de 2 9 377 1088 -1203us[-1144us] +/- 27ms ^- ntp2.hetzner.de 2 7 377 100 -249us[ -249us] +/- 27ms ^- ntp3.hetzner.de 2 10 377 807 -1734us[-1674us] +/- 29ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Tue 23 Jun 17:19:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 8 377 253 -1350us[-1350us] +/- 20ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 284 +49us[ +210us] +/- 7210us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Tue 23 Jun 17:19:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 257 -171us[ -299us] +/- 7552us ^- time.fu-berlin.de 1 10 377 786 -425us[ -549us] +/- 63ms ^- ntp1.hetzner.de 2 9 377 428 -380us[ -507us] +/- 37ms ^- ntp2.hetzner.de 2 6 377 48 -459us[ -459us] +/- 26ms ^- ntp3.hetzner.de 2 9 377 88 -163us[ -163us] +/- 29ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Tue 23 Jun 17:19:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 651 -1230us[-1166us] +/- 27ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 108 +348us[ +414us] +/- 9052us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Tue 23 Jun 17:19:06 UTC 2026
Current performance for ntp21.linocomm.net (Roubaix, FR)
Tue 23 Jun 17:19:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 617 +202us[ +202us] +/- 11ms ^+ 2A10-3781-08cC.connected> 2 10 377 635 -264us[ -264us] +/- 10ms ^- ntp-public-2.oma.be 2 8 377 202 -2382us[-2382us] +/- 21ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 78 -772us[ -772us] +/- 9086us ^* d54c70bd3.static.telenet> 1 10 377 29m +2036us[+1972us] +/- 9299us ^+ 82-64-45-50.subs.proxad.> 1 10 377 93 -698us[ -698us] +/- 7496us
Current performance for ntp22.linocomm.net (Paris, FR)
Tue 23 Jun 17:19:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 36 +2163us[+2163us] +/- 14ms ^+ 2A10-3781-08cC.connected> 2 10 177 995 +374us[ +443us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 950 +1440us[+1508us] +/- 56ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 154 -262us[ -192us] +/- 7757us
Current performance for ntp23.linocomm.net (Paris, FR)
Tue 23 Jun 17:19:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 928 +202us[ +181us] +/- 15ms ^+ 2A10-3781-08cC.connected> 2 10 377 289 +241us[ +241us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 156 -1946us[-1946us] +/- 27ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 418 -299us[ -327us] +/- 7840us
Current performance for ntp24.linocomm.net (Paris, FR)
Tue 23 Jun 17:19:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 268 -74us[ -74us] +/- 12ms ^? 2A10-3781-08cc.connected> 0 10 0 - +0ns[ +0ns] +/- 0ns ^- ntp-public-2.oma.be 2 10 377 416 -185us[ -185us] +/- 35ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 873 -340us[ -110us] +/- 8005us ^+ d54c70bd3.static.telenet> 1 10 377 238 +3658us[+3658us] +/- 10ms ^* 82-64-45-50.subs.proxad.> 1 10 377 867 +182us[ +412us] +/- 5640us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Tue 23 Jun 17:19:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 424 +11us[ +72us] +/- 7954us ^- time.fu-berlin.de 1 10 377 497 -186us[ -126us] +/- 68ms ^- ntp1.hetzner.de 2 8 377 144 -40us[ -40us] +/- 42ms ^- ntp2.hetzner.de 2 6 377 39 -195us[ -195us] +/- 26ms ^- ntp3.hetzner.de 2 9 377 256 +78us[ +78us] +/- 27ms