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 10 Aug 10:13:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 10 377 480 +152us[ +14us] +/- 6892us ^+ 2a10-3781-08cc.connected> 2 10 377 800 +441us[ +305us] +/- 6547us ^- ntp-public-2.oma.be 2 10 377 662 -173us[ -309us] +/- 21ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 516 -3861us[-4000us] +/- 10ms ^+ d54c70bd3.static.telenet> 1 10 377 880 +4576us[+4441us] +/- 11ms ^+ 82-64-171-216.subs.proxa> 1 10 377 482 +1836us[+1697us] +/- 9649us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Mon 10 Aug 10:13:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 374 -222us[ -187us] +/- 7401us ^- time.fu-berlin.de 1 10 377 835 -373us[ -340us] +/- 58ms ^- ntp1.hetzner.de 2 10 377 269 +345us[ +345us] +/- 29ms ^- ntp2.hetzner.de 2 10 377 211 -182us[ -182us] +/- 11ms ^- ntp3.hetzner.de 2 9 377 99 -171us[ -171us] +/- 35ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Mon 10 Aug 10:13:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 137 705 -110us[ -518us] +/- 8132us ^- time.fu-berlin.de 1 10 377 581 -147us[ -147us] +/- 58ms ^- ntp1.hetzner.de 2 10 377 303 -1304us[-1304us] +/- 31ms ^- ntp2.hetzner.de 2 8 377 190 -217us[ -217us] +/- 10ms ^- ntp3.hetzner.de 2 8 377 500 -172us[ -172us] +/- 28ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Mon 10 Aug 10:13:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 10 377 190 -310us[ -664us] +/- 3468us ^+ time1.esa.int 1 10 377 530 -521us[ -852us] +/- 3639us ^+ ntp1.time.nl 1 9 377 511 -406us[ -738us] +/- 4561us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Mon 10 Aug 10:13:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 367 966 -172us[ -235us] +/- 7114us ^- time.fu-berlin.de 1 10 377 492 -382us[ -382us] +/- 59ms ^- ntp1.hetzner.de 2 10 377 479 -18us[ -18us] +/- 34ms ^- ntp2.hetzner.de 2 10 377 14 -2446us[-2446us] +/- 16ms ^- ntp3.hetzner.de 2 10 377 455 -404us[ -404us] +/- 30ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Mon 10 Aug 10:13:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 643 -2228us[-2228us] +/- 23ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 225 -141us[ -142us] +/- 7318us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Mon 10 Aug 10:13:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 65 +39us[ +104us] +/- 7694us ^- time.fu-berlin.de 1 10 377 284 -418us[ -353us] +/- 59ms ^- ntp1.hetzner.de 2 7 377 102 +67us[ +131us] +/- 32ms ^- ntp2.hetzner.de 2 7 377 118 -496us[ -431us] +/- 11ms ^- ntp3.hetzner.de 2 9 377 392 -410us[ -346us] +/- 29ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Mon 10 Aug 10:13:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 181 -2812us[-2797us] +/- 30ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 108 +40us[ +56us] +/- 6998us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Mon 10 Aug 10:13:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 356 +73us[-8007ns] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 127 -314us[ -314us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 398 -3221us[-3302us] +/- 27ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 223 -422us[ -422us] +/- 6991us ^+ d54c70bd3.static.telenet> 1 10 377 26m +4799us[+4669us] +/- 9664us ^* 82-64-171-216.subs.proxa> 1 10 377 237 -386us[ -468us] +/- 5972us
Current performance for ntp22.linocomm.net (Paris, FR)
Mon 10 Aug 10:13:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 88 -1776us[-1903us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 546 -2066us[-1920us] +/- 13ms ^- ntp-public-2.oma.be 2 9 377 2 -44us[ -171us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 2 -418us[ -546us] +/- 7855us
Current performance for ntp23.linocomm.net (Paris, FR)
Mon 10 Aug 10:13:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 681 -171us[ -79us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 513 +101us[ +193us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 25m +180us[ -476us] +/- 31ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 189 -128us[ -97us] +/- 8150us
Current performance for ntp24.linocomm.net (Paris, FR)
Mon 10 Aug 10:13:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 525 +235us[ +135us] +/- 11ms ^- 2a10-3781-08cc.connected> 2 10 377 943 -1124us[-1303us] +/- 12ms ^- ntp-public-2.oma.be 2 9 377 662 -2153us[-2248us] +/- 27ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 248 -218us[ -326us] +/- 7993us ^- d54c70bd3.static.telenet> 1 10 377 190 +1820us[+1710us] +/- 8788us ^* 82-64-171-216.subs.proxa> 1 9 377 188 -226us[ -336us] +/- 3613us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Mon 10 Aug 10:13:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 177 957 -825us[ -921us] +/- 7796us ^- time.fu-berlin.de 1 10 377 581 -881us[ -881us] +/- 58ms ^- ntp1.hetzner.de 2 7 377 61 -378us[ -378us] +/- 33ms ^- ntp2.hetzner.de 2 7 377 57 -886us[ -886us] +/- 12ms ^- ntp3.hetzner.de 2 8 377 41 -854us[ -854us] +/- 34ms