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 11 Aug 12:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 10 377 1035 -172us[ -96us] +/- 6784us ^+ 2a10-3781-08cc.connected> 2 10 377 903 -208us[ -208us] +/- 5953us ^- ntp-public-2.oma.be 2 10 377 14 -387us[ -387us] +/- 28ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 35m -4096us[-4065us] +/- 10ms ^+ d54c70bd3.static.telenet> 1 10 377 427 +6110us[+6110us] +/- 11ms ^+ 82-64-171-216.subs.proxa> 1 10 377 993 +118us[ +118us] +/- 7944us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Tue 11 Aug 12:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 955 -309us[ -315us] +/- 7558us ^- time.fu-berlin.de 1 10 377 245 -331us[ -331us] +/- 58ms ^- ntp1.hetzner.de 2 9 377 295 -590us[ -590us] +/- 41ms ^- ntp2.hetzner.de 2 10 377 658 +253us[ +253us] +/- 28ms ^- ntp3.hetzner.de 2 10 377 473 -82us[ -82us] +/- 29ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Tue 11 Aug 12:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 183 -773us[ -646us] +/- 8756us ^- time.fu-berlin.de 1 9 377 164 -425us[ -425us] +/- 60ms ^- ntp1.hetzner.de 2 9 377 63 -905us[ -905us] +/- 23ms ^- ntp2.hetzner.de 2 9 377 360 -32us[ +95us] +/- 18ms ^- ntp3.hetzner.de 2 8 377 166 -419us[ -419us] +/- 31ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Tue 11 Aug 12:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 9 377 436 -196us[ -241us] +/- 3383us ^+ time1.esa.int 1 9 377 7 -535us[ -535us] +/- 3510us ^+ ntp1.time.nl 1 9 377 207 -268us[ -268us] +/- 4415us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Tue 11 Aug 12:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 438 -1063us[-1079us] +/- 7111us ^- time.fu-berlin.de 1 10 377 34m -1324us[-1330us] +/- 61ms ^- ntp1.hetzner.de 2 9 377 15 -1720us[-1720us] +/- 23ms ^- ntp2.hetzner.de 2 10 377 195 -2794us[-2794us] +/- 23ms ^- ntp3.hetzner.de 2 10 377 1033 -1182us[-1197us] +/- 47ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Tue 11 Aug 12:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 137 -2347us[-2347us] +/- 28ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 772 +8618ns[ +13us] +/- 7291us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Tue 11 Aug 12:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 577 -475us[ -447us] +/- 7906us ^- time.fu-berlin.de 1 10 377 867 -684us[ -657us] +/- 65ms ^- ntp1.hetzner.de 2 8 377 61 -1093us[-1093us] +/- 23ms ^- ntp2.hetzner.de 2 9 377 123 -285us[ -285us] +/- 21ms ^- ntp3.hetzner.de 2 10 377 176 -597us[ -597us] +/- 31ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Tue 11 Aug 12:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 8 377 14 -2953us[-2953us] +/- 30ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 131 -34us[ -37us] +/- 7103us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Tue 11 Aug 12:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 422 -416us[ -416us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 9 377 186 -241us[ -241us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 404 -3387us[-3387us] +/- 24ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 250 -371us[ -371us] +/- 6927us ^+ d54c70bd3.static.telenet> 1 10 377 103 +2982us[+2982us] +/- 9671us ^* 82-64-171-216.subs.proxa> 1 10 377 786 -146us[ -272us] +/- 6071us
Current performance for ntp22.linocomm.net (Paris, FR)
Tue 11 Aug 12:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 177 667 -1648us[-1801us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 77 -109us[ -127us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 126 -2487us[-2505us] +/- 33ms ^* ntp0.rrze.uni-erlangen.de 1 7 377 49 -213us[ -231us] +/- 7812us
Current performance for ntp23.linocomm.net (Paris, FR)
Tue 11 Aug 12:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 738 -1880us[-2076us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 116 -52us[+4381ns] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 74 -975us[ -975us] +/- 31ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 87 -547us[ -489us] +/- 8136us
Current performance for ntp24.linocomm.net (Paris, FR)
Tue 11 Aug 12:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 97 -1610us[-1610us] +/- 13ms ^- 2a10-3781-08cc.connected> 2 10 377 533 -2086us[-2070us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 156 -480us[ -480us] +/- 30ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 157 +26us[ +26us] +/- 8015us ^- d54c70bd3.static.telenet> 1 10 377 821 +2319us[+2340us] +/- 8924us ^* 82-64-171-216.subs.proxa> 1 9 377 318 +136us[ +148us] +/- 3670us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Tue 11 Aug 12:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 484 +113us[ +143us] +/- 7864us ^- time.fu-berlin.de 1 10 377 597 +62us[ +92us] +/- 61ms ^- ntp1.hetzner.de 2 7 377 34 -335us[ -335us] +/- 24ms ^- ntp2.hetzner.de 2 8 377 246 +449us[ +449us] +/- 19ms ^- ntp3.hetzner.de 2 9 377 245 +63us[ +63us] +/- 30ms