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)
Fri 4 Sep 20:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 915 +100us[ +83us] +/- 7074us ^+ 2a10-3781-08cc.connected> 2 10 377 560 +111us[ +77us] +/- 6790us ^- ntp-public-2.oma.be 2 8 377 242 -253us[ -253us] +/- 49ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 305 +183us[ +150us] +/- 6602us ^+ d54c70bd3.static.telenet> 1 10 377 368 +7343us[+7310us] +/- 12ms ^+ 82-64-171-216.subs.proxa> 1 10 377 443 -1609us[-1643us] +/- 9890us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Fri 4 Sep 20:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 367 837 -667us[ -663us] +/- 7738us ^- time.fu-berlin.de 1 10 377 21m -462us[ -457us] +/- 66ms ^- ntp1.hetzner.de 2 9 377 179 -521us[ -521us] +/- 15ms ^- ntp2.hetzner.de 2 9 377 287 -117us[ -117us] +/- 23ms ^- ntp3.hetzner.de 2 10 377 11 -3146us[-3146us] +/- 36ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Fri 4 Sep 20:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 957 -127us[ -411us] +/- 7826us ^- time.fu-berlin.de 1 9 377 590 -124us[ -124us] +/- 62ms ^- ntp1.hetzner.de 2 8 377 144 -70us[ -70us] +/- 17ms ^- ntp2.hetzner.de 2 7 377 36 -524us[ -524us] +/- 24ms ^- ntp3.hetzner.de 2 8 377 477 -915us[ -915us] +/- 26ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Fri 4 Sep 20:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 10 377 574 +255us[ +299us] +/- 3872us ^- time1.esa.int 1 10 377 329 -178us[ -178us] +/- 3218us ^+ ntp1.time.nl 1 10 377 1034 -421us[ -379us] +/- 4484us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Fri 4 Sep 20:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 367 63 -378us[ -751us] +/- 7373us ^- time.fu-berlin.de 1 10 377 27m -59us[ -604us] +/- 60ms ^- ntp1.hetzner.de 2 8 377 145 -218us[ -590us] +/- 16ms ^- ntp2.hetzner.de 2 9 377 338 -344us[ -717us] +/- 21ms ^- ntp3.hetzner.de 2 10 377 351 -1017us[-1390us] +/- 29ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Fri 4 Sep 20:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 680 -2166us[-2149us] +/- 43ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 489 +5357ns[ +24us] +/- 7316us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Fri 4 Sep 20:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 227 -255us[ -488us] +/- 7826us ^- time.fu-berlin.de 1 10 377 884 -306us[ -540us] +/- 72ms ^- ntp1.hetzner.de 2 8 377 5 -288us[ -288us] +/- 19ms ^- ntp2.hetzner.de 2 8 377 20 -806us[ -806us] +/- 25ms ^- ntp3.hetzner.de 2 10 377 9 -1179us[-1179us] +/- 33ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Fri 4 Sep 20:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 477 -2043us[-2017us] +/- 46ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 387 +40us[ +67us] +/- 7101us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Fri 4 Sep 20:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 82 +231us[ +231us] +/- 9653us ^+ 2a10-3781-08cc.connected> 2 9 377 13 +29us[ +29us] +/- 9569us ^- ntp-public-2.oma.be 2 9 377 243 -2000us[-2000us] +/- 49ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 323 +57us[ +57us] +/- 7124us ^+ d54c70bd3.static.telenet> 1 10 377 30m +4261us[+4620us] +/- 9120us ^* 82-64-171-216.subs.proxa> 1 10 377 567 +577us[ +723us] +/- 5529us
Current performance for ntp22.linocomm.net (Paris, FR)
Fri 4 Sep 20:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 688 -2707us[-2799us] +/- 16ms ^+ 2a10-3781-08cc.connected> 2 10 377 121 -2945us[-2945us] +/- 15ms ^- ntp-public-2.oma.be 2 10 377 184 -596us[ -616us] +/- 56ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 156 +1352us[+1333us] +/- 8090us
Current performance for ntp23.linocomm.net (Paris, FR)
Fri 4 Sep 20:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 520 -3150us[-3150us] +/- 14ms ^+ 2a10-3781-08cc.connected> 2 10 377 130 +440us[ +440us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 255 +515us[ +515us] +/- 53ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 679 +525us[ +485us] +/- 8181us
Current performance for ntp24.linocomm.net (Paris, FR)
Fri 4 Sep 20:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 597 +741us[ +900us] +/- 12ms ^- 2a10-3781-08cc.connected> 2 9 377 164 -2249us[-2075us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 730 -250us[ -96us] +/- 46ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 67 -51us[ -51us] +/- 8240us ^+ d54c70bd3.static.telenet> 1 10 377 465 +3248us[+3411us] +/- 9825us ^* 82-64-171-216.subs.proxa> 1 10 177 147 -217us[ -41us] +/- 3458us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Fri 4 Sep 20:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 21m -125us[ -154us] +/- 8134us ^- time.fu-berlin.de 1 8 377 103 +124us[ +124us] +/- 69ms ^- ntp1.hetzner.de 2 10 377 575 +3021ns[+3021ns] +/- 10ms ^- ntp2.hetzner.de 2 6 377 61 -360us[ -360us] +/- 24ms ^- ntp3.hetzner.de 2 8 377 260 -741us[ -741us] +/- 29ms