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 20 Jul 21:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 761 -53us[+8714ns] +/- 7900us ^* 2a10-3781-08cc.connected> 2 10 377 754 -187us[ -125us] +/- 7671us ^- ntp-public-2.oma.be 2 10 377 959 +239us[ +300us] +/- 41ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 189 -4066us[-4066us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 237 +5535us[+5535us] +/- 12ms ^+ 82-64-171-216.subs.proxa> 1 10 377 670 +1589us[+1589us] +/- 9749us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Mon 20 Jul 21:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 357 449 -367us[ -371us] +/- 7549us ^- time.fu-berlin.de 1 10 377 163 -734us[ -734us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 557 -299us[ -304us] +/- 26ms ^- ntp2.hetzner.de 2 10 377 31m -417us[ -426us] +/- 35ms ^- ntp3.hetzner.de 2 10 377 334 -214us[ -214us] +/- 21ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Mon 20 Jul 21:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 971 -731us[ -723us] +/- 8882us ^- time.fu-berlin.de 1 9 377 76 -861us[ -861us] +/- 63ms ^- ntp1.hetzner.de 2 10 377 31m -89us[ -81us] +/- 19ms ^- ntp2.hetzner.de 2 10 377 515 -57us[ -57us] +/- 51ms ^- ntp3.hetzner.de 2 10 377 739 +15us[ +15us] +/- 39ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Mon 20 Jul 21:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 937 +123us[ +123us] +/- 3765us ^* time1.esa.int 1 10 377 32m -51us[ +110us] +/- 3485us ^+ ntp1.time.nl 1 10 377 195 +366us[ +366us] +/- 4379us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Mon 20 Jul 21:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 529 -764us[ -763us] +/- 7814us ^- time.fu-berlin.de 1 10 377 515 -654us[ -654us] +/- 71ms ^- ntp1.hetzner.de 2 10 377 482 -538us[ -538us] +/- 27ms ^- ntp2.hetzner.de 2 10 377 669 -507us[ -506us] +/- 50ms ^- ntp3.hetzner.de 2 10 377 452 -1536us[-1536us] +/- 46ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Mon 20 Jul 21:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 536 -1773us[-1771us] +/- 48ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 363 -100us[ -98us] +/- 7408us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Mon 20 Jul 21:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 842 -114us[ -90us] +/- 7859us ^- time.fu-berlin.de 1 10 377 745 -291us[ -291us] +/- 68ms ^+ ntp1.hetzner.de 2 10 377 393 -58us[ -58us] +/- 30ms ^- ntp2.hetzner.de 2 10 377 921 -137us[ -113us] +/- 45ms ^- ntp3.hetzner.de 2 10 377 120 +53us[ +53us] +/- 23ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Mon 20 Jul 21:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 100 -2890us[-2890us] +/- 24ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 861 -432ns[-3182ns] +/- 7074us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Mon 20 Jul 21:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 255 -337us[ -337us] +/- 13ms ^+ 2A10-3781-08cc.connected> 2 10 377 715 -114us[ -64us] +/- 12ms ^- ntp-public-2.oma.be 2 7 377 674 -2676us[-2624us] +/- 47ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 399 +124us[ +124us] +/- 7034us ^+ d54c70bd3.static.telenet> 1 10 377 626 +6840us[+6893us] +/- 11ms ^* 82-64-171-216.subs.proxa> 1 10 377 523 -7920ns[ +48us] +/- 5716us
Current performance for ntp22.linocomm.net (Paris, FR)
Mon 20 Jul 21:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 32 +1508us[+1986us] +/- 15ms ^+ 2A10-3781-08CC.connected> 2 10 377 417 -503us[ -201us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 558 +119us[ +405us] +/- 52ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 13 +431us[ +910us] +/- 8197us
Current performance for ntp23.linocomm.net (Paris, FR)
Mon 20 Jul 21:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 43 -1909us[-1909us] +/- 15ms ^+ 2a10-3781-08cc.connected> 2 10 377 177 +78us[ +202us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 418 +527us[ +665us] +/- 57ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 95 +393us[ +519us] +/- 7923us
Current performance for ntp24.linocomm.net (Paris, FR)
Mon 20 Jul 21:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 751 -192us[ +388us] +/- 12ms ^- 2a10-3781-08CC.connected> 2 10 377 741 -2089us[-1509us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 859 -1381us[ -805us] +/- 48ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 55 +345us[ +345us] +/- 7801us ^- d54c70bd3.static.telenet> 1 10 377 442 +5008us[+5008us] +/- 12ms ^* 82-64-171-216.subs.proxa> 1 10 377 589 +339us[ +923us] +/- 3481us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Mon 20 Jul 21:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 964 -243us[ -252us] +/- 7919us ^- time.fu-berlin.de 1 10 377 767 -403us[ -403us] +/- 67ms ^- ntp1.hetzner.de 2 9 377 149 -239us[ -239us] +/- 33ms ^- ntp2.hetzner.de 2 9 377 37 -283us[ -283us] +/- 34ms ^- ntp3.hetzner.de 2 10 377 704 -192us[ -192us] +/- 39ms