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)
Thu 23 Jul 04:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 9 377 121 +113us[ +151us] +/- 7420us ^+ 2a10-3781-08cc.connected> 2 10 377 334 +287us[ +324us] +/- 7219us ^- ntp-public-2.oma.be 2 10 377 695 +93us[ +159us] +/- 17ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 707 -3469us[-3403us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 26m +3504us[+3534us] +/- 9071us ^+ 82-64-171-216.subs.proxa> 1 10 377 125 +760us[ +798us] +/- 8650us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Thu 23 Jul 04:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 713 -78us[ -99us] +/- 7086us ^- time.fu-berlin.de 1 10 377 25m -435us[ -456us] +/- 60ms ^- ntp1.hetzner.de 2 10 377 14 -168us[ -168us] +/- 25ms ^- ntp2.hetzner.de 2 10 377 422 -590us[ -590us] +/- 28ms ^- ntp3.hetzner.de 2 10 377 29m -261us[ -282us] +/- 47ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Thu 23 Jul 04:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 789 -221us[ -171us] +/- 8197us ^- time.fu-berlin.de 1 9 377 699 -367us[ -367us] +/- 66ms ^+ ntp1.hetzner.de 2 10 377 88 -1525us[-1525us] +/- 35ms ^- ntp2.hetzner.de 2 9 377 207 -510us[ -510us] +/- 18ms ^- ntp3.hetzner.de 2 10 377 835 -85us[ -36us] +/- 27ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Thu 23 Jul 04:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 10 377 726 +164us[ +297us] +/- 3638us ^+ time1.esa.int 1 10 377 438 -61us[ -61us] +/- 3902us ^+ ntp1.time.nl 1 10 377 558 -216us[ -216us] +/- 4694us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Thu 23 Jul 04:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 9 377 630 -356us[ -271us] +/- 7448us ^- time.fu-berlin.de 1 9 377 488 -445us[ -445us] +/- 69ms ^- ntp1.hetzner.de 2 9 377 877 -123us[ -41us] +/- 21ms ^- ntp2.hetzner.de 2 10 377 639 -736us[ -651us] +/- 49ms ^- ntp3.hetzner.de 2 10 377 502 -307us[ -307us] +/- 23ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Thu 23 Jul 04:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 471 -2025us[-2025us] +/- 14ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 665 -122us[ -126us] +/- 7332us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Thu 23 Jul 04:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 362 -265us[ -255us] +/- 8019us ^- time.fu-berlin.de 1 10 377 487 -438us[ -429us] +/- 69ms ^- ntp1.hetzner.de 2 10 377 580 -158us[ -149us] +/- 26ms ^- ntp2.hetzner.de 2 10 377 796 -560us[ -551us] +/- 45ms ^- ntp3.hetzner.de 2 10 377 692 -294us[ -285us] +/- 30ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Thu 23 Jul 04:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 341 -1919us[-1919us] +/- 15ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 730 -37us[ -23us] +/- 6979us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Thu 23 Jul 04:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 635 -689us[ -689us] +/- 9085us ^+ 2a10-3781-08cc.connected> 2 10 377 728 -708us[ -708us] +/- 10ms ^- ntp-public-2.oma.be 2 9 377 407 -2256us[-2256us] +/- 14ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 745 -384us[ -384us] +/- 6987us ^+ d54c70bd3.static.telenet> 1 10 377 214 +3143us[+3143us] +/- 8845us ^* 82-64-171-216.subs.proxa> 1 10 377 776 +242us[ +200us] +/- 5946us
Current performance for ntp22.linocomm.net (Paris, FR)
Thu 23 Jul 04:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 475 -1814us[-2129us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 891 -1962us[-2213us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 516 +35us[ -281us] +/- 16ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 36 +150us[ -160us] +/- 7937us
Current performance for ntp23.linocomm.net (Paris, FR)
Thu 23 Jul 04:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 240 -552us[ -552us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 640 -353us[ -340us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 71 -39us[ -39us] +/- 23ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 285 +344us[ +357us] +/- 8076us
Current performance for ntp24.linocomm.net (Paris, FR)
Thu 23 Jul 04:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 929 -1215us[-1210us] +/- 14ms ^- 2a10-3781-08cc.connected> 2 10 377 984 -370us[ -366us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 560 -1621us[-1621us] +/- 17ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 135 -17us[ -17us] +/- 7911us ^- d54c70bd3.static.telenet> 1 10 377 176 +3901us[+3901us] +/- 11ms ^* 82-64-171-216.subs.proxa> 1 10 377 904 +303us[ +309us] +/- 3755us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Thu 23 Jul 04:16:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 405 -297us[ -310us] +/- 8044us ^- time.fu-berlin.de 1 10 377 571 -370us[ -383us] +/- 68ms ^- ntp1.hetzner.de 2 10 377 712 -117us[ -130us] +/- 24ms ^- ntp2.hetzner.de 2 10 377 249 -514us[ -514us] +/- 17ms ^- ntp3.hetzner.de 2 10 377 997 -265us[ -277us] +/- 25ms