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)
Fri 14 Aug 13:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 376 +185us[ +185us] +/- 6761us ^* 2a10-3781-08cc.connected> 2 10 377 563 +92us[ -132us] +/- 6396us ^- ntp-public-2.oma.be 2 8 377 91 +1907us[+1907us] +/- 32ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 98 -4004us[-4004us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 100 +4252us[+4252us] +/- 11ms ^+ 82-64-171-216.subs.proxa> 1 10 377 463 +2461us[+2461us] +/- 9776us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Fri 14 Aug 13:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 375 630 -540us[ -172us] +/- 7668us ^- time.fu-berlin.de 1 10 377 727 -805us[ -437us] +/- 69ms ^- ntp1.hetzner.de 2 10 377 516 +169us[ +169us] +/- 22ms ^- ntp2.hetzner.de 2 10 377 473 -583us[ -583us] +/- 20ms ^- ntp3.hetzner.de 2 10 377 472 -637us[ -637us] +/- 23ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Fri 14 Aug 13:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 400 -1672us[-1656us] +/- 9221us ^- time.fu-berlin.de 1 9 377 195 -956us[ -956us] +/- 63ms ^- ntp1.hetzner.de 2 8 377 34 +316us[ +316us] +/- 19ms ^- ntp2.hetzner.de 2 7 377 91 -607us[ -607us] +/- 25ms ^- ntp3.hetzner.de 2 10 377 54 -647us[ -647us] +/- 26ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Fri 14 Aug 13:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ time1.esa.int 1 9 377 224 +33us[ +33us] +/- 3658us ^+ ntp1.time.nl 1 9 377 364 -242us[ -332us] +/- 4494us ^* ntp0.nl.uu.net 1 9 377 270 -214us[ -306us] +/- 3506us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Fri 14 Aug 13:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 375 918 -514us[ -507us] +/- 7544us ^- time.fu-berlin.de 1 10 377 217 -594us[ -594us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 388 +521us[ +521us] +/- 24ms ^- ntp2.hetzner.de 2 9 377 127 -462us[ -462us] +/- 26ms ^- ntp3.hetzner.de 2 10 377 571 -481us[ -481us] +/- 21ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Fri 14 Aug 13:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 126 -135us[ -135us] +/- 33ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 428 +30us[ +40us] +/- 9251us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Fri 14 Aug 13:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 21 -83us[ -56us] +/- 8048us ^- time.fu-berlin.de 1 10 377 955 -323us[ -299us] +/- 66ms ^- ntp1.hetzner.de 2 9 377 316 +559us[ +584us] +/- 26ms ^- ntp2.hetzner.de 2 6 377 23 -286us[ -259us] +/- 26ms ^- ntp3.hetzner.de 2 8 377 94 -351us[ -324us] +/- 25ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Fri 14 Aug 13:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 8 377 163 -1016us[-1012us] +/- 33ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 124 +8630ns[ +13us] +/- 6948us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Fri 14 Aug 13:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 234 -440us[ -440us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 9 377 233 +34us[ +34us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 922 -1548us[-1792us] +/- 26ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 25 -327us[ -327us] +/- 7001us ^+ d54c70bd3.static.telenet> 1 10 377 32m +5834us[+5515us] +/- 11ms ^* 82-64-171-216.subs.proxa> 1 10 377 423 -192us[ -477us] +/- 5792us
Current performance for ntp22.linocomm.net (Paris, FR)
Fri 14 Aug 13:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 350 -247us[ -286us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 975 -1265us[-1282us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 273 +1429us[+1387us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 101 -240us[ -288us] +/- 7787us
Current performance for ntp23.linocomm.net (Paris, FR)
Fri 14 Aug 13:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 156 -1734us[-1734us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 8 377 77 +61us[ +61us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 86 +650us[ +650us] +/- 38ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 255 +84us[ +54us] +/- 8062us
Current performance for ntp24.linocomm.net (Paris, FR)
Fri 14 Aug 13:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 294 -1389us[-1389us] +/- 13ms ^- 2a10-3781-08cc.connected> 2 10 377 899 -75us[ -103us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 948 -428us[ -456us] +/- 30ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 1003 -139us[ -166us] +/- 7881us ^- d54c70bd3.static.telenet> 1 10 377 321 +6678us[+6678us] +/- 13ms ^* 82-64-171-216.subs.proxa> 1 10 377 491 +403us[ +374us] +/- 4011us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Fri 14 Aug 13:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 936 +20us[ +28us] +/- 7906us ^- time.fu-berlin.de 1 10 377 725 -206us[ -206us] +/- 70ms ^- ntp1.hetzner.de 2 7 377 38 +790us[ +790us] +/- 19ms ^- ntp2.hetzner.de 2 7 377 72 -84us[ -84us] +/- 25ms ^- ntp3.hetzner.de 2 8 377 67 -142us[ -142us] +/- 25ms