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 17 Aug 09:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 420 +467us[ +467us] +/- 6811us ^* 2a10-3781-08cc.connected> 2 10 377 818 +614us[ +301us] +/- 6340us ^- ntp-public-2.oma.be 2 10 377 408 +180us[ +180us] +/- 34ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 735 -3373us[-3373us] +/- 10ms ^+ d54c70bd3.static.telenet> 1 10 377 220 +2910us[+2910us] +/- 9187us ^+ 82-64-171-216.subs.proxa> 1 10 377 535 -1357us[-1357us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Mon 17 Aug 09:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 710 -126us[ +429us] +/- 7261us ^- time.fu-berlin.de 1 10 377 344 -814us[ -814us] +/- 62ms ^- ntp1.hetzner.de 2 10 377 299 -722us[ -722us] +/- 24ms ^- ntp2.hetzner.de 2 10 377 834 -749us[ -195us] +/- 31ms ^- ntp3.hetzner.de 2 10 377 105 -639us[ -639us] +/- 39ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Mon 17 Aug 09:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 425 -319us[ -333us] +/- 8162us ^- time.fu-berlin.de 1 10 377 863 -322us[ -334us] +/- 62ms ^- ntp1.hetzner.de 2 8 377 147 -142us[ -142us] +/- 27ms ^- ntp2.hetzner.de 2 9 377 257 -55us[ -55us] +/- 39ms ^+ ntp3.hetzner.de 2 9 377 280 -182us[ -182us] +/- 35ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Mon 17 Aug 09:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* time1.esa.int 1 10 377 862 -62us[ -235us] +/- 3326us ^+ ntp1.time.nl 1 9 377 358 -541us[ -541us] +/- 4587us ^+ ntp0.nl.uu.net 1 10 377 536 -334us[ -334us] +/- 3536us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Mon 17 Aug 09:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 955 -333us[ -337us] +/- 7322us ^- time.fu-berlin.de 1 10 377 31m -520us[ -524us] +/- 58ms ^- ntp1.hetzner.de 2 10 377 654 -244us[ -244us] +/- 35ms ^- ntp2.hetzner.de 2 10 377 1010 -316us[ -320us] +/- 29ms ^- ntp3.hetzner.de 2 10 377 512 -550us[ -550us] +/- 33ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Mon 17 Aug 09:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 65 -2958us[-2958us] +/- 41ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 620 -1161us[-1224us] +/- 9229us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Mon 17 Aug 09:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 277 184 -22us[ -98us] +/- 7588us ^- time.fu-berlin.de 1 10 377 193 -378us[ -454us] +/- 65ms ^- ntp1.hetzner.de 2 10 377 244 -172us[ -247us] +/- 26ms ^- ntp2.hetzner.de 2 10 377 759 -54us[ -118us] +/- 31ms ^+ ntp3.hetzner.de 2 8 377 15 -144us[ -144us] +/- 39ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Mon 17 Aug 09:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 715 -2366us[-1976us] +/- 31ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 145 +389us[ +927us] +/- 7848us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Mon 17 Aug 09:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 596 -179us[ -179us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 543 -402us[ -402us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 22m -3161us[-3577us] +/- 26ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 455 -369us[ -369us] +/- 8947us ^+ d54c70bd3.static.telenet> 1 10 377 42 +2670us[+2670us] +/- 8244us ^* 82-64-171-216.subs.proxa> 1 10 377 1010 -238us[ -663us] +/- 5796us
Current performance for ntp22.linocomm.net (Paris, FR)
Mon 17 Aug 09:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 318 -411us[ -411us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 980 -354us[ -442us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 781 -422us[ -526us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 494 -745us[ -873us] +/- 7808us
Current performance for ntp23.linocomm.net (Paris, FR)
Mon 17 Aug 09:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 310 -3123us[-3426us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 171 -1045us[-1269us] +/- 11ms ^- ntp-public-2.oma.be 2 10 337 725 -1104us[-1436us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 21 -1028us[-1256us] +/- 8227us
Current performance for ntp24.linocomm.net (Paris, FR)
Mon 17 Aug 09:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 385 -60us[ -535us] +/- 11ms ^- 2a10-3781-08cc.connected> 2 10 377 13 -1611us[-1611us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 479 -1732us[-2188us] +/- 40ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 151 -207us[ -728us] +/- 7961us ^- d54c70bd3.static.telenet> 1 10 377 526 +5122us[+4675us] +/- 11ms ^* 82-64-171-216.subs.proxa> 1 10 377 26 -143us[ -689us] +/- 3735us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Mon 17 Aug 09:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 83 -482us[ -482us] +/- 7868us ^- time.fu-berlin.de 1 10 377 650 -508us[ -509us] +/- 58ms ^- ntp1.hetzner.de 2 9 377 225 -311us[ -312us] +/- 26ms ^- ntp2.hetzner.de 2 9 377 146 -201us[ -202us] +/- 40ms ^+ ntp3.hetzner.de 2 8 377 152 -297us[ -297us] +/- 37ms