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 6 Sep 09:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 974 -392us[ -491us] +/- 6594us ^+ 2a10-3781-08cc.connected> 2 10 377 754 -350us[ -451us] +/- 6288us ^- ntp-public-2.oma.be 2 8 377 97 -938us[ -938us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 200 -586us[ -693us] +/- 6783us ^+ d54c70bd3.static.telenet> 1 10 377 371 +2492us[+2388us] +/- 8566us ^+ 82-64-171-216.subs.proxa> 1 10 377 453 -11us[ -115us] +/- 8471us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sun 6 Sep 09:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 900 -470us[ -450us] +/- 7408us ^- time.fu-berlin.de 1 9 377 153 -300us[ -300us] +/- 60ms ^- ntp1.hetzner.de 2 9 377 348 -604us[ -604us] +/- 28ms ^- ntp2.hetzner.de 2 10 377 17 -329us[ -329us] +/- 29ms ^- ntp3.hetzner.de 2 9 377 189 -564us[ -564us] +/- 43ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sun 6 Sep 09:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 31m -138us[ -106us] +/- 8049us ^- time.fu-berlin.de 1 10 377 544 -21us[ -21us] +/- 70ms ^- ntp1.hetzner.de 2 9 377 356 -108us[ -108us] +/- 29ms ^+ ntp2.hetzner.de 2 9 377 145 +274us[ +274us] +/- 25ms ^- ntp3.hetzner.de 2 8 377 133 -143us[ -143us] +/- 43ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sun 6 Sep 09:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 9 377 279 -558us[ -590us] +/- 3630us ^+ time1.esa.int 1 10 377 22m -190us[ -295us] +/- 3559us ^+ ntp1.time.nl 1 9 377 216 -168us[ -168us] +/- 4260us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sun 6 Sep 09:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 126 -136us[ -264us] +/- 7338us ^- time.fu-berlin.de 1 10 377 725 -399us[ -514us] +/- 67ms ^- ntp1.hetzner.de 2 10 377 324 -367us[ -490us] +/- 28ms ^- ntp2.hetzner.de 2 10 377 1029 +52us[ -56us] +/- 26ms ^- ntp3.hetzner.de 2 10 377 848 -294us[ -406us] +/- 33ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sun 6 Sep 09:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 151 -1976us[-1976us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 203 -44us[ -79us] +/- 7325us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sun 6 Sep 09:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 176 -271us[ -246us] +/- 8104us ^- time.fu-berlin.de 1 10 377 306 -383us[ -359us] +/- 58ms ^- ntp1.hetzner.de 2 10 377 892 -631us[ -609us] +/- 21ms ^- ntp2.hetzner.de 2 9 377 161 -172us[ -172us] +/- 25ms ^- ntp3.hetzner.de 2 8 377 55 -471us[ -471us] +/- 44ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sun 6 Sep 09:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 610 -1851us[-1776us] +/- 28ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 606 +120us[ +196us] +/- 7055us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sun 6 Sep 09:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 582 -1024us[-1744us] +/- 8745us ^+ 2a10-3781-08cc.connected> 2 9 377 481 -820us[ -820us] +/- 8974us ^- ntp-public-2.oma.be 2 9 377 98 -3156us[-3156us] +/- 35ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 350 -1023us[-1023us] +/- 6984us ^+ d54c70bd3.static.telenet> 1 10 377 679 +5517us[+4815us] +/- 11ms ^* 82-64-171-216.subs.proxa> 1 10 377 561 -792us[-1515us] +/- 5255us
Current performance for ntp22.linocomm.net (Paris, FR)
Sun 6 Sep 09:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 543 -1023us[-1130us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 36 -4283us[-4283us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 155 -3003us[-3003us] +/- 39ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 483 -810us[ -918us] +/- 7885us
Current performance for ntp23.linocomm.net (Paris, FR)
Sun 6 Sep 09:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 353 -329us[ -513us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 39 -338us[ -338us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 189 -3015us[-3201us] +/- 39ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 159 -670us[ -857us] +/- 8105us
Current performance for ntp24.linocomm.net (Paris, FR)
Sun 6 Sep 09:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 560 -894us[ -894us] +/- 11ms ^- 2a10-3781-08cc.connected> 2 10 377 27m +51us[+1180ns] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 705 -3145us[-3215us] +/- 32ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 37 -916us[ -916us] +/- 7795us ^+ d54c70bd3.static.telenet> 1 10 377 412 +2210us[+2210us] +/- 9307us ^* 82-64-171-216.subs.proxa> 1 10 377 698 -487us[ -557us] +/- 3832us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sun 6 Sep 09:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 277 -703us[ -705us] +/- 8200us ^- time.fu-berlin.de 1 10 377 66 -456us[ -456us] +/- 62ms ^- ntp1.hetzner.de 2 9 377 78 -581us[ -581us] +/- 33ms ^- ntp2.hetzner.de 2 10 377 582 -247us[ -250us] +/- 19ms ^- ntp3.hetzner.de 2 7 377 93 -566us[ -566us] +/- 43ms