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)
Sat 20 Jun 18:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 940 +90us[ +25us] +/- 6572us ^* 2A10-3781-08cc.connected> 2 10 377 375 -42us[ -110us] +/- 6119us ^- ntp-public-2.oma.be 2 10 377 434 +71us[+3279ns] +/- 31ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 601 -3942us[-4009us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 189 +2329us[+2329us] +/- 8780us ^+ 82-64-45-50.subs.proxad.> 1 10 373 474 +703us[ +636us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sat 20 Jun 18:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 238 -94us[ -157us] +/- 7154us ^- time.fu-berlin.de 1 10 377 637 -379us[ -437us] +/- 58ms ^- ntp1.hetzner.de 2 10 377 356 -477us[ -539us] +/- 30ms ^- ntp2.hetzner.de 2 7 377 92 -229us[ -229us] +/- 26ms ^- ntp3.hetzner.de 2 9 377 211 -354us[ -354us] +/- 25ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sat 20 Jun 18:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 31m -1418us[-1439us] +/- 9059us ^- time.fu-berlin.de 1 10 377 644 -778us[ -778us] +/- 58ms ^- ntp1.hetzner.de 2 9 377 178 -1014us[-1014us] +/- 33ms ^- ntp2.hetzner.de 2 7 377 53 -758us[ -758us] +/- 25ms ^- ntp3.hetzner.de 2 8 377 265 -848us[ -848us] +/- 23ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sat 20 Jun 18:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 705 +64us[ +100us] +/- 3710us ^* time1.esa.int 1 9 377 456 -158us[ -124us] +/- 3473us ^+ ntp1.time.nl 1 10 377 78 -4356ns[-4356ns] +/- 4379us
Current performance for ntp5.linocomm.net (Paris, FR)
Sun 7 Jun 08:34:01 UTC 2026
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sat 20 Jun 18:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 638 -537us[ -542us] +/- 7614us ^- time.fu-berlin.de 1 9 377 310 -398us[ -398us] +/- 62ms ^- ntp1.hetzner.de 2 9 377 322 -522us[ -522us] +/- 30ms ^- ntp2.hetzner.de 2 8 377 325 -255us[ -255us] +/- 22ms ^- ntp3.hetzner.de 2 9 377 423 -337us[ -337us] +/- 37ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sat 20 Jun 18:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 827 -1571us[-1571us] +/- 26ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 856 -85us[ -208us] +/- 7144us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sat 20 Jun 18:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 1019 -122us[ -236us] +/- 7740us ^- time.fu-berlin.de 1 10 377 519 -392us[ -392us] +/- 60ms ^- ntp1.hetzner.de 2 10 377 831 -544us[ -544us] +/- 29ms ^- ntp2.hetzner.de 2 7 377 105 -432us[ -432us] +/- 24ms ^- ntp3.hetzner.de 2 9 377 336 -427us[ -427us] +/- 22ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sat 20 Jun 18:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 478 -2163us[-2163us] +/- 31ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 876 -533us[ -682us] +/- 8878us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Sat 20 Jun 18:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 326 +13us[ +83us] +/- 8043us ^- time.fu-berlin.de 1 10 377 376 -169us[ -99us] +/- 62ms ^- ntp1.hetzner.de 2 8 377 23 -358us[ -358us] +/- 28ms ^- ntp2.hetzner.de 2 7 377 15 -76us[ -76us] +/- 25ms ^- ntp3.hetzner.de 2 9 377 234 -117us[ -117us] +/- 23ms
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sat 20 Jun 18:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 395 -504us[ -504us] +/- 8751us ^+ 2a10-3781-08cc.connected> 2 10 377 96 -572us[ -572us] +/- 9140us ^- ntp-public-2.oma.be 2 10 377 342 -2115us[-2115us] +/- 33ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 512 -601us[ -601us] +/- 9016us ^+ d54c70bd3.static.telenet> 1 10 377 593 +4051us[+4051us] +/- 10ms ^* 82-64-45-50.subs.proxad.> 1 10 377 824 -402us[ -156us] +/- 7326us
Current performance for ntp22.linocomm.net (Paris, FR)
Sat 20 Jun 18:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 796 -351us[ -456us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 767 +192us[ +217us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 758 -1796us[-1772us] +/- 32ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 255 -30us[-3308ns] +/- 7936us
Current performance for ntp23.linocomm.net (Paris, FR)
Sat 20 Jun 18:01:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 775 -332us[ -344us] +/- 12ms ^+ 2a10-3781-08cC.connected> 2 10 377 181 -37us[ -37us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 138 +1563us[+1563us] +/- 42ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 686 +182us[ +171us] +/- 8009us
Current performance for ntp24.linocomm.net (Paris, FR)
Sat 20 Jun 18:01:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 105 -2549us[-2620us] +/- 13ms ^? 2A10-3781-08cc.connected> 0 10 0 - +0ns[ +0ns] +/- 0ns ^- ntp-public-2.oma.be 2 10 377 182 -1015us[-1086us] +/- 39ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 207 -945us[-1016us] +/- 7950us ^+ d54c70bd3.static.telenet> 1 10 377 116 +1982us[+1911us] +/- 10ms ^* 82-64-45-50.subs.proxad.> 1 10 177 36 -295us[ -366us] +/- 5668us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sat 20 Jun 18:01:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 193 -201us[ -179us] +/- 8090us ^- time.fu-berlin.de 1 10 377 618 -336us[ -315us] +/- 58ms ^- ntp1.hetzner.de 2 8 377 111 -456us[ -456us] +/- 34ms ^- ntp2.hetzner.de 2 6 377 19 -193us[ -193us] +/- 25ms ^- ntp3.hetzner.de 2 8 377 135 -255us[ -255us] +/- 25ms