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 2 Jul 23:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 10 75 632 +470us[+1055us] +/- 7010us ^+ 2A10-3781-08Cc.connected> 2 10 375 756 +591us[+1175us] +/- 6976us ^- ntp-public-2.oma.be 2 10 377 798 +418us[+1002us] +/- 33ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 661 -3409us[-2825us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 616 +4058us[+4058us] +/- 9104us ^+ 82-64-45-50.subs.proxad.> 1 10 377 624 -52us[ -52us] +/- 12ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Thu 2 Jul 23:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 26 -304us[ -333us] +/- 7243us ^- time.fu-berlin.de 1 10 377 828 -594us[ -619us] +/- 58ms ^- ntp1.hetzner.de 2 9 377 298 -87us[ -114us] +/- 23ms ^- ntp2.hetzner.de 2 10 377 913 -1819us[-1844us] +/- 17ms ^- ntp3.hetzner.de 2 9 377 110 -647us[ -675us] +/- 37ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Thu 2 Jul 23:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 26m -2576us[-2597us] +/- 11ms ^- time.fu-berlin.de 1 9 377 360 -125us[ -125us] +/- 60ms ^- ntp1.hetzner.de 2 7 377 97 +359us[ +359us] +/- 27ms ^- ntp2.hetzner.de 2 7 377 18 +304us[ +304us] +/- 16ms ^- ntp3.hetzner.de 2 9 377 140 -159us[ -159us] +/- 35ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Thu 2 Jul 23:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 114 +244us[ +244us] +/- 3758us ^* time1.esa.int 1 10 377 1007 +41us[ +113us] +/- 3774us ^+ ntp1.time.nl 1 10 377 108 +420us[ +420us] +/- 6715us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Thu 2 Jul 23:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 541 -430us[ -378us] +/- 7893us ^- time.fu-berlin.de 1 10 377 472 -251us[ -251us] +/- 57ms ^- ntp1.hetzner.de 2 9 377 199 +396us[ +396us] +/- 24ms ^- ntp2.hetzner.de 2 7 377 287 +536us[ +536us] +/- 16ms ^- ntp3.hetzner.de 2 10 377 696 -1517us[-1467us] +/- 29ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Thu 2 Jul 23:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 416 -1916us[-1908us] +/- 39ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 189 +509ns[+8767ns] +/- 7277us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Thu 2 Jul 23:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 758 -597us[ -610us] +/- 7996us ^- time.fu-berlin.de 1 9 377 482 -689us[ -689us] +/- 59ms ^- ntp1.hetzner.de 2 9 377 156 -221us[ -221us] +/- 26ms ^- ntp2.hetzner.de 2 7 377 103 -170us[ -170us] +/- 15ms ^- ntp3.hetzner.de 2 8 377 201 -664us[ -664us] +/- 34ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Thu 2 Jul 23:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 143 -1861us[-1861us] +/- 43ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 413 +82us[ +160us] +/- 6967us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Thu 2 Jul 23:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 10 -411us[ -411us] +/- 10ms ^+ 2a10-3781-08cC.connected> 2 9 377 212 -218us[ -218us] +/- 10ms ^- ntp-public-2.oma.be 2 9 377 181 -1892us[-1892us] +/- 43ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 173 +129us[ +129us] +/- 6980us ^* d54c70bd3.static.telenet> 1 10 377 447 +5375us[+5526us] +/- 11ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 151 +577us[ +577us] +/- 7591us
Current performance for ntp22.linocomm.net (Paris, FR)
Thu 2 Jul 23:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 75 64 -1175us[-1175us] +/- 15ms ^+ 2a10-3781-08cC.connected> 2 10 261 965 +318us[+1154us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 647 +1785us[+1739us] +/- 41ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 400 +916us[ +893us] +/- 8057us
Current performance for ntp23.linocomm.net (Paris, FR)
Thu 2 Jul 23:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 353 51 +50us[ +114us] +/- 13ms ^+ 2a10-3781-08cC.connected> 2 10 137 33m -302us[ -167us] +/- 13ms ^- ntp-public-2.oma.be 2 10 152 47m -1467us[-1349us] +/- 45ms ^* ntp0.rrze.uni-erlangen.de 1 7 377 20 +707us[ +772us] +/- 8041us
Current performance for ntp24.linocomm.net (Paris, FR)
Thu 2 Jul 23:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 77 919 +730us[+1348us] +/- 13ms ^+ 2a10-3781-08cC.connected> 2 10 373 31m -2795us[-2258us] +/- 13ms ^- ntp-public-2.oma.be 2 10 177 976 -746us[ -135us] +/- 35ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 101 -423us[ -423us] +/- 8040us ^+ d54c70bd3.static.telenet> 1 10 377 410 +3950us[+3950us] +/- 10ms ^* 82-64-45-50.subs.proxad.> 1 10 377 500 +273us[ +938us] +/- 5963us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Thu 2 Jul 23:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 622 +34us[ +66us] +/- 7833us ^- time.fu-berlin.de 1 10 377 494 -39us[ -39us] +/- 59ms ^- ntp1.hetzner.de 2 8 377 153 +502us[ +502us] +/- 26ms ^- ntp2.hetzner.de 2 6 377 26 +469us[ +469us] +/- 16ms ^- ntp3.hetzner.de 2 8 377 244 +3756ns[+3756ns] +/- 33ms