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 12 Jul 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 9 377 341 -991us[-1000us] +/- 6619us ^+ 2a10-3781-08cC.connected> 2 10 377 495 -797us[ -793us] +/- 7108us ^- ntp-public-2.oma.be 2 8 377 88 -1187us[-1187us] +/- 35ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 147 -5291us[-5291us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 544 +1689us[+1698us] +/- 9099us ^+ 82-64-45-50.subs.proxad.> 1 10 377 830 +6789us[+6821us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sun 12 Jul 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 506 -327us[ -403us] +/- 7482us ^- time.fu-berlin.de 1 10 377 320 -333us[ -333us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 385 -309us[ -309us] +/- 28ms ^- ntp2.hetzner.de 2 8 377 79 -346us[ -346us] +/- 34ms ^- ntp3.hetzner.de 2 10 377 367 -37us[ -37us] +/- 25ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sun 12 Jul 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 278 -511us[ -574us] +/- 8409us ^- time.fu-berlin.de 1 10 377 29m -286us[ -320us] +/- 71ms ^- ntp1.hetzner.de 2 10 377 628 -404us[ -466us] +/- 31ms ^- ntp2.hetzner.de 2 7 377 2 -515us[ -515us] +/- 34ms ^- ntp3.hetzner.de 2 8 377 80 -165us[ -165us] +/- 15ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sun 12 Jul 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 9 377 436 -466us[ -466us] +/- 4020us ^* time1.esa.int 1 9 377 476 -74us[ -69us] +/- 3555us ^+ ntp1.time.nl 1 10 377 23m +42us[ -36us] +/- 4290us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sun 12 Jul 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 43m -696us[ -688us] +/- 7555us ^- time.fu-berlin.de 1 10 377 402 -518us[ -518us] +/- 60ms ^- ntp1.hetzner.de 2 9 377 398 -414us[ -414us] +/- 27ms ^- ntp2.hetzner.de 2 10 377 718 -617us[ -617us] +/- 26ms ^- ntp3.hetzner.de 2 10 377 9 -111us[ -111us] +/- 18ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sun 12 Jul 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 139 -1808us[-1808us] +/- 36ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 914 +5178ns[ +22us] +/- 7228us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sun 12 Jul 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 1021 +148us[ +213us] +/- 7789us ^- time.fu-berlin.de 1 10 377 435 -374us[ -374us] +/- 60ms ^- ntp1.hetzner.de 2 9 377 266 -314us[ -314us] +/- 30ms ^- ntp2.hetzner.de 2 6 377 13 -455us[ -455us] +/- 34ms ^+ ntp3.hetzner.de 2 10 377 289 -56us[ -56us] +/- 12ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sun 12 Jul 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 8 377 137 -2967us[-2967us] +/- 37ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 235 -3418ns[ -30us] +/- 6907us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sun 12 Jul 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 24 -1573us[-1573us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 493 -1505us[-1400us] +/- 12ms ^- ntp-public-2.oma.be 2 8 377 108 -4559us[-4559us] +/- 37ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 311 -1615us[-1509us] +/- 6918us ^+ d54c70bd3.static.telenet> 1 10 377 313 +5469us[+5574us] +/- 12ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 128 +6475us[+6475us] +/- 7470us
Current performance for ntp22.linocomm.net (Paris, FR)
Sun 12 Jul 16:58:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 991 -344us[ -331us] +/- 11ms ^+ 2a10-3781-08cC.connected> 2 10 377 413 +39us[ +39us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 656 -1407us[-1392us] +/- 45ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 590 +41us[ +56us] +/- 7957us
Current performance for ntp23.linocomm.net (Paris, FR)
Sun 12 Jul 16:58:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 685 +325us[ +379us] +/- 12ms ^+ 2a10-3781-08cC.connected> 2 10 377 293 -32us[ +16us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 538 -124us[ -72us] +/- 37ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 228 -87us[ -39us] +/- 7847us
Current performance for ntp24.linocomm.net (Paris, FR)
Sun 12 Jul 16:58:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 713 -4483us[-3831us] +/- 13ms ^+ 2A10-3781-08Cc.connected> 2 10 377 818 -2983us[-2332us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 939 -3309us[-2660us] +/- 39ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 836 -2968us[-2318us] +/- 8104us ^+ d54c70bd3.static.telenet> 1 10 377 902 +1329us[+1977us] +/- 10ms ^* 82-64-45-50.subs.proxad.> 1 10 377 477 +4732us[+5389us] +/- 5763us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sun 12 Jul 16:58:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 914 -526us[ -593us] +/- 8189us ^- time.fu-berlin.de 1 9 377 94 -411us[ -411us] +/- 65ms ^- ntp1.hetzner.de 2 10 377 429 -352us[ -352us] +/- 28ms ^- ntp2.hetzner.de 2 6 377 41 -414us[ -414us] +/- 33ms ^+ ntp3.hetzner.de 2 9 377 360 -77us[ -77us] +/- 24ms