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)
Tue 7 Jul 17:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 264 -268us[ -525us] +/- 6773us ^* 2a10-3781-08cC.connected> 2 10 377 25 +10us[ -251us] +/- 7270us ^- ntp-public-2.oma.be 2 7 377 86 +536us[ +275us] +/- 31ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 191 -3592us[-3850us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 430 +7365us[+7111us] +/- 13ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 957 -511us[ -754us] +/- 11ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Tue 7 Jul 17:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 357 23m -162us[ -331us] +/- 7289us ^- time.fu-berlin.de 1 10 377 228 -699us[ -699us] +/- 57ms ^+ ntp1.hetzner.de 2 8 377 127 -374us[ -374us] +/- 13ms ^- ntp2.hetzner.de 2 7 377 65 -281us[ -281us] +/- 32ms ^- ntp3.hetzner.de 2 9 377 452 -251us[ -251us] +/- 30ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Tue 7 Jul 17:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 344 -165us[ -182us] +/- 8159us ^- time.fu-berlin.de 1 10 377 33m -314us[ -332us] +/- 64ms ^- ntp1.hetzner.de 2 8 377 253 -102us[ -102us] +/- 15ms ^- ntp2.hetzner.de 2 6 377 10 -91us[ -91us] +/- 31ms ^+ ntp3.hetzner.de 2 8 377 152 -47us[ -47us] +/- 33ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Tue 7 Jul 17:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 800 +226us[ +297us] +/- 3873us ^* time1.esa.int 1 10 377 768 +322us[ +393us] +/- 3552us ^+ ntp1.time.nl 1 10 377 17 +355us[ +355us] +/- 4442us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Tue 7 Jul 17:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 80 -176us[ -107us] +/- 7505us ^- time.fu-berlin.de 1 10 377 240 -239us[ -174us] +/- 57ms ^- ntp1.hetzner.de 2 9 377 354 -29us[ +33us] +/- 12ms ^- ntp2.hetzner.de 2 10 377 150 -2729ns[ +65us] +/- 31ms ^+ ntp3.hetzner.de 2 10 377 342 +58us[ +120us] +/- 32ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Tue 7 Jul 17:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 753 -1617us[-1670us] +/- 22ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 332 -119us[ -184us] +/- 7377us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Tue 7 Jul 17:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 994 -104us[ -35us] +/- 7974us ^- time.fu-berlin.de 1 10 377 396 -198us[ -198us] +/- 58ms ^- ntp1.hetzner.de 2 9 377 231 -104us[ -104us] +/- 15ms ^- ntp2.hetzner.de 2 6 377 63 -79us[ -79us] +/- 30ms ^+ ntp3.hetzner.de 2 7 377 112 -45us[ -45us] +/- 34ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Tue 7 Jul 17:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 911 -2624us[-2629us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 600 -20us[ -25us] +/- 7096us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Tue 7 Jul 17:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 801 -1652us[-1794us] +/- 11ms ^+ 2A10-3781-08CC.connected> 2 10 377 138 -1506us[-1506us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 934 -2568us[-2712us] +/- 34ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 186 +111us[ -22us] +/- 6891us ^* d54c70bd3.static.telenet> 1 10 377 146 +5210us[+5077us] +/- 9977us ^+ 82-64-45-50.subs.proxad.> 1 10 377 137 +409us[ +409us] +/- 7484us
Current performance for ntp22.linocomm.net (Paris, FR)
Tue 7 Jul 17:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 175 -2173us[-2173us] +/- 14ms ^+ 2a10-3781-08CC.connected> 2 10 377 787 -493us[ -715us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 632 +394us[ +394us] +/- 28ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 718 +49us[ -174us] +/- 7901us
Current performance for ntp23.linocomm.net (Paris, FR)
Tue 7 Jul 17:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 723 +897us[+1002us] +/- 13ms ^+ 2A10-3781-08Cc.connected> 2 10 377 544 -2518us[-2409us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 557 +1843us[+1952us] +/- 30ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 357 +15us[ +128us] +/- 7800us
Current performance for ntp24.linocomm.net (Paris, FR)
Tue 7 Jul 17:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 548 +749us[ +858us] +/- 13ms ^+ 2A10-3781-08Cc.connected> 2 10 377 914 -870us[ -768us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 1005 +838us[ +941us] +/- 37ms ^+ ntp0.rrze.uni-erlangen.de 1 7 377 104 -187us[ -187us] +/- 8158us ^+ d54c70bd3.static.telenet> 1 10 377 472 +5879us[+5990us] +/- 13ms ^* 82-64-45-50.subs.proxad.> 1 9 377 109 +428us[ +548us] +/- 5878us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Tue 7 Jul 17:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 849 -978us[ -791us] +/- 8061us ^- time.fu-berlin.de 1 10 377 540 -1138us[-1138us] +/- 59ms ^- ntp1.hetzner.de 2 9 377 69 -989us[ -989us] +/- 15ms ^- ntp2.hetzner.de 2 7 377 47 -975us[ -975us] +/- 30ms ^- ntp3.hetzner.de 2 8 377 119 -973us[ -973us] +/- 34ms