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)
Sun 23 Aug 14:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 664 -273us[ -273us] +/- 5909us ^+ 2a10-3781-08cc.connected> 2 10 377 975 -456us[ -456us] +/- 6161us ^- ntp-public-2.oma.be 2 10 377 983 -23us[ -23us] +/- 38ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 32m -354us[ -277us] +/- 6720us ^+ d54c70bd3.static.telenet> 1 10 377 396 +5866us[+5866us] +/- 12ms ^+ 82-64-171-216.subs.proxa> 1 10 377 855 -452us[ -452us] +/- 11ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sun 23 Aug 14:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 531 -255us[ -247us] +/- 7156us ^- time.fu-berlin.de 1 10 377 911 -552us[ -544us] +/- 72ms ^- ntp1.hetzner.de 2 10 377 741 -423us[ -415us] +/- 30ms ^- ntp2.hetzner.de 2 10 377 28m -395us[ -385us] +/- 37ms ^- ntp3.hetzner.de 2 10 377 282 -327us[ -327us] +/- 35ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sun 23 Aug 14:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 94 -391us[ -422us] +/- 8106us ^- time.fu-berlin.de 1 10 377 923 -583us[ -612us] +/- 73ms ^- ntp1.hetzner.de 2 10 377 436 -470us[ -500us] +/- 36ms ^- ntp2.hetzner.de 2 8 377 200 -440us[ -471us] +/- 39ms ^- ntp3.hetzner.de 2 10 377 206 -428us[ -459us] +/- 17ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sun 23 Aug 14:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 218 -327us[ -497us] +/- 3650us ^* time1.esa.int 1 8 377 208 +15us[ -154us] +/- 3235us ^+ ntp1.time.nl 1 10 377 436 -672us[ -836us] +/- 5067us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sun 23 Aug 14:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 862 -27us[ +53us] +/- 7197us ^- time.fu-berlin.de 1 10 377 629 -441us[ -441us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 445 -399us[ -399us] +/- 35ms ^- ntp2.hetzner.de 2 10 377 711 -289us[ -289us] +/- 33ms ^- ntp3.hetzner.de 2 10 377 779 -248us[ -248us] +/- 28ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sun 23 Aug 14:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 166 -1315us[-1377us] +/- 51ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 16 -35us[ -104us] +/- 7369us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sun 23 Aug 14:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 535 -178us[ -167us] +/- 7850us ^- time.fu-berlin.de 1 10 377 372 -267us[ -267us] +/- 65ms ^- ntp1.hetzner.de 2 9 377 314 -170us[ -170us] +/- 38ms ^+ ntp2.hetzner.de 2 10 377 788 -160us[ -149us] +/- 30ms ^- ntp3.hetzner.de 2 9 377 407 -105us[ -105us] +/- 32ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sun 23 Aug 14:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp-public-2.oma.be 2 10 377 902 -1002us[-1010us] +/- 40ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 489 +326us[ +317us] +/- 6946us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sun 23 Aug 14:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 77 -400us[ -400us] +/- 8669us ^+ 2a10-3781-08cc.connected> 2 9 377 243 -233us[ -233us] +/- 8753us ^- ntp-public-2.oma.be 2 7 377 61 -1865us[-1865us] +/- 53ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 156 -401us[ -401us] +/- 7080us ^+ d54c70bd3.static.telenet> 1 10 377 35 +4870us[+4870us] +/- 10ms ^* 82-64-171-216.subs.proxa> 1 10 377 418 -344us[ -607us] +/- 4927us
Current performance for ntp22.linocomm.net (Paris, FR)
Sun 23 Aug 14:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 520 -66us[ -66us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 270 -14us[ -14us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 297 -20us[ -20us] +/- 52ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 460 -330us[ -327us] +/- 7967us
Current performance for ntp23.linocomm.net (Paris, FR)
Sun 23 Aug 14:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 172 -442us[ -520us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 313 -1715us[-1801us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 400 -1526us[-1601us] +/- 53ms ^* ntp0.rrze.uni-erlangen.de 1 7 377 22 +386us[ +355us] +/- 8074us
Current performance for ntp24.linocomm.net (Paris, FR)
Sun 23 Aug 14:40:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 367 598 -1613us[-1613us] +/- 12ms ^- 2a10-3781-08cc.connected> 2 10 377 264 -1664us[-1664us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 850 -382us[ -382us] +/- 45ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 290 -103us[ -103us] +/- 7869us ^- d54c70bd3.static.telenet> 1 10 377 871 +3458us[+3458us] +/- 10ms ^* 82-64-171-216.subs.proxa> 1 10 377 899 -8001ns[ -323us] +/- 3642us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sun 23 Aug 14:40:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 483 -634us[ -650us] +/- 8228us ^- time.fu-berlin.de 1 10 377 646 -376us[ -393us] +/- 61ms ^- ntp1.hetzner.de 2 9 377 40 -330us[ -330us] +/- 42ms ^- ntp2.hetzner.de 2 10 377 688 -278us[ -294us] +/- 32ms ^- ntp3.hetzner.de 2 10 377 11 -249us[ -249us] +/- 20ms