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 8 Jun 18:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 269 +468us[ +468us] +/- 7490us ^* 2a10-3781-08cc.connected> 2 10 377 930 +213us[ +232us] +/- 6800us ^- ntp-public-2.oma.be 2 10 377 56 +611us[ +611us] +/- 20ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 613 -3640us[-3640us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 444 +5325us[+5325us] +/- 11ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 873 +687us[ +687us] +/- 9633us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Mon 8 Jun 18:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 19 -129us[ -73us] +/- 7483us ^- time.fu-berlin.de 1 10 377 479 -572us[ -518us] +/- 60ms ^- ntp1.hetzner.de 2 8 377 155 -378us[ -322us] +/- 27ms ^- ntp2.hetzner.de 2 10 377 373 -120us[ -66us] +/- 15ms ^- ntp3.hetzner.de 2 10 377 310 -499us[ -445us] +/- 35ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Mon 8 Jun 18:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 24m -960us[ -947us] +/- 7784us ^- time.fu-berlin.de 1 10 377 621 -1508us[-1508us] +/- 58ms ^- ntp1.hetzner.de 2 10 377 217 -1744us[-1744us] +/- 27ms ^- ntp2.hetzner.de 2 8 377 118 -1574us[-1574us] +/- 18ms ^- ntp3.hetzner.de 2 8 377 75 -1841us[-1841us] +/- 37ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Mon 8 Jun 18:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 10 377 941 +27us[ +635ns] +/- 4153us ^+ time1.esa.int 1 10 377 669 -54us[ -54us] +/- 3605us ^+ ntp1.time.nl 1 10 377 215 +174us[ +174us] +/- 4340us
Current performance for ntp5.linocomm.net (Paris, FR)
Sun 7 Jun 08:34:01 UTC 2026
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Mon 8 Jun 18:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 98 -1947us[-1936us] +/- 9230us ^- time.fu-berlin.de 1 10 377 779 -246us[ -234us] +/- 71ms ^- ntp1.hetzner.de 2 10 377 1007 -129us[ -118us] +/- 26ms ^- ntp2.hetzner.de 2 10 377 774 -151us[ -139us] +/- 27ms ^+ ntp3.hetzner.de 2 10 377 233 -668us[ -656us] +/- 36ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Mon 8 Jun 18:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp-public-2.oma.be 2 9 377 75 -916us[ -916us] +/- 37ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 316 +490us[ +134us] +/- 9456us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Mon 8 Jun 18:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 20m -163us[ -196us] +/- 8035us ^- time.fu-berlin.de 1 10 377 766 -205us[ -205us] +/- 72ms ^- ntp1.hetzner.de 2 10 377 583 -328us[ -328us] +/- 23ms ^- ntp2.hetzner.de 2 7 377 95 -150us[ -150us] +/- 18ms ^+ ntp3.hetzner.de 2 8 377 216 -546us[ -546us] +/- 35ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Mon 8 Jun 18:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 317 -1427us[-1427us] +/- 33ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 453 +104us[ +507us] +/- 6940us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Mon 8 Jun 18:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 512 -661us[ -737us] +/- 7992us ^- time.fu-berlin.de 1 10 377 37 -749us[ -749us] +/- 67ms ^- ntp1.hetzner.de 2 9 377 243 -835us[ -835us] +/- 27ms ^- ntp2.hetzner.de 2 6 377 63 -703us[ -703us] +/- 18ms ^- ntp3.hetzner.de 2 9 377 436 -940us[ -940us] +/- 32ms
Current performance for ntp21.linocomm.net (Roubaix, FR)
Mon 8 Jun 18:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 183 -1067us[-1067us] +/- 9957us ^- 2A10-3781-08cc.connected> 2 9 377 156 -724us[ -724us] +/- 10ms ^+ ntp-public-2.oma.be 2 10 377 926 -2053us[-2053us] +/- 24ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 970 -580us[ -401us] +/- 7102us ^+ d54c70bd3.static.telenet> 1 10 377 955 +2394us[+2573us] +/- 8297us ^* 82-64-45-50.subs.proxad.> 1 10 377 953 -342us[ -163us] +/- 7395us
Current performance for ntp22.linocomm.net (Paris, FR)
Mon 8 Jun 18:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 890 -1552us[-1552us] +/- 13ms ^+ 2A10-3781-08cc.connected> 2 10 377 942 -1963us[-1963us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 397 +275us[ +275us] +/- 39ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 989 +120us[ +107us] +/- 7966us
Current performance for ntp23.linocomm.net (Paris, FR)
Mon 8 Jun 18:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 974 +577us[ +811us] +/- 12ms ^? 2a10-3781-08Cc.connected> 0 10 0 - +0ns[ +0ns] +/- 0ns ^- ntp-public-2.oma.be 2 10 377 64 -591us[ -591us] +/- 42ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 965 +965us[+1198us] +/- 8142us
Current performance for ntp24.linocomm.net (Paris, FR)
Mon 8 Jun 18:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 927 -798us[ -803us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 909 -735us[ -741us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 107 +1543us[+1543us] +/- 41ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 415 -111us[ -111us] +/- 8183us ^+ d54c70bd3.static.telenet> 1 10 377 770 +5704us[+5699us] +/- 12ms ^* 82-64-45-50.subs.proxad.> 1 10 377 564 +141us[ +136us] +/- 5573us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Mon 8 Jun 18:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 49 -496us[ -481us] +/- 8144us ^- time.fu-berlin.de 1 10 377 596 -295us[ -277us] +/- 59ms ^- ntp1.hetzner.de 2 8 377 250 -401us[ -385us] +/- 27ms ^- ntp2.hetzner.de 2 7 377 57 -225us[ -210us] +/- 18ms ^+ ntp3.hetzner.de 2 8 377 190 -641us[ -626us] +/- 36ms