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 10 Aug 03:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 9 377 36 -161us[ -219us] +/- 7385us ^+ 2a10-3781-08cc.connected> 2 10 377 851 -288us[ -760us] +/- 7463us ^- ntp-public-2.oma.be 2 9 377 221 -369us[ -422us] +/- 21ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 30 -4133us[-4133us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 913 +3916us[+3449us] +/- 9180us ^+ 82-64-171-216.subs.proxa> 1 10 377 559 -1340us[-1838us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Mon 10 Aug 03:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 347 393 -600us[ -619us] +/- 7635us ^- time.fu-berlin.de 1 10 377 872 -910us[ -928us] +/- 62ms ^- ntp1.hetzner.de 2 9 377 128 -637us[ -637us] +/- 24ms ^- ntp2.hetzner.de 2 10 377 21m -824us[ -842us] +/- 28ms ^- ntp3.hetzner.de 2 9 377 938 -294us[ -312us] +/- 38ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Mon 10 Aug 03:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 758 -1543us[-1569us] +/- 9456us ^- time.fu-berlin.de 1 10 377 1191 -324us[ -348us] +/- 73ms ^- ntp1.hetzner.de 2 9 377 399 -368us[ -368us] +/- 21ms ^- ntp2.hetzner.de 2 9 377 1047 -569us[ -594us] +/- 31ms ^- ntp3.hetzner.de 2 9 377 301 +158us[ +158us] +/- 18ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Mon 10 Aug 03:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 10 377 819 -9975ns[ +182us] +/- 3470us ^+ time1.esa.int 1 10 377 572 -137us[ -137us] +/- 3604us ^+ ntp1.time.nl 1 9 377 324 +116us[ +116us] +/- 4397us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Mon 10 Aug 03:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 54 -997us[ -876us] +/- 7382us ^- time.fu-berlin.de 1 10 377 534 -2755us[-2639us] +/- 60ms ^- ntp1.hetzner.de 2 9 377 506 -1436us[-1320us] +/- 18ms ^- ntp2.hetzner.de 2 10 377 148 -1549us[-1429us] +/- 26ms ^- ntp3.hetzner.de 2 10 377 570 -973us[ -857us] +/- 43ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Mon 10 Aug 03:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 742 -2501us[-2499us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 276 -49us[ -48us] +/- 7336us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Mon 10 Aug 03:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 95 -1149us[-1149us] +/- 8490us ^- time.fu-berlin.de 1 10 377 361 -818us[ -818us] +/- 62ms ^- ntp1.hetzner.de 2 9 377 495 -786us[ -786us] +/- 19ms ^- ntp2.hetzner.de 2 8 377 75 -1122us[-1122us] +/- 25ms ^- ntp3.hetzner.de 2 8 377 210 -493us[ -493us] +/- 19ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Mon 10 Aug 03:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 8 377 256 -3052us[-3046us] +/- 23ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 154 -7517ns[-1255ns] +/- 6954us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Mon 10 Aug 03:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 445 -596us[ -506us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 9 377 450 -452us[ -363us] +/- 12ms ^- ntp-public-2.oma.be 2 9 377 178 -3627us[-3627us] +/- 24ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 37 -476us[ -476us] +/- 6986us ^+ d54c70bd3.static.telenet> 1 10 377 588 +3842us[+3928us] +/- 9391us ^* 82-64-171-216.subs.proxa> 1 10 377 307 -340us[ -247us] +/- 5718us
Current performance for ntp22.linocomm.net (Paris, FR)
Mon 10 Aug 03:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 206 +713us[+1047us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 615 -9900ns[ +834us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 101 +94us[ +439us] +/- 27ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 66 +720us[+1069us] +/- 8198us
Current performance for ntp23.linocomm.net (Paris, FR)
Mon 10 Aug 03:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 757 -2050us[-1812us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 599 +74us[ +327us] +/- 12ms ^- ntp-public-2.oma.be 2 9 377 97 -116us[ -116us] +/- 27ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 159 +533us[ +798us] +/- 8224us
Current performance for ntp24.linocomm.net (Paris, FR)
Mon 10 Aug 03:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 631 -30us[ -387us] +/- 11ms ^- 2a10-3781-08cc.connected> 2 10 377 995 -2205us[-2604us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 735 -2146us[-2515us] +/- 39ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 213 +72us[ +72us] +/- 8137us ^- d54c70bd3.static.telenet> 1 10 377 302 +7547us[+7229us] +/- 14ms ^* 82-64-171-216.subs.proxa> 1 10 377 239 +175us[ -136us] +/- 3723us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Mon 10 Aug 03:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 177 2 +32us[ +407us] +/- 7516us ^- time.fu-berlin.de 1 10 377 160 -714us[ -345us] +/- 65ms ^- ntp1.hetzner.de 2 7 377 73 -619us[ -247us] +/- 25ms ^- ntp2.hetzner.de 2 8 377 195 -963us[ -595us] +/- 24ms ^- ntp3.hetzner.de 2 9 377 64 -379us[-6123ns] +/- 13ms