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)
Wed 17 Jun 16:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 705 +745us[ +745us] +/- 6230us ^+ 2A10-3781-08Cc.connected> 2 9 377 43 +814us[ +814us] +/- 6360us ^- ntp-public-2.oma.be 2 10 377 106 +1202us[+1202us] +/- 48ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 269 -3546us[-3546us] +/- 11ms ^* d54c70bd3.static.telenet> 1 10 377 878 +6512us[+6408us] +/- 11ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 216 +1006us[+1006us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Wed 17 Jun 16:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 969 -217us[ -190us] +/- 8143us ^- time.fu-berlin.de 1 10 377 840 -147us[ -147us] +/- 63ms ^- ntp1.hetzner.de 2 9 377 305 +2753ns[+2753ns] +/- 29ms ^- ntp2.hetzner.de 2 10 377 30m +348us[ +371us] +/- 17ms ^- ntp3.hetzner.de 2 10 377 635 +153us[ +153us] +/- 40ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Wed 17 Jun 16:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 462 -164us[ -151us] +/- 8238us ^- time.fu-berlin.de 1 10 377 28m -316us[ -249us] +/- 59ms ^- ntp1.hetzner.de 2 10 377 770 -183us[ -171us] +/- 47ms ^- ntp2.hetzner.de 2 8 377 185 +142us[ +142us] +/- 22ms ^+ ntp3.hetzner.de 2 10 377 264 -1593us[-1593us] +/- 46ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Wed 17 Jun 16:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 232 -437us[ -437us] +/- 4036us ^* time1.esa.int 1 9 377 384 -279us[ -323us] +/- 3378us ^+ ntp1.time.nl 1 9 377 403 -577us[ -620us] +/- 4757us
Current performance for ntp5.linocomm.net (Paris, FR)
Sun 7 Jun 08:34:01 UTC 2026
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Wed 17 Jun 16:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 205 -513us[ -501us] +/- 7965us ^- time.fu-berlin.de 1 9 377 185 -145us[ -145us] +/- 58ms ^- ntp1.hetzner.de 2 8 377 57 -135us[ -135us] +/- 32ms ^- ntp2.hetzner.de 2 9 377 449 -1651us[-1638us] +/- 40ms ^- ntp3.hetzner.de 2 9 377 535 +73us[ +86us] +/- 41ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Wed 17 Jun 16:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 425 -836us[ -815us] +/- 45ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 231 +8986ns[ +31us] +/- 9272us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Wed 17 Jun 16:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 618 -98us[ -71us] +/- 8134us ^- time.fu-berlin.de 1 10 377 188 -213us[ -213us] +/- 58ms ^- ntp1.hetzner.de 2 9 377 439 -192us[ -192us] +/- 28ms ^- ntp2.hetzner.de 2 8 377 7 +153us[ +153us] +/- 25ms ^- ntp3.hetzner.de 2 10 377 603 -96us[ -96us] +/- 39ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Wed 17 Jun 16:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 107 -1107us[-1107us] +/- 49ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 884 +10us[ +125us] +/- 8782us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Wed 17 Jun 16:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 965 -984us[ -960us] +/- 8577us ^- time.fu-berlin.de 1 10 377 490 -434us[ -434us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 863 -330us[ -330us] +/- 45ms ^- ntp2.hetzner.de 2 9 377 230 -92us[ -92us] +/- 21ms ^+ ntp3.hetzner.de 2 9 377 495 -308us[ -308us] +/- 41ms
Current performance for ntp21.linocomm.net (Roubaix, FR)
Wed 17 Jun 16:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 488 -120us[ -120us] +/- 8765us ^+ 2a10-3781-08cC.connected> 2 10 377 245 -306us[ -306us] +/- 8552us ^- ntp-public-2.oma.be 2 10 377 303 -1390us[-1390us] +/- 46ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 268 -287us[ -287us] +/- 8983us ^+ d54c70bd3.static.telenet> 1 10 377 131 +2633us[+2633us] +/- 9012us ^* 82-64-45-50.subs.proxad.> 1 10 377 895 +222us[ +274us] +/- 7632us
Current performance for ntp22.linocomm.net (Paris, FR)
Wed 17 Jun 16:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 423 -801us[ -914us] +/- 11ms ^+ 2a10-3781-08CC.connected> 2 10 377 877 -278us[ -389us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 376 +1174us[+1061us] +/- 51ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 140 -468us[ -582us] +/- 8138us
Current performance for ntp23.linocomm.net (Paris, FR)
Wed 17 Jun 16:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 333 -512us[ -537us] +/- 11ms ^+ 2a10-3781-08CC.connected> 2 10 377 973 -33us[ -31us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 891 -1461us[-1458us] +/- 43ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 178 -460us[ -485us] +/- 7828us
Current performance for ntp24.linocomm.net (Paris, FR)
Wed 17 Jun 16:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 657 -236us[ -236us] +/- 11ms ^? 2a10-3781-08cC.connected> 0 10 0 - +0ns[ +0ns] +/- 0ns ^- ntp-public-2.oma.be 2 10 377 807 -1752us[-1719us] +/- 44ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 217 -388us[ -388us] +/- 8223us ^+ d54c70bd3.static.telenet> 1 10 377 854 +6344us[+6375us] +/- 14ms ^* 82-64-45-50.subs.proxad.> 1 10 377 760 +48us[ +82us] +/- 5663us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Wed 17 Jun 16:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 794 -435us[ -508us] +/- 7813us ^- time.fu-berlin.de 1 10 377 220 -483us[ -483us] +/- 58ms ^- ntp1.hetzner.de 2 7 377 119 -473us[ -473us] +/- 32ms ^- ntp2.hetzner.de 2 7 377 22 -204us[ -204us] +/- 24ms ^- ntp3.hetzner.de 2 10 377 994 -313us[ -383us] +/- 33ms