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 3 Aug 20:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 20 -184us[ -184us] +/- 7693us ^* 2a10-3781-08cc.connected> 2 9 377 411 -104us[ -163us] +/- 7599us ^- ntp-public-2.oma.be 2 9 377 242 -24us[ -24us] +/- 33ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 332 -3407us[-3407us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 415 +5853us[+5794us] +/- 13ms ^+ 82-64-171-216.subs.proxa> 1 10 377 259 +1118us[+1118us] +/- 8540us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Mon 3 Aug 20:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 357 34m -467us[ -437us] +/- 7557us ^- time.fu-berlin.de 1 10 377 421 -493us[ -493us] +/- 66ms ^- ntp1.hetzner.de 2 9 377 304 -245us[ -245us] +/- 21ms ^- ntp2.hetzner.de 2 9 377 284 -89us[ -89us] +/- 39ms ^- ntp3.hetzner.de 2 9 377 26 -394us[ -394us] +/- 17ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Mon 3 Aug 20:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 215 -398us[ -368us] +/- 8325us ^- time.fu-berlin.de 1 10 377 1175 -1190us[-1161us] +/- 71ms ^- ntp1.hetzner.de 2 10 377 1014 -226us[ -196us] +/- 27ms ^- ntp2.hetzner.de 2 9 377 281 -12us[ +18us] +/- 38ms ^- ntp3.hetzner.de 2 9 377 210 -230us[ -230us] +/- 13ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Mon 3 Aug 20:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 10 377 458 +86us[ +167us] +/- 4018us ^+ time1.esa.int 1 10 377 598 +224us[ +304us] +/- 3887us ^+ ntp1.time.nl 1 10 377 15 +55us[ +55us] +/- 5104us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Mon 3 Aug 20:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 177 335 -30us[ +15us] +/- 7162us ^- time.fu-berlin.de 1 10 377 734 -296us[ -257us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 821 -180us[ -142us] +/- 29ms ^- ntp2.hetzner.de 2 10 377 17 -57us[ -57us] +/- 43ms ^- ntp3.hetzner.de 2 9 377 32 -303us[ -303us] +/- 17ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Mon 3 Aug 20:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp-public-2.oma.be 2 10 377 998 -1476us[-1399us] +/- 43ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 126 +554us[ +629us] +/- 9305us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Mon 3 Aug 20:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 443 -56us[ -39us] +/- 7827us ^- time.fu-berlin.de 1 10 377 7 -420us[ -420us] +/- 72ms ^- ntp1.hetzner.de 2 7 377 13 -115us[ -115us] +/- 26ms ^- ntp2.hetzner.de 2 8 377 92 -103us[ -103us] +/- 40ms ^- ntp3.hetzner.de 2 7 377 71 -321us[ -321us] +/- 15ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Mon 3 Aug 20:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 8 377 158 -3807us[-3807us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 576 -2449us[-2762us] +/- 7945us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Mon 3 Aug 20:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 1002 -465us[ -306us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 719 -212us[ -51us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 912 -1838us[-1678us] +/- 24ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 336 -639us[ -475us] +/- 8056us ^+ d54c70bd3.static.telenet> 1 10 377 80 +4401us[+4401us] +/- 8998us ^* 82-64-171-216.subs.proxa> 1 10 377 143 +808us[ +975us] +/- 5942us
Current performance for ntp22.linocomm.net (Paris, FR)
Mon 3 Aug 20:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 686 -2085us[-2157us] +/- 15ms ^+ 2a10-3781-08cc.connected> 2 10 377 503 -1923us[-2001us] +/- 15ms ^- ntp-public-2.oma.be 2 9 377 514 -2523us[-2601us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 28 -24us[ -117us] +/- 7824us
Current performance for ntp23.linocomm.net (Paris, FR)
Mon 3 Aug 20:04:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 722 -2443us[-2546us] +/- 15ms ^+ 2a10-3781-08cc.connected> 2 10 377 699 -2571us[-2673us] +/- 15ms ^- ntp-public-2.oma.be 2 10 377 761 -2494us[-2597us] +/- 31ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 124 -25us[ -22us] +/- 8258us
Current performance for ntp24.linocomm.net (Paris, FR)
Mon 3 Aug 20:04:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 200 -729us[ -684us] +/- 12ms ^- 2a10-3781-08cc.connected> 2 10 377 208 -1119us[-1073us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 599 -2680us[-2628us] +/- 33ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 205 -717us[ -671us] +/- 7999us ^+ d54c70bd3.static.telenet> 1 10 377 738 +1537us[+1552us] +/- 8575us ^* 82-64-171-216.subs.proxa> 1 9 377 130 +21us[ +65us] +/- 4013us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Mon 3 Aug 20:04:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 464 -991us[-1172us] +/- 8057us ^- time.fu-berlin.de 1 10 377 851 -1033us[-1213us] +/- 60ms ^- ntp1.hetzner.de 2 7 377 119 -756us[ -756us] +/- 25ms ^- ntp2.hetzner.de 2 8 377 142 -723us[ -723us] +/- 40ms ^- ntp3.hetzner.de 2 8 377 217 -950us[ -950us] +/- 13ms