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)
Thu 13 Aug 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 80 +725us[ +725us] +/- 6620us ^* 2a10-3781-08cc.connected> 2 9 377 489 +759us[+1710us] +/- 6187us ^- ntp-public-2.oma.be 2 8 377 33 +967us[ +967us] +/- 9053us ^+ ntp0.rrze.uni-erlangen.de 1 8 377 32 -2937us[-2937us] +/- 10ms ^+ d54c70bd3.static.telenet> 1 10 377 617 +5684us[+6545us] +/- 9799us ^+ 82-64-171-216.subs.proxa> 1 10 377 954 +422us[+1046us] +/- 8623us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Thu 13 Aug 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 95 -210us[ -166us] +/- 7315us ^- time.fu-berlin.de 1 10 377 208 -841us[ -798us] +/- 58ms ^- ntp1.hetzner.de 2 9 377 130 +527us[ +571us] +/- 33ms ^- ntp2.hetzner.de 2 10 377 990 -320us[ -281us] +/- 27ms ^- ntp3.hetzner.de 2 10 377 445 -214us[ -172us] +/- 23ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Thu 13 Aug 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 9 377 378 -201us[ -112us] +/- 7979us ^- time.fu-berlin.de 1 9 377 76 -672us[ -672us] +/- 60ms ^- ntp1.hetzner.de 2 9 377 323 +648us[ +648us] +/- 32ms ^- ntp2.hetzner.de 2 8 377 42 -276us[ -276us] +/- 28ms ^- ntp3.hetzner.de 2 9 377 33 -171us[ -171us] +/- 28ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Thu 13 Aug 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ time1.esa.int 1 8 377 155 -125us[ -206us] +/- 3320us ^+ ntp1.time.nl 1 8 377 183 -358us[ -437us] +/- 4621us ^* ntp0.nl.uu.net 1 9 377 13 -260us[ -345us] +/- 3478us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Thu 13 Aug 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 367 33m -263us[ -184us] +/- 7312us ^- time.fu-berlin.de 1 10 377 660 -219us[ -219us] +/- 58ms ^- ntp1.hetzner.de 2 9 377 45 +683us[ +683us] +/- 35ms ^- ntp2.hetzner.de 2 10 377 102 -220us[ -220us] +/- 28ms ^- ntp3.hetzner.de 2 9 377 71 +94us[ +94us] +/- 28ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Thu 13 Aug 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 476 -1917us[-1956us] +/- 15ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 337 +4367ns[ -37us] +/- 7215us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Thu 13 Aug 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 528 -907us[ -941us] +/- 8490us ^- time.fu-berlin.de 1 10 377 496 -373us[ -373us] +/- 58ms ^- ntp1.hetzner.de 2 9 377 468 +536us[ +536us] +/- 29ms ^- ntp2.hetzner.de 2 10 377 752 -309us[ -342us] +/- 30ms ^- ntp3.hetzner.de 2 9 377 472 -198us[ -198us] +/- 21ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Thu 13 Aug 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 8 377 171 -2648us[-2648us] +/- 20ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 365 +23us[ +36us] +/- 6984us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Thu 13 Aug 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 8 377 182 -98us[ -98us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 771 +215us[ +76us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 17 -2800us[-2800us] +/- 11ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 12 -57us[ -57us] +/- 7018us ^+ d54c70bd3.static.telenet> 1 10 377 860 +2103us[+1963us] +/- 7809us ^* 82-64-171-216.subs.proxa> 1 10 377 415 +210us[ +72us] +/- 6051us
Current performance for ntp22.linocomm.net (Paris, FR)
Thu 13 Aug 16:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 813 +92us[ -95us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 947 -81us[ -268us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 739 -233us[ -420us] +/- 14ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 216 -27us[ -15us] +/- 8044us
Current performance for ntp23.linocomm.net (Paris, FR)
Thu 13 Aug 16:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 55 -221us[ -221us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 367 362 -1311us[-1311us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 45 +498us[ +498us] +/- 14ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 612 +132us[ +198us] +/- 8032us
Current performance for ntp24.linocomm.net (Paris, FR)
Thu 13 Aug 16:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 375 840 -1800us[-1799us] +/- 12ms ^- 2a10-3781-08cc.connected> 2 10 377 373 -280us[ -280us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 425 +146us[ +141us] +/- 19ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 294 +39us[ +39us] +/- 7828us ^- d54c70bd3.static.telenet> 1 10 377 868 +4605us[+4605us] +/- 11ms ^* 82-64-171-216.subs.proxa> 1 10 377 408 +267us[ +262us] +/- 3747us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Thu 13 Aug 16:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 382 -559us[ -491us] +/- 8116us ^- time.fu-berlin.de 1 10 377 104 -799us[ -799us] +/- 60ms ^- ntp1.hetzner.de 2 9 377 228 +181us[ +181us] +/- 33ms ^- ntp2.hetzner.de 2 10 377 247 -760us[ -760us] +/- 24ms ^- ntp3.hetzner.de 2 9 377 18 -591us[ -591us] +/- 28ms