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 21 Aug 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 58 -1502us[-1502us] +/- 6625us ^+ 2a10-3781-08cc.connected> 2 10 377 969 -193us[ -193us] +/- 6577us ^- ntp-public-2.oma.be 2 10 377 945 -41us[ -41us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 30m -4042us[-4080us] +/- 10ms ^+ d54c70bd3.static.telenet> 1 10 377 862 +5012us[+5012us] +/- 10ms ^+ 82-64-171-216.subs.proxa> 1 10 377 195 -1170us[-1170us] +/- 11ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Fri 21 Aug 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 1037 -522us[ -540us] +/- 7551us ^- time.fu-berlin.de 1 10 377 867 -678us[ -678us] +/- 60ms ^- ntp1.hetzner.de 2 10 377 174 -377us[ -377us] +/- 28ms ^- ntp2.hetzner.de 2 8 377 110 -500us[ -500us] +/- 22ms ^- ntp3.hetzner.de 2 9 377 150 -439us[ -439us] +/- 37ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Fri 21 Aug 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 599 -330us[ -179us] +/- 8261us ^- time.fu-berlin.de 1 9 377 357 -565us[ -565us] +/- 65ms ^- ntp1.hetzner.de 2 9 377 232 -468us[ -468us] +/- 28ms ^- ntp2.hetzner.de 2 6 377 39 -572us[ -572us] +/- 13ms ^- ntp3.hetzner.de 2 9 377 130 -682us[ -682us] +/- 35ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Fri 21 Aug 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 9 377 123 -225us[ -225us] +/- 3596us ^* time1.esa.int 1 9 377 410 -124us[ -194us] +/- 3545us ^+ ntp1.time.nl 1 9 377 369 -258us[ -258us] +/- 4664us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Fri 21 Aug 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 277 391 +65us[ +170us] +/- 7206us ^- time.fu-berlin.de 1 10 377 69 -357us[ -357us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 903 -268us[ -165us] +/- 32ms ^- ntp2.hetzner.de 2 9 377 317 -325us[ -325us] +/- 19ms ^- ntp3.hetzner.de 2 10 377 253 -472us[ -472us] +/- 35ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Fri 21 Aug 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp-public-2.oma.be 2 10 377 700 -982us[ -982us] +/- 23ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 454 +425us[ +425us] +/- 7456us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Fri 21 Aug 16:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 930 -464us[ -748us] +/- 7816us ^- time.fu-berlin.de 1 10 377 892 -583us[ -583us] +/- 60ms ^- ntp1.hetzner.de 2 9 377 446 -459us[ -459us] +/- 25ms ^- ntp2.hetzner.de 2 6 377 14 -610us[ -610us] +/- 14ms ^- ntp3.hetzner.de 2 8 377 16 -808us[ -808us] +/- 37ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Fri 21 Aug 16:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 7 377 101 -1711us[-1711us] +/- 32ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 831 -143us[ -93us] +/- 7065us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Fri 21 Aug 16:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 984 -188us[ -147us] +/- 9204us ^+ 2a10-3781-08cc.connected> 2 10 377 692 -365us[ -319us] +/- 8922us ^- ntp-public-2.oma.be 2 8 377 97 -1688us[-1688us] +/- 32ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 124 -122us[ -122us] +/- 7010us ^+ d54c70bd3.static.telenet> 1 10 377 521 +4395us[+4395us] +/- 8660us ^* 82-64-171-216.subs.proxa> 1 10 377 674 -422us[ -376us] +/- 5587us
Current performance for ntp22.linocomm.net (Paris, FR)
Fri 21 Aug 16:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 1021 -554us[ -333us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 27m -16us[ +186us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 591 +49us[ +74us] +/- 28ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 314 +202us[ +229us] +/- 8200us
Current performance for ntp23.linocomm.net (Paris, FR)
Fri 21 Aug 16:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 968 -1669us[-1708us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 823 -459us[ -502us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 941 -1452us[-1492us] +/- 41ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 32 -536us[ -553us] +/- 8091us
Current performance for ntp24.linocomm.net (Paris, FR)
Fri 21 Aug 16:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 41 -3284us[-3284us] +/- 13ms ^- 2a10-3781-08cc.connected> 2 10 377 612 -2992us[-2992us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 230 -1886us[-1886us] +/- 35ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 632 -732us[ -732us] +/- 7994us ^- d54c70bd3.static.telenet> 1 10 377 227 +2622us[+2622us] +/- 9947us ^* 82-64-171-216.subs.proxa> 1 10 377 791 -424us[ -331us] +/- 3691us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Fri 21 Aug 16:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 31m +28us[ +178us] +/- 7721us ^- time.fu-berlin.de 1 10 377 484 -335us[ -335us] +/- 63ms ^- ntp1.hetzner.de 2 10 377 912 -165us[ -165us] +/- 33ms ^- ntp2.hetzner.de 2 6 377 2 -310us[ -310us] +/- 14ms ^- ntp3.hetzner.de 2 9 377 187 -453us[ -453us] +/- 34ms