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 07:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 119 +117us[ +117us] +/- 8085us ^+ 2a10-3781-08cc.connected> 2 10 377 1 +670us[ +670us] +/- 8812us ^+ ntp-public-2.oma.be 2 10 377 427 +57us[ +57us] +/- 27ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 1021 -3411us[-3411us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 130 +3681us[+3681us] +/- 9923us ^* 82-64-171-216.subs.proxa> 1 10 377 1031 +756us[ +768us] +/- 12ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Mon 3 Aug 07:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 27m -219us[ -218us] +/- 7570us ^- time.fu-berlin.de 1 10 377 71 -225us[ -225us] +/- 57ms ^- ntp1.hetzner.de 2 9 377 476 +106us[ +106us] +/- 37ms ^- ntp2.hetzner.de 2 9 377 25m +1534us[+1534us] +/- 47ms ^- ntp3.hetzner.de 2 10 377 149 +324us[ +324us] +/- 24ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Mon 3 Aug 07:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 910 -2013us[-2299us] +/- 9677us ^- time.fu-berlin.de 1 10 377 867 -520us[ -520us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 913 -124us[ -410us] +/- 32ms ^- ntp2.hetzner.de 2 7 377 62 -1426us[-1426us] +/- 20ms ^- ntp3.hetzner.de 2 9 377 87 -56us[ -56us] +/- 24ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Mon 3 Aug 07:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 10 377 597 -926us[-1340us] +/- 4272us ^+ time1.esa.int 1 10 377 227 -356us[ -356us] +/- 4412us ^+ ntp1.time.nl 1 10 377 216 -179us[ -179us] +/- 5279us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Mon 3 Aug 07:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 375 1035 -1388us[ -550us] +/- 7862us ^- time.fu-berlin.de 1 10 377 403 -1455us[-1455us] +/- 68ms ^- ntp1.hetzner.de 2 8 377 222 -1123us[-1123us] +/- 18ms ^- ntp2.hetzner.de 2 9 377 463 -200us[ -200us] +/- 18ms ^- ntp3.hetzner.de 2 10 377 33m -1190us[ -361us] +/- 21ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Mon 3 Aug 07:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 7 377 66 -1990us[-1990us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 823 -55us[ -254us] +/- 9363us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Mon 3 Aug 07:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 49 -236us[ -213us] +/- 8054us ^- time.fu-berlin.de 1 10 377 713 -366us[ -344us] +/- 63ms ^- ntp1.hetzner.de 2 9 377 380 +8336ns[ +31us] +/- 17ms ^- ntp2.hetzner.de 2 6 377 51 +288us[ +311us] +/- 19ms ^+ ntp3.hetzner.de 2 9 377 168 +162us[ +185us] +/- 23ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Mon 3 Aug 07:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 594 -1014us[ -838us] +/- 26ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 170 +82us[ +299us] +/- 8048us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Mon 3 Aug 07:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 658 -544us[ -544us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 324 -702us[ -702us] +/- 11ms ^- ntp-public-2.oma.be 2 9 377 10 -2613us[-2613us] +/- 35ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 978 -1772us[-1779us] +/- 7993us ^+ d54c70bd3.static.telenet> 1 10 377 747 -847us[ -847us] +/- 6249us ^* 82-64-171-216.subs.proxa> 1 10 377 793 -185us[ -192us] +/- 6092us
Current performance for ntp22.linocomm.net (Paris, FR)
Mon 3 Aug 07:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 315 -1946us[-2003us] +/- 14ms ^+ 2a10-3781-08cc.connected> 2 10 377 177 -646us[ -646us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 227 -195us[ -195us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 276 -466us[ -523us] +/- 7790us
Current performance for ntp23.linocomm.net (Paris, FR)
Mon 3 Aug 07:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 331 -16us[ -16us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 390 -2223us[-2223us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 392 -2273us[-2273us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 513 -16us[ -16us] +/- 8062us
Current performance for ntp24.linocomm.net (Paris, FR)
Mon 3 Aug 07:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 922 +871us[+1049us] +/- 13ms ^- 2a10-3781-08cc.connected> 2 10 377 880 +368us[ +548us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 280 -157us[ -157us] +/- 34ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 245 +296us[ +296us] +/- 8038us ^- d54c70bd3.static.telenet> 1 10 377 306 +6010us[+6010us] +/- 12ms ^* 82-64-171-216.subs.proxa> 1 9 377 352 +104us[ +231us] +/- 3642us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Mon 3 Aug 07:37:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 367 154 -933us[ -974us] +/- 8093us ^- time.fu-berlin.de 1 10 377 508 -951us[ -992us] +/- 67ms ^- ntp1.hetzner.de 2 9 377 56 -747us[ -747us] +/- 22ms ^- ntp2.hetzner.de 2 6 377 6 -566us[ -566us] +/- 19ms ^- ntp3.hetzner.de 2 7 377 128 -511us[ -511us] +/- 23ms