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)
Sat 22 Aug 21:34:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 118 -324us[ -324us] +/- 6679us ^+ 2a10-3781-08cc.connected> 2 10 377 422 -518us[ -518us] +/- 6045us ^- ntp-public-2.oma.be 2 10 377 602 -408us[ -408us] +/- 29ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 24m -363us[ -285us] +/- 6561us ^+ d54c70bd3.static.telenet> 1 10 377 934 +6012us[+6012us] +/- 11ms ^+ 82-64-171-216.subs.proxa> 1 10 377 296 -1692us[-1692us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sat 22 Aug 21:34:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 357 3 -204us[ -252us] +/- 7351us ^- time.fu-berlin.de 1 10 377 410 -148us[ -194us] +/- 64ms ^- ntp1.hetzner.de 2 10 377 193 -124us[ -172us] +/- 15ms ^- ntp2.hetzner.de 2 10 377 205 -86us[ -134us] +/- 23ms ^- ntp3.hetzner.de 2 10 377 732 -47us[ -92us] +/- 30ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sat 22 Aug 21:34:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 357 577 -2467us[-2247us] +/- 10ms ^- time.fu-berlin.de 1 9 377 436 -358us[ -358us] +/- 65ms ^+ ntp1.hetzner.de 2 9 377 336 -110us[ -110us] +/- 14ms ^- ntp2.hetzner.de 2 9 377 444 -204us[ -204us] +/- 18ms ^- ntp3.hetzner.de 2 9 377 207 -49us[ -49us] +/- 36ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sat 22 Aug 21:34:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 699 -85us[ +156us] +/- 3470us ^* time1.esa.int 1 9 377 455 -225us[ +26us] +/- 3396us ^+ ntp1.time.nl 1 10 377 482 -123us[ +127us] +/- 4362us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sat 22 Aug 21:34:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 464 -895us[-1156us] +/- 7692us ^- time.fu-berlin.de 1 10 377 101 -749us[ -749us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 919 -487us[ -748us] +/- 23ms ^- ntp2.hetzner.de 2 10 377 128 -665us[ -665us] +/- 17ms ^- ntp3.hetzner.de 2 10 377 268 -584us[ -584us] +/- 37ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sat 22 Aug 21:34:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 677 -1749us[-1759us] +/- 29ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 2 -96us[ -105us] +/- 7442us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sat 22 Aug 21:34:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 41 -384us[ -483us] +/- 7890us ^- time.fu-berlin.de 1 10 377 891 -476us[ -565us] +/- 58ms ^- ntp1.hetzner.de 2 10 377 766 -268us[ -358us] +/- 26ms ^- ntp2.hetzner.de 2 10 377 780 -363us[ -453us] +/- 13ms ^- ntp3.hetzner.de 2 9 377 384 -190us[ -286us] +/- 33ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sat 22 Aug 21:34:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 356 -1749us[-1749us] +/- 20ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 955 +14us[-4038ns] +/- 6990us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sat 22 Aug 21:34:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 108 +297us[ +297us] +/- 9332us ^+ 2a10-3781-08cc.connected> 2 9 377 221 -92us[ -92us] +/- 9061us ^- ntp-public-2.oma.be 2 8 377 160 -1737us[-1737us] +/- 23ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 320 +50us[ +50us] +/- 6897us ^+ d54c70bd3.static.telenet> 1 10 377 572 +6445us[+6445us] +/- 11ms ^* 82-64-171-216.subs.proxa> 1 10 377 856 +147us[ +246us] +/- 5504us
Current performance for ntp22.linocomm.net (Paris, FR)
Sat 22 Aug 21:34:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 962 -2039us[-1786us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 774 +339us[ +453us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 776 -2069us[-1955us] +/- 33ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 428 +295us[ +410us] +/- 8090us
Current performance for ntp23.linocomm.net (Paris, FR)
Sat 22 Aug 21:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 86 -1858us[-1858us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 796 -109us[ -164us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 974 -47us[ -222us] +/- 29ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 134 +62us[ +57us] +/- 8217us
Current performance for ntp24.linocomm.net (Paris, FR)
Sat 22 Aug 21:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 91 -2051us[-2051us] +/- 12ms ^- 2a10-3781-08cc.connected> 2 10 377 741 -2534us[-2534us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 334 -260us[ -260us] +/- 23ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 157 -291us[ -291us] +/- 7898us ^- d54c70bd3.static.telenet> 1 10 377 22m +3672us[+3578us] +/- 10ms ^* 82-64-171-216.subs.proxa> 1 10 377 875 -13us[ -127us] +/- 3747us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sat 22 Aug 21:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 936 -480us[ -444us] +/- 8098us ^- time.fu-berlin.de 1 10 377 216 -374us[ -374us] +/- 60ms ^+ ntp1.hetzner.de 2 8 377 156 -189us[ -189us] +/- 17ms ^- ntp2.hetzner.de 2 10 377 351 -237us[ -237us] +/- 19ms ^- ntp3.hetzner.de 2 10 377 47 -86us[ -86us] +/- 39ms