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)
Sat 25 Jul 19:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 10 377 890 -189us[ -301us] +/- 6704us ^+ 2a10-3781-08cc.connected> 2 10 377 484 -405us[ -405us] +/- 6325us ^- ntp-public-2.oma.be 2 8 377 36 -171us[ -171us] +/- 37ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 21m -4370us[-4469us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 369 +5766us[+5766us] +/- 11ms ^+ 82-64-171-216.subs.proxa> 1 10 377 730 +1621us[+1621us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sat 25 Jul 19:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 337 422 -822us[ -822us] +/- 8223us ^- time.fu-berlin.de 1 10 377 150 -514us[ -514us] +/- 67ms ^- ntp1.hetzner.de 2 9 377 822 -1468us[-1468us] +/- 25ms ^- ntp2.hetzner.de 2 9 377 64 -570us[ -570us] +/- 29ms ^- ntp3.hetzner.de 2 10 377 910 -668us[ -668us] +/- 47ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sat 25 Jul 19:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 367 546 -499us[ -466us] +/- 8592us ^- time.fu-berlin.de 1 10 377 615 -779us[ -746us] +/- 61ms ^- ntp1.hetzner.de 2 9 377 255 -1500us[-1500us] +/- 23ms ^- ntp2.hetzner.de 2 8 377 89 -618us[ -618us] +/- 27ms ^- ntp3.hetzner.de 2 10 377 753 -829us[ -797us] +/- 48ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sat 25 Jul 19:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 80 -149us[ -149us] +/- 3916us ^* time1.esa.int 1 10 377 735 -430us[ -466us] +/- 3618us ^+ ntp1.time.nl 1 9 377 318 -299us[ -299us] +/- 4485us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sat 25 Jul 19:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 1017 +127us[ +308us] +/- 7019us ^- time.fu-berlin.de 1 10 377 173 -286us[ -286us] +/- 67ms ^- ntp1.hetzner.de 2 8 377 335 -1319us[-1319us] +/- 33ms ^- ntp2.hetzner.de 2 9 377 300 -609us[ -609us] +/- 25ms ^- ntp3.hetzner.de 2 10 377 30m -475us[ -303us] +/- 34ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sat 25 Jul 19:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 69 -1378us[-1378us] +/- 38ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 195 -7148ns[-5811ns] +/- 7302us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sat 25 Jul 19:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 337 223 -569us[ -594us] +/- 8125us ^- time.fu-berlin.de 1 10 377 789 -677us[ -701us] +/- 58ms ^- ntp1.hetzner.de 2 9 377 241 -1712us[-1737us] +/- 23ms ^- ntp2.hetzner.de 2 6 377 45 -976us[ -976us] +/- 28ms ^- ntp3.hetzner.de 2 10 377 363 -1046us[-1071us] +/- 23ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sat 25 Jul 19:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 8 377 109 -1459us[-1459us] +/- 37ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 109 -77us[ -86us] +/- 7153us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sat 25 Jul 19:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 289 +18us[ +18us] +/- 9171us ^+ 2a10-3781-08cc.connected> 2 10 377 688 -216us[ -60us] +/- 8499us ^- ntp-public-2.oma.be 2 8 377 154 -1560us[-1560us] +/- 36ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 963 -241us[ -97us] +/- 6967us ^+ d54c70bd3.static.telenet> 1 10 377 850 +3924us[+4073us] +/- 9127us ^* 82-64-171-216.subs.proxa> 1 10 377 586 +18us[ +178us] +/- 5855us
Current performance for ntp22.linocomm.net (Paris, FR)
Sat 25 Jul 19:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 658 -1507us[-1074us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 150 +299us[ +299us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 423 +320us[ +763us] +/- 36ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 416 +121us[ +565us] +/- 7892us
Current performance for ntp23.linocomm.net (Paris, FR)
Sat 25 Jul 19:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 801 -1648us[-1739us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 468 +347us[ +261us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 369 +1774us[+1690us] +/- 38ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 306 +229us[ +146us] +/- 7900us
Current performance for ntp24.linocomm.net (Paris, FR)
Sat 25 Jul 19:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 591 -83us[ -83us] +/- 14ms ^- 2a10-3781-08cc.connected> 2 10 377 762 -41us[ +46us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 329 +1346us[+1346us] +/- 39ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 333 -236us[ -236us] +/- 7937us ^- d54c70bd3.static.telenet> 1 10 377 931 +3617us[+3702us] +/- 9536us ^* 82-64-171-216.subs.proxa> 1 10 377 716 +163us[ +250us] +/- 3763us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sat 25 Jul 19:58:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 177 83 -94us[ -38us] +/- 8041us ^- time.fu-berlin.de 1 9 377 144 -115us[ -58us] +/- 68ms ^- ntp1.hetzner.de 2 10 377 703 -1157us[-1106us] +/- 28ms ^- ntp2.hetzner.de 2 7 377 39 -422us[ -422us] +/- 28ms ^- ntp3.hetzner.de 2 8 377 244 -499us[ -444us] +/- 25ms