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)
Wed 5 Aug 07:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 10 377 504 +112us[ +136us] +/- 6001us ^+ 2a10-3781-08cc.connected> 2 10 377 17 +345us[ +345us] +/- 6153us ^- ntp-public-2.oma.be 2 7 377 16 +60us[ +60us] +/- 26ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 385 -3582us[-3582us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 430 +3475us[+3475us] +/- 9372us ^+ 82-64-171-216.subs.proxa> 1 10 377 276 +2156us[+2156us] +/- 9637us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Wed 5 Aug 07:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 9 377 488 +65us[ +229us] +/- 8715us ^- time.fu-berlin.de 1 10 377 390 -580us[ -580us] +/- 61ms ^- ntp1.hetzner.de 2 7 377 11 -615us[ -615us] +/- 14ms ^- ntp2.hetzner.de 2 8 377 22 -415us[ -415us] +/- 34ms ^- ntp3.hetzner.de 2 10 377 84 -1627us[-1627us] +/- 39ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Wed 5 Aug 07:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 280 -737us[-1178us] +/- 11ms ^- time.fu-berlin.de 1 10 377 73 -38us[ -38us] +/- 66ms ^+ ntp1.hetzner.de 2 9 377 329 -188us[ -628us] +/- 25ms ^+ ntp2.hetzner.de 2 9 377 427 -39us[ -479us] +/- 26ms ^+ ntp3.hetzner.de 2 9 377 430 +185us[ -255us] +/- 31ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Wed 5 Aug 07:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 9 377 93 -338us[ -470us] +/- 3633us ^+ time1.esa.int 1 10 377 275 -161us[ -285us] +/- 3456us ^+ ntp1.time.nl 1 9 377 35 -248us[ -248us] +/- 4469us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Wed 5 Aug 07:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 344 -26us[ -226us] +/- 8810us ^- time.fu-berlin.de 1 9 377 169 -226us[ -226us] +/- 64ms ^+ ntp1.hetzner.de 2 8 377 107 -242us[ -242us] +/- 13ms ^- ntp2.hetzner.de 2 8 377 304 -308us[ -308us] +/- 30ms ^- ntp3.hetzner.de 2 9 377 156 -1527us[-1527us] +/- 38ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Wed 5 Aug 07:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp-public-2.oma.be 2 10 377 147 -1782us[-1782us] +/- 26ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 892 +565us[ -74us] +/- 9296us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Wed 5 Aug 07:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 678 -116us[ -58us] +/- 9607us ^- time.fu-berlin.de 1 10 377 15 -126us[ -126us] +/- 67ms ^- ntp1.hetzner.de 2 7 377 42 -135us[ -135us] +/- 15ms ^- ntp2.hetzner.de 2 7 377 45 -214us[ -214us] +/- 32ms ^+ ntp3.hetzner.de 2 9 377 127 +60us[ +60us] +/- 36ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Wed 5 Aug 07:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 8 377 140 -2579us[-2579us] +/- 27ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 569 +276us[+1147us] +/- 6857us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Wed 5 Aug 07:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 115 -379us[ -170us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 268 -493us[ -288us] +/- 11ms ^- ntp-public-2.oma.be 2 8 377 7 -3586us[-3586us] +/- 29ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 132 -648us[ -440us] +/- 6890us ^+ d54c70bd3.static.telenet> 1 10 377 127 +2996us[+3204us] +/- 8176us ^* 82-64-171-216.subs.proxa> 1 10 377 38 -54us[ +156us] +/- 6207us
Current performance for ntp22.linocomm.net (Paris, FR)
Wed 5 Aug 07:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 756 -658us[ -715us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 651 -539us[ -576us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 570 -2343us[-2377us] +/- 40ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 155 +18us[ +32us] +/- 8198us
Current performance for ntp23.linocomm.net (Paris, FR)
Wed 5 Aug 07:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 748 -421us[ -624us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 227 -1687us[-1542us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 462 -640us[ -514us] +/- 40ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 158 -316us[ -164us] +/- 7874us
Current performance for ntp24.linocomm.net (Paris, FR)
Wed 5 Aug 07:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 179 -2495us[-2495us] +/- 13ms ^- 2a10-3781-08cc.connected> 2 10 377 403 -643us[ -576us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 763 -978us[-1031us] +/- 35ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 55 -358us[ -358us] +/- 8045us ^+ d54c70bd3.static.telenet> 1 10 377 752 +2104us[+2050us] +/- 8938us ^* 82-64-171-216.subs.proxa> 1 9 377 202 -358us[ -290us] +/- 3751us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Wed 5 Aug 07:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 367 525 -283us[ -333us] +/- 9634us ^- time.fu-berlin.de 1 9 377 432 -240us[ -240us] +/- 61ms ^- ntp1.hetzner.de 2 6 377 5 -244us[ -244us] +/- 15ms ^- ntp2.hetzner.de 2 6 377 18 -307us[ -307us] +/- 32ms ^- ntp3.hetzner.de 2 8 377 157 -117us[ -117us] +/- 35ms