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 27 Jul 09:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 713 +356us[ +421us] +/- 6368us ^* 2a10-3781-08cc.connected> 2 9 377 399 +37us[ +111us] +/- 6633us ^- ntp-public-2.oma.be 2 10 377 745 -26us[ +38us] +/- 23ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 711 -3710us[-3645us] +/- 10ms ^+ d54c70bd3.static.telenet> 1 10 377 901 +2531us[+2590us] +/- 8425us ^+ 82-64-171-216.subs.proxa> 1 10 377 142 -1396us[-1396us] +/- 9644us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Mon 27 Jul 09:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 30m -2242us[-2251us] +/- 8906us ^- time.fu-berlin.de 1 10 377 666 -975us[ -975us] +/- 60ms ^- ntp1.hetzner.de 2 10 377 913 -651us[ -651us] +/- 23ms ^- ntp2.hetzner.de 2 9 377 684 -838us[ -838us] +/- 42ms ^- ntp3.hetzner.de 2 10 377 212 -812us[ -812us] +/- 41ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Mon 27 Jul 09:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 11 -1431us[-1473us] +/- 8611us ^- time.fu-berlin.de 1 9 377 396 -939us[ -981us] +/- 64ms ^- ntp1.hetzner.de 2 10 377 48 -695us[ -737us] +/- 26ms ^- ntp2.hetzner.de 2 10 377 23m -2289us[-2332us] +/- 32ms ^- ntp3.hetzner.de 2 9 377 695 -905us[ -946us] +/- 32ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Mon 27 Jul 09:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 418 -271us[ -271us] +/- 3787us ^* time1.esa.int 1 10 377 1058 -126us[ -155us] +/- 3222us ^+ ntp1.time.nl 1 9 377 453 -333us[ -333us] +/- 4494us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Mon 27 Jul 09:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 367 669 +122us[ +525us] +/- 6944us ^- time.fu-berlin.de 1 10 377 1021 -664us[ -263us] +/- 62ms ^- ntp1.hetzner.de 2 10 377 45 -525us[ -525us] +/- 25ms ^- ntp2.hetzner.de 2 10 377 858 -699us[ -297us] +/- 40ms ^- ntp3.hetzner.de 2 10 377 279 -611us[ -611us] +/- 40ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Mon 27 Jul 09:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 358 -1773us[-1773us] +/- 30ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 462 -54us[ -55us] +/- 7176us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Mon 27 Jul 09:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 822 -41us[ -33us] +/- 8076us ^- time.fu-berlin.de 1 10 377 565 -161us[ -161us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 569 -83us[ -83us] +/- 29ms ^- ntp2.hetzner.de 2 9 377 381 -261us[ -261us] +/- 45ms ^- ntp3.hetzner.de 2 10 377 401 -120us[ -120us] +/- 36ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Mon 27 Jul 09:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 299 -1947us[-1947us] +/- 30ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 674 -113us[ -210us] +/- 6898us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Mon 27 Jul 09:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 171 -745us[ -745us] +/- 9284us ^+ 2a10-3781-08cc.connected> 2 9 377 212 -580us[ -580us] +/- 9366us ^- ntp-public-2.oma.be 2 10 377 997 -2483us[-2632us] +/- 36ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 187 -836us[ -836us] +/- 6956us ^+ d54c70bd3.static.telenet> 1 10 377 897 +1588us[+1439us] +/- 7645us ^* 82-64-171-216.subs.proxa> 1 10 377 550 -814us[ -963us] +/- 5867us
Current performance for ntp22.linocomm.net (Paris, FR)
Mon 27 Jul 09:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 971 +1170us[+1415us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 832 -2539us[-2485us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 73 -954us[ -954us] +/- 38ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 119 -382us[ -322us] +/- 8188us
Current performance for ntp23.linocomm.net (Paris, FR)
Mon 27 Jul 09:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 234 -847us[-1643us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 975 -2047us[-2774us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 483 -2554us[-3327us] +/- 33ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 172 -733us[-1535us] +/- 8079us
Current performance for ntp24.linocomm.net (Paris, FR)
Mon 27 Jul 09:16:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 223 -537us[ -537us] +/- 12ms ^- 2a10-3781-08cc.connected> 2 10 377 257 -2830us[-2830us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 328 -1146us[-1146us] +/- 34ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 481 -852us[-1362us] +/- 7828us ^+ d54c70bd3.static.telenet> 1 10 377 333 +3026us[+2504us] +/- 10ms ^* 82-64-171-216.subs.proxa> 1 10 377 330 -749us[-1271us] +/- 3642us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Mon 27 Jul 09:16:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 841 -251us[ -376us] +/- 7872us ^- time.fu-berlin.de 1 10 377 692 -294us[ -294us] +/- 59ms ^- ntp1.hetzner.de 2 9 377 343 -241us[ -241us] +/- 33ms ^- ntp2.hetzner.de 2 9 377 194 -457us[ -457us] +/- 48ms ^+ ntp3.hetzner.de 2 10 377 247 -326us[ -326us] +/- 39ms