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)
Wed 22 Jul 19:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 9 357 211 +109us[ -58us] +/- 9928us ^+ 2a10-3781-08cc.connected> 2 10 377 59m +213us[ -67us] +/- 8099us ^- ntp-public-2.oma.be 2 9 377 272 +1014us[ +843us] +/- 34ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 60 -3087us[-3087us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 1144 +4039us[+3818us] +/- 9577us ^+ 82-64-171-216.subs.proxa> 1 10 377 731 +3298us[+3100us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Wed 22 Jul 19:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 280 -84us[ -128us] +/- 7466us ^- time.fu-berlin.de 1 10 377 101 -149us[ -149us] +/- 60ms ^- ntp1.hetzner.de 2 9 377 833 -330us[ -372us] +/- 37ms ^- ntp2.hetzner.de 2 9 377 492 +14us[ -30us] +/- 30ms ^- ntp3.hetzner.de 2 10 377 282 +122us[ +78us] +/- 38ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Wed 22 Jul 19:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 275 +3137ns[ +103us] +/- 8252us ^- time.fu-berlin.de 1 10 377 266 +53us[ +53us] +/- 58ms ^+ ntp1.hetzner.de 2 9 377 190 -180us[ -180us] +/- 21ms ^- ntp2.hetzner.de 2 9 377 553 -39us[ +57us] +/- 28ms ^- ntp3.hetzner.de 2 10 377 381 +84us[ +182us] +/- 35ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Wed 22 Jul 19:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 317 +361us[ +361us] +/- 3686us ^* time1.esa.int 1 10 377 52m +150us[ +625us] +/- 3380us ^+ ntp1.time.nl 1 10 373 137 +506us[ +506us] +/- 4563us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Wed 22 Jul 19:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 177 235 -35us[ +142us] +/- 7610us ^- time.fu-berlin.de 1 10 377 539 -135us[ +39us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 972 -367us[ -198us] +/- 35ms ^- ntp2.hetzner.de 2 9 377 213 -1251us[-1251us] +/- 36ms ^- ntp3.hetzner.de 2 10 377 77 +39us[ +39us] +/- 41ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Wed 22 Jul 19:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 85 -2006us[-2006us] +/- 22ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 235 -19us[ -33us] +/- 7129us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Wed 22 Jul 19:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 938 -626us[ -631us] +/- 8071us ^- time.fu-berlin.de 1 10 377 81 -463us[ -463us] +/- 60ms ^- ntp1.hetzner.de 2 9 377 446 -622us[ -622us] +/- 43ms ^- ntp2.hetzner.de 2 8 377 119 -378us[ -378us] +/- 35ms ^- ntp3.hetzner.de 2 10 377 246 -260us[ -260us] +/- 37ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Wed 22 Jul 19:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 445 -1638us[-1705us] +/- 32ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 313 -57us[ -127us] +/- 6918us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Wed 22 Jul 19:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 235 -1178us[-1178us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 315 -1229us[-1191us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 445 -1922us[-1884us] +/- 32ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 330 -340us[ -302us] +/- 6990us ^+ d54c70bd3.static.telenet> 1 10 377 790 +1860us[+1898us] +/- 6902us ^* 82-64-171-216.subs.proxa> 1 10 377 294 -249us[ -211us] +/- 5618us
Current performance for ntp22.linocomm.net (Paris, FR)
Wed 22 Jul 19:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 70 -1002us[-1002us] +/- 17ms ^+ 2a10-3781-08cc.connected> 2 10 377 25m +312us[ +303us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 117 +1496us[+1496us] +/- 25ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 402 +1498us[+1472us] +/- 8184us
Current performance for ntp23.linocomm.net (Paris, FR)
Wed 22 Jul 19:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 30m +261us[ +317us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 217 -546us[ -546us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 718 +416us[ +456us] +/- 32ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 361 +534us[ +579us] +/- 7847us
Current performance for ntp24.linocomm.net (Paris, FR)
Wed 22 Jul 19:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 59m -1182us[ -974us] +/- 13ms ^- 2a10-3781-08cc.connected> 2 10 377 506 -2848us[-2763us] +/- 16ms ^- ntp-public-2.oma.be 2 10 377 133 -1946us[-1946us] +/- 26ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 991 -48us[ +21us] +/- 8212us ^+ d54c70bd3.static.telenet> 1 10 377 796 +6782us[+6857us] +/- 13ms ^* 82-64-171-216.subs.proxa> 1 10 377 447 +184us[ +270us] +/- 3744us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Wed 22 Jul 19:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 968 +26us[ +56us] +/- 7673us ^- time.fu-berlin.de 1 10 377 96 -346us[ -346us] +/- 60ms ^- ntp1.hetzner.de 2 8 377 63 -439us[ -439us] +/- 23ms ^- ntp2.hetzner.de 2 8 377 83 -238us[ -238us] +/- 35ms ^- ntp3.hetzner.de 2 10 377 565 -133us[ -133us] +/- 32ms